Fix Code 52 driver signature error

Code 52 means Windows blocked the device's driver because its digital signature is missing, invalid or damaged. The fix is to remove that driver and install a correctly signed one from Windows Update or the device maker's website. Microsoft's Device Manager error code article and its Learn page for Code 52 say a signed driver is the only end-user fix.

Checked November 3, 2026 against the manufacturer's own pages.

The short version

What to install and where it comes from. Every link goes to the manufacturer or Microsoft, never to a copy.

Developer nameCM_PROB_UNSIGNED_DRIVER
Rule behind itKernel-mode code signing policy
Secure Boot onNew kernel drivers must be signed through Microsoft's portal
Event log to checkCode Integrity, Operational
Microsoft Support: Error codes in Device Manager (Code 52)support.microsoft.comMicrosoft Learn: Code 52 CM_PROB_UNSIGNED_DRIVERlearn.microsoft.comMicrosoft Learn: Driver signing policylearn.microsoft.com

Official files only, nothing bundled

Step by step

  1. Note the device and recent changes

    Write down the device name showing Code 52 and anything installed just before it appeared, such as a new device, a driver from a disc or a utility that installs its own driver.

  2. Run Windows Update

    Open Settings, Windows Update, check for updates, then open Advanced options, Optional updates and install any driver listed for the device. Drivers from Windows Update are published through Microsoft.

  3. Remove the blocked driver

    In Device Manager, right-click the device, choose Uninstall device and tick the option to delete the driver software if it is shown. Restart.

  4. Install the maker's current driver

    Download the driver for your exact model and Windows version from the PC maker or the device maker's support page. Microsoft's recommended resolution is the latest driver from the hardware maker.

  5. Restore if it started after an update

    If Code 52 began after a recent install and no signed driver is available yet, use System Restore to a point from before the change, and contact the maker for a signed release.

Faster option: update drivers automatically

The steps above fix this one device. If several drivers are old, a driver updater finds and installs them all in one go, and backs up the current ones first.

  1. Driver Updater scan listing outdated drivers1. Scan. Download the free version and run a scan.
  2. Missing driver found with the newest version2. Review. See each old or missing driver with its newer version.
  3. Update complete with every driver updated3. Update. Update one driver free, or all at once with Pro.

Update this driver automatically

Finds and updates this driver and every other outdated driver on your PC.

Auslogics Driver Updater · Free scan · Windows 11, 10, 8, 7 · Backup before every change

What does Code 52 mean?

The full message from Microsoft is: “Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)”. Microsoft’s support article gives the cause as a driver that may be unsigned or corrupted. Microsoft Learn adds that the driver does not comply with the kernel-mode code signing policy, and that the device did not start because of it.

How Secure Boot affects driver signing

Microsoft’s driver signing policy explains why a driver that once loaded can now be refused. Starting with Windows 10 version 1607, Windows does not load new kernel-mode drivers unless they are signed through Microsoft’s Hardware Dev Center portal. Microsoft lists three exceptions where older cross-signed drivers are still allowed:

Exception What it means for you
PC upgraded to Windows 10 version 1607 from an earlier release Older drivers kept working after that upgrade
Secure Boot is off in the BIOS The stricter rule does not apply
Signed with a certificate issued before 29 July 2015 Very old drivers can still load

So a reinstall of Windows 11, or turning Secure Boot back on, can expose an old driver that never met the newer rule. The fix is a driver signed under current rules, not undoing the protection.

Where to look for more detail

Microsoft Learn points to Code Integrity events for diagnosis. Open Event Viewer, then Applications and Services Logs, Microsoft, Windows, CodeIntegrity, Operational. Entries logged at the time the device failed can show which file failed the signature check. Search the maker’s support page for that file name or the device model to find the signed version.

Questions

Should I disable driver signature enforcement to fix Code 52?

No. Microsoft Learn says the only end-user fix is a digitally signed driver. Methods for loading unsigned drivers are meant for developers testing their own code, and they leave the PC open to unverified kernel code.

Can Code 52 mean malware?

It can. Microsoft's message says the file might be malicious software from an unknown source. If you did not install anything new, run a full Microsoft Defender scan before reinstalling drivers.

Why did an old driver work before and not now?

Microsoft's policy allows some older cross-signed drivers only in set cases, such as Secure Boot being off or a PC upgraded to Windows 10 version 1607 from an earlier release. A clean install or a BIOS change can remove that exception.

Does turning Secure Boot off fix Code 52?

Do not use that as a fix. Secure Boot protects the start-up process, and the right answer is a driver that meets Microsoft's signing rules, which works with Secure Boot on.