Third-Party INF No Digital Signature: Fix

If you see “The third-party INF does not contain digital signature information” while installing a driver on Windows, the fix is to temporarily disable driver signature enforcement, install the driver, then re-enable enforcement. This error appears because Windows 10 and 11 require drivers to be digitally signed, and third-party or unsigned drivers are blocked by default.

Why Windows Blocks Unsigned Drivers

Starting with Windows Vista, Microsoft required all kernel-mode drivers to be digitally signed. A digital signature verifies the driver’s publisher and confirms the file hasn’t been tampered with. This protects your system from malicious or buggy code that could cause crashes or security vulnerabilities.

When a driver lacks a valid signature, Windows assumes it may be unsafe and refuses to install it. This is common with older hardware, niche peripherals, or drivers downloaded from smaller vendors that haven’t gone through Microsoft’s certification process.

How to Fix the Error (Step-by-Step)

There are several ways to bypass the signature check. The most reliable method is to start Windows in a special mode that disables enforcement temporarily.

1. Open Settings > Update & Security > Recovery (Windows 10) or System > Recovery (Windows 11).
2. Under “Advanced startup,” click Restart now.
3. After the PC restarts, choose Troubleshoot > Advanced options > Startup Settings > Restart.
4. When the Startup Settings screen appears, press 7 or F7 to select “Disable driver signature enforcement.”
5. Windows will boot with enforcement disabled for that session. Install the driver normally.
6. Restart your PC again—enforcement will be re-enabled automatically.

This method works for both Windows 10 and 11, and it’s the easiest because it doesn’t require any command-line tools.

Alternative: Use Advanced Boot Options (Windows 10/11)

If you can’t access Settings, you can interrupt the boot process three times. Turn the PC on, and as soon as the Windows logo appears, press and hold the power button to force shutdown. Repeat this three times. On the fourth boot, Windows should enter the Windows Recovery Environment automatically. From there, follow the same path: Troubleshoot > Advanced options > Startup Settings > Restart.

Permanent Fix: Sign the Driver Yourself

If you need to install the driver frequently, you can sign it with a self-signed certificate. This requires the Windows Driver Kit (WDK) and a tool called Inf2Cat and SignTool. Here’s the general process:

1. Create a self-signed certificate using MakeCert or New-SelfSignedCertificate in PowerShell.
2. Use Inf2Cat to create a catalog file for the driver.
3. Sign the catalog file with SignTool using your certificate.
4. Install the certificate into the “Trusted Root Certification Authorities” store.

This is more technical, but it makes the driver permanently accepted by Windows. Note that this only works on your own machine—other systems won’t trust your self-signed certificate unless you install it there too.

When a Driver Is Unsigned: Is It Safe?

An unsigned driver isn’t necessarily malicious. Many legitimate hardware vendors release drivers without Microsoft certification, especially for older or niche devices. However, an unsigned driver could also be malware disguised as a driver. Only download drivers from the manufacturer’s official website, and verify the file’s hash if possible. If you’re unsure, search for the driver filename online to see if others have reported issues.

Common Related Errors and Misconceptions

Some users confuse this error with “Driver is not digitally signed” or “Windows cannot verify the publisher.” These are similar but not identical. The “INF does not contain digital signature information” specifically means the .inf file (the installation file) lacks a signature, not the driver binary itself.

Another misconception is that disabling Secure Boot will fix this. Secure Boot is a separate feature that verifies the bootloader, not drivers. Disabling it won’t help with driver signatures.

If you’re using a 64-bit version of Windows, you cannot permanently disable driver signature enforcement via the boot menu—it only lasts for one session. That’s why the self-signing method is the only permanent solution.

Frequently Asked Questions

Will disabling driver signature enforcement harm my PC?

It’s temporary and only for one boot session. As long as you re-enable it (by restarting normally), your PC remains protected. The risk is limited to that session, so only install trusted drivers during that time.

Can I install an unsigned driver on Windows 11?

Yes, using the same method. Windows 11 has the same signature enforcement as Windows 10, but the Startup Settings option is still available.

Why does Windows keep blocking the driver even after I disable enforcement?

Make sure you’re booting into the “Disable driver signature enforcement” mode. If you restart normally, enforcement returns. Also, ensure you’re installing the driver during that session, not after a reboot.

Is there a way to permanently disable driver signature enforcement?

You can use the bcdedit command to set nointegritychecks on, but this is not recommended and can be reversed by Windows updates. It also weakens security. The self-signing method is safer.

What if the driver still fails to install after disabling enforcement?

Check if the driver is compatible with your Windows version. Some old drivers may need compatibility mode. Right-click the installer, select Properties, and set it to run in compatibility mode for an older Windows version.

Does this error appear on 32-bit Windows?

32-bit Windows versions have less strict signature enforcement, but they may still show the error for some drivers. The same fix works, but you may not need to disable enforcement at all.

Related

• Power Bank Confiscated at Airport? Rules Explained
• Sawzall Useful? Real Uses & Buying Tips
• Power Tool Batteries in Home Items: What Works