vista64: driver not loaded after updates, testsigning enabled



Hello,

I'm developing a KMDF driver under Vista64.
It has a test certificate, and loads fine if I attach windbg.
This morning (feb 14 2008), the driver is not loaded anymore.

In the device manager, I see "error code 37", which could indicate
a failed driver signature enforcement, if I remember right.
And as I used an early beta of WDK 6001, this was caused by WdfCoInstaller01007.dll: my driver was fine, but the coinstaller could not start.

I tried this:
- disabling signature enforcement with F8 at boot time does not help.
- "bcdedit -set testsigning ON" does not help.
- reinstalling the test certificate on the target machine did not help

I had some Vista security updates automatically installed this morning, maybe this caused the error.

What to do now?

Thanks for caring

J. Hoppe, PEAK-System Technik




.



Relevant Pages

  • Re: A sniffer, fast and dirty...
    ... Thank you Thomas, ... where I can't put the test certificate, so users will have to click thru ... Your PCAUSA rawether protocol driver installs in the old good legacy way ...
    (microsoft.public.development.device.drivers)
  • TestCertificate - "Not Digitally Signed"
    ... I have created a test certificate by using Makecert, ... imported it to the test system by certmgr, ... verified the Driver Signature by signtool verify. ... Inf2Cat tool is from Winqual Submission tools ...
    (microsoft.public.development.device.drivers)
  • Re: Kernel mode code signing - Test signing
    ... Install the test certificate in the Trusted Root Certification ... with "winqual submission tool .msi setup". ... I tried to sign the driver itself, but it doesn't work on Vista 64-bit. ...
    (microsoft.public.development.device.drivers)
  • Re: TestCertificate - "Not Digitally Signed"
    ... I found that I made a mistake when importing Test Certificate to a test ... verified the Driver Signature by signtool verify. ...
    (microsoft.public.development.device.drivers)
  • Re: I need help to understand a double fault
    ... If the processor also has MCA feature available (For example Intel ... O ID Other Information Error Code Error Code ... Now my driver> will ... > the request is still in the driver since I don't remove requests from> queue ...
    (microsoft.public.development.device.drivers)