|

Fix Device Manager Code 52 Digital Signature Error (2026)

Code 52 in Device Manager means Windows blocked a driver because it cannot verify the driver’s digital signature.

The device shows a yellow exclamation mark and does not start.

Microsoft’s answer is to install a properly signed driver for the device, and the steps below show how to find and replace the blocked one.

Quick answer

StepWhat to doWhy
1Read the Device status boxConfirms the Code 52 message
2Check Optional updates in Windows UpdateWindows may offer a signed driver
3Download the driver from the maker’s websiteMicrosoft says the fix is a digitally signed driver
4Check Event Viewer for blocked-driver eventsNames the driver that was blocked
5Ask the maker for a certified driverThe old driver may not have a signed replacement yet

What Code 52 means

Microsoft’s message for this code reads “Windows cannot verify the digital signature for the drivers required for this device.”

The same message adds that a recent hardware or software change might have installed a file that is signed incorrectly, damaged, or from an unknown source.

Microsoft’s driver documentation names the problem CM_PROB_UNSIGNED_DRIVER and says the device did not start on a 64-bit version of Windows because its driver is not digitally signed.

It says the driver does not meet the kernel-mode code signing policy, and that the only way to avoid the error is to obtain and install a digitally signed driver.

ItemMicrosoft’s wording
MessageWindows cannot verify the digital signature for the drivers required for this device. (Code 52)
Problem nameCM_PROB_UNSIGNED_DRIVER
Applies to64-bit versions of Windows
End-user resolutionInstall a digitally signed driver from the manufacturer

See the error in Device Manager

  1. Right-click the Start button and select Device Manager.
  2. Find the device with a yellow exclamation mark and right-click it.
  3. Select Properties.
  4. On the General tab, read the Device status box for the code and message.

Why an older driver can start failing

Microsoft’s Windows driver policy page says kernel-mode drivers must be signed by an authority Microsoft trusts.

It says new drivers go through the Windows Hardware Compatibility Program, known as WHCP.

Drivers signed under the older cross-signed program were trusted until the April 2026 security update, and are no longer trusted by default.

A short Microsoft allow list covers some widely used older drivers, so a driver that still loads may simply be on that list.

Fix 1: Check optional driver updates

Microsoft says optional drivers are not installed automatically.

  1. Open Settings, then Windows Update, then Advanced options.
  2. Under Additional options, select Optional updates.
  3. Tick any driver updates listed and select the download and install option.
  4. Restart the PC afterward.

Fix 2: Install the maker’s signed driver

Download the newest driver for your Windows version from the device maker or PC maker, not from a third-party driver site.

  1. In Device Manager, right-click the device and select Update driver.
  2. Select Browse my computer for drivers if you downloaded the files, then point it to the folder.
  3. Restart if Windows asks you to.

Microsoft’s update article also covers Uninstall device followed by a restart, which makes Windows try to reinstall the driver.

Our guide to updating a driver in Device Manager has the full routine.

Fix 3: Find the blocked driver in Event Viewer

If you do not know which driver is the problem, Microsoft says to check the Code Integrity log.

  1. Right-click Start and select Event Viewer.
  2. Go to Applications and Services Logs, then Microsoft, then Windows, then CodeIntegrity, then Operational.
  3. Look for event ID 3077, which Microsoft says means a driver was blocked by the enforcement policy.
  4. Look for event ID 3076 too, which means a driver would have been blocked but loaded because the policy was in audit mode.
  5. Open the event and read the file name of the driver.

Microsoft’s driver policy page also gives PowerShell commands that list the affected file, product and parent process from these events.

Fix 4: Ask the maker for a certified driver

Microsoft tells device users to contact the vendor and ask whether a WHCP-certified version of the driver exists.

Give the maker the file name from Event Viewer, the device name and your Windows version.

Microsoft says there is no way to exempt a single driver from the policy, and that the answer is a WHCP-signed version of that driver.

What not to do

Microsoft’s documentation describes ways to load an unsigned driver only for driver development and testing, and does not offer them as a fix for a user’s PC.

Its driver policy page advises keeping the protection turned on because turning it off reduces the security of the device.

A driver that cannot be verified may be damaged or malicious, as Microsoft’s own message warns, so replace it rather than work around it.

How Code 52 differs from similar codes

CodeMicrosoft’s messageFix
52Windows cannot verify the digital signature for the drivers.Install a signed driver from the maker
28The drivers for this device are not installed.See our Code 28 guide
43Windows has stopped this device because it has reported problems.See our Code 43 guide

Sources

Microsoft: Code 52 CM_PROB_UNSIGNED_DRIVER, The Windows driver policy, Update drivers through Device Manager and Error codes in Device Manager in Windows.

Leave a Reply

Your email address will not be published. Required fields are marked *