Issues after applying BSOD Patch to cure system crash in windows 10 v.18365
Welcome to all
I am describing about system crashes in Windows 10 v18365 when a scheduled back task/s performed by AOMEI Backupper.
The Issue was resolved by Admin by providing BSOD Patch (that was unsigned driver). BSOD Patch worked after "Disable Driver Signature Enforcement" but after restart "Driver Signature Enforcement" again enabled and AOMEI Backupper does not read the partitions in the system and hence backup process finished with error, log of this error showed "System does not find the path specified partition (Backup drive/partition)" and also new backup can not be created because of the same reason.
I also noted that the problem can be solved by permanently Disabling Driver Signature Enforcement (mean condition sustain after every restart),
Is there a way to disable driver Signature Enforcement permanently in Windows 10 v18362, HP 8440P.
Anybody can help;
I am describing about system crashes in Windows 10 v18365 when a scheduled back task/s performed by AOMEI Backupper.
The Issue was resolved by Admin by providing BSOD Patch (that was unsigned driver). BSOD Patch worked after "Disable Driver Signature Enforcement" but after restart "Driver Signature Enforcement" again enabled and AOMEI Backupper does not read the partitions in the system and hence backup process finished with error, log of this error showed "System does not find the path specified partition (Backup drive/partition)" and also new backup can not be created because of the same reason.
I also noted that the problem can be solved by permanently Disabling Driver Signature Enforcement (mean condition sustain after every restart),
Is there a way to disable driver Signature Enforcement permanently in Windows 10 v18362, HP 8440P.
Anybody can help;
Tagged:
Comments
When will the new driver finally be signed so that we can work with Backupper scheduled tasks again without problems?
How many weeks or months do we still have to wait before everything works normally again?
We had a similar driver signing issue with version 3 a few years ago. Then we also had to wait for ages before the driver successfully went through the signing process...
I refer to postings here:
https://www.aomeitech.com/forum/discussion/comment/8531#Comment_8531
and with regard to driver signing especially to the posts of RiseT .