I have a driver that gets loaded in our Recovery mode(windows PE). It was signed long back in 2011 with my company's SHA1 certificate. Till date it was working fine and loading fine in my recovery PE environment. I did not get Microsoft sign that driver.
Now for internal reasons I was suppose to sign the driver again. But now when I load the driver with new certificate I get error
"Error 577: Windows cannot verify the digital signature for this file"
The same driver works for 32 bit machine.
How does windows check the authenticity of my driver.
1. My previous driver also was not microsoft signed. But it worked. Now the new driver is not loading. Does the date at which the driver is signed matters?
2. To overcome it should I get it microsoft signed? If so how to run the suit for winPE environment.
It looks like you're new here. If you want to get involved, click one of these buttons!
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!||Kernel Debugging||30 Mar 2020||OSR Seminar Space|
|Developing Minifilters||20 Apr 2020||LIVE ONLINE|
|Writing WDF Drivers||11 May 2020||LIVE ONLINE|
|Internals & Software Drivers||28 Sept 2020||Dulles, VA|