Device Manager Code 52: Digital signature cannot be verified
Windows 64-bit Kernel-Mode Driver Signature Enforcement blocks a third-party driver because its cryptographic signature is absent, expired, or self-signed.
Internal desktop parts run on harmless 12V DC voltage and cannot shock you. Simply unplug the wall power cable first, then touch the unpainted metal case frame to ground static electricity.
Common Symptoms & Tells
- Status: 'Windows cannot verify the digital signature for the drivers required for this device. (Code 52)'
- Custom gamepad, legacy synthesizer, OBD2 car scanner, or microcontroller driver fails to start
- Occurs after upgrading Windows 10 to a newer feature update
Interactive Fix Checklist
0 of 4 steps completedCheck for an updated WHQL signed driver release
Visit the hardware manufacturer website to download the latest signed driver package updated for Windows 10/11 64-bit architecture.
Temporarily disable Driver Signature Enforcement
Hold Shift and click Restart from the Start Menu > Troubleshoot > Advanced Options > Startup Settings > Click Restart > Press 7 or F7 to 'Disable driver signature enforcement'. Test device functionality.
Install OEM digital security certificate into Windows Root Store
Right-click the driver's .inf or .sys file > Properties > Digital Signatures tab > Select signer > Details > View Certificate > Install Certificate > Select 'Trusted Root Certification Authorities'.
Use modern signed alternative driver packages
For USB serial devices (CH340, FTDI, CP2102) and controllers, download official WHQL drivers directly from FTDI Chip or Silicon Labs websites.
Still having trouble with your PC?
Describe what is happening to your AI Technician. We will tailor the fix to your exact hardware setup.