Fix Driver Not Digitally Signed Error in Windows

This guide walks you through resolving the “driver not digitally signed” error in Windows, which typically appears when installing older or third-party hardware drivers. The fix involves either enabling a special boot mode to allow unsigned drivers temporarily, or permanently disabling the signature enforcement via advanced startup settings. You’ll need administrator access to your PC and a few minutes to complete the steps.

What You’ll Need

Administrator account on the Windows PC
The driver installation file (usually a .inf or .sys file)
Access to the Windows Settings and Command Prompt
Optional: a backup of important data before making system changes

Step-by-Step

Identify the exact error: When the driver installation fails, note the error code (e.g., Code 52 or “Windows cannot verify the digital signature”). This confirms the issue is signature-related.
Open Windows Settings: Press Win + I to open Settings. Click “Update & Security” (Windows 10) or “System” (Windows 11), then select “Recovery” from the left sidebar.
Access Advanced Startup: Under the “Advanced startup” section, click “Restart now.” Your PC will reboot into the Windows Recovery Environment (WinRE).
Navigate to Startup Settings: In WinRE, click “Troubleshoot” â†’ “Advanced options” â†’ “Startup Settings” â†’ “Restart.” Your PC will restart again and show a list of boot options.
Enable Disable Driver Signature Enforcement: When the list appears, press 7 or F7 on your keyboard to select “Disable driver signature enforcement.” Windows will boot with this temporary setting.
Install the driver: Once Windows loads, run the driver installer again. The unsigned driver should now install without the signature error.
Reboot normally: After installation, restart your PC normally. The signature enforcement will be re-enabled automatically, but the driver remains installed and functional.
If the above doesn’t work (permanent method): Boot into WinRE again as in steps 2-4, but this time choose “Command Prompt” from Advanced options instead of Startup Settings. At the command prompt, type bcdedit /set testsigning on and press Enter. Reboot. This enables Test Mode, which allows unsigned drivers to load permanently. To turn it off later, repeat the steps and type bcdedit /set testsigning off.

Common Mistakes

Using the wrong boot option: Pressing F8 at the wrong time or selecting “Enable low-resolution video” instead of “Disable driver signature enforcement” will not help.
Not running the installer as administrator: Right-click the installer and select “Run as administrator” to avoid permission-related failures.
Forgetting to reboot after the driver install: Some drivers require a restart to take effect; if you skip it, the error may persist.
Leaving Test Mode on permanently: This can weaken system security and cause issues with other software. Turn it off once the driver is installed.

Tips

Check for a signed alternative: Before disabling signature enforcement, visit the hardware manufacturer’s website to see if a signed version of the driver is available for your Windows version.
Use the temporary method first: The F7 boot option is safer because it only affects the current session. Use it for a one-time driver installation.
Verify the driver source: Only download drivers from official manufacturer websites or trusted sources. Unsigned drivers from unknown sources may contain malware.
Create a system restore point: Before making permanent changes like enabling Test Mode, create a restore point so you can revert if something goes wrong.

Troubleshooting

If the driver still fails to install after following the steps:

Check Windows version compatibility: The driver may be designed for an older Windows version. Right-click the installer, go to Properties â†’ Compatibility, and try running it in compatibility mode for an earlier OS.
Re-download the driver: The file may be corrupted. Download it again and try the installation.
Use Device Manager: If the installer fails, open Device Manager, find the device with a yellow exclamation mark, right-click it, select “Update driver,” then “Browse my computer for drivers” and point to the downloaded driver folder.
Disable Secure Boot: Some systems block unsigned drivers at the firmware level. Enter your BIOS/UEFI settings (usually by pressing F2, F12, or Del during startup) and disable Secure Boot. This is a more advanced step; only do it if you’re comfortable with BIOS settings.
Check for Windows updates: Sometimes a Windows update can resolve signature verification issues. Go to Settings â†’ Update & Security â†’ Windows Update and check for updates.

Frequently Asked Questions

Is it safe to disable driver signature enforcement?

Temporarily disabling it for a single session is generally safe, but permanently disabling it (via Test Mode) can expose your system to potentially malicious drivers. Only do this if you trust the driver source.

Why does the error appear even for drivers from reputable manufacturers?

Some manufacturers release drivers that are not signed for the latest Windows versions, especially for older hardware. The signature may have expired or the driver may be in beta.

Will the driver stop working after I reboot normally?

No. Once the driver is installed, it remains active even after signature enforcement is re-enabled. The enforcement only applies to new driver installations, not to already-installed ones.

How do I know if a driver is unsigned?

Right-click the driver file (usually .inf or .sys), select Properties, and look for a “Digital Signatures” tab. If it’s missing, the file is unsigned.

Can I sign the driver myself?

Yes, but it requires a code-signing certificate and the Windows Driver Kit (WDK). This is complex and not recommended for most users. It’s easier to use the boot options described above.

What is the difference between “Disable driver signature enforcement” and “Test Mode”?

The F7 boot option disables enforcement for one boot session only. Test Mode (via bcdedit) disables it permanently until you turn it off, and it also displays a watermark on the desktop.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →