Share via

Device Manager error 52 despite valid certificates for custom driver

Megareyka 0 Reputation points
2024-09-14T09:20:08.55+00:00

Hello! I am learning to create drivers using the WDK, and I created a simple driver that appears as a Graphics Adapter in Device Manager. My certificate and .CAT files are valid, but I received error code 52 when checking the device status in Device Manager. Additionally, the Event Viewer shows the message: The driver \Driver\helloWorldDriver failed to load for the device ROOT\UNKNOWN\0000.

I am not sure if error 52 is causing the issue, and I have already checked the driver to be valid with signtool. I found solutions to disable Driver Signature Enforcement, but it seems a bit difficult for me to disable secure boot on and off as this is my only personal device. Are there any other free solutions? And is the error 52 responsible for the Event Viewer error?

If you have any help or guidance, I would greatly appreciate it as I am new to creating drivers.

Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
5,498 questions
Windows Driver Kit (WDK)
Windows Driver Kit (WDK)
A set of Microsoft tools that are used to develop, test, and deploy Windows drivers.
123 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Daisy Zhou 25,061 Reputation points Microsoft Vendor
    2024-09-18T08:12:13.9533333+00:00

    Hello Megareyka,

    Thank you for posting in Q&A forum.

    Error code 52 typically indicates that Windows cannot verify the digital signature for the driver files. Here are some steps you can take to troubleshoot：

    1. Verify Driver Signature:

    You can use the signtool utility to verify the signature: signtool verify /v /kp yourdriver.sys

    1. Disable Driver Signature Enforcement:

    Temporarily disable driver signature enforcement to test your driver:

    Run the following commands:

    bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS

    bcdedit -set TESTSIGNING ON

    Restart your computer and try loading the driver again.

    1. Reinstall the Driver:

    Uninstall the driver from Device Manager and then reinstall it:

    1. Check Event Viewer:

    Look for more detailed error messages in the Event Viewer that might give you additional clues about what is going wrong.

    I hope the information above is helpful.

    If you have any questions or concerns, please feel free to let us know.

    Best Regards,

    Daisy Zhou

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.