06-17-2024, 02:01 PM
(06-17-2024, 01:53 PM)lavande Wrote:(06-17-2024, 01:41 PM)admin Wrote:(06-17-2024, 01:24 PM)lavande Wrote:(06-17-2024, 01:11 PM)admin Wrote:(06-17-2024, 12:16 PM)lavande Wrote: Yes it is signed, it is there.
Can you zip the driver file and send it to [email protected]? We need to check it to see if it's corrupted.
The driver signature may not be valid for the Windows10/11 signature policy with for example secure boot, TPM and others. I did a search by skimming the articles because it's too complicated, there seem to be several Microsoft signature policies.
Yes, I will send you the file immediately to the email address indicated.
The strange thing is that it works very well on our computers that have TPM chip and have Secure Boot enabled.
Yes then it's strange. Windows defender had problems with error 577! I also saw eset endpoint security and others you are not the only ones
Microsoft requires the driver to be signed using EV code signing on Windows 8 and above, and hasldisk.sys is already signed using EV code signing, so this should not happen. Can you try temporarily disabling secure boot to see if it works?