![]() ![]() I had a similar issue a few months ago, when we decided to switch our certificate provider. Is anyone aware of any other changes which might make this combination fail to load? The new driver loads just fine on Windows 10 machines. They load the 2015 built driver just fine even though the certificates on both look identical. Something seems to have changed though and Windows 7 圆4 boxes can't load the new driver even with the latest updates. Windows 7 doesn't support SHA-2 certs out of the box however, it was previously working provided: Our driver was/is attestation signed by Microsoft via the MS Hardware portal and so it's joint signed by both our company and Microsoft with a SHA-2 signature each. Or that might be malicious software from an unknown source. ![]() Software change might have installed a file that is signed incorrectly or damaged, Windows cannot verify the digital signature for this file. It get's: Load failed with error: 0x80070241 ![]() I also moved to the latest SDK + WDK 22000 (Which is the new Windows 11 one).Įverything seemed to work except that on Win 7 圆4 (with secure boot) boxes the driver no longer loads. I recently took on a task to update our filter driver from building with Visual Studio 2015 -> 2019. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |