Fix Driver Not Validated for This Computer (Windows)

If you see “The driver being installed is not validated for this computer,” the fix is to disable Windows driver signature enforcement, then install the driver. This error appears when a driver lacks a valid Microsoft signature, often for older hardware or unsigned drivers on Windows 10 and 11.

Why Windows Blocks Unsigned Drivers

Since Windows Vista, 64-bit versions of Windows require kernel-mode drivers to be digitally signed by Microsoft. This signature proves the driver hasn’t been tampered with and comes from a known publisher. When you try to install an unsigned driver, Windows shows the “not validated” error and stops the installation. The policy is designed to prevent malware and unstable code from running at the kernel level, where a crash can blue-screen the whole system.

However, legitimate drivers—especially for older printers, audio interfaces, or specialized industrial hardware—may not have a valid signature. Manufacturers sometimes stop updating drivers, or the driver was signed with an expired certificate. In those cases, you have to tell Windows to temporarily allow unsigned drivers.

What “Not Validated” Actually Means

The error message is a bit misleading. It doesn’t mean the driver is broken or malicious; it means the driver doesn’t meet Windows’ signature requirements. There are two common scenarios:

Driver is unsigned: The publisher never submitted it to Microsoft for attestation signing.
Driver has an expired or revoked certificate: The signing certificate is no longer valid, so Windows treats it as untrusted.

In either case, the driver may work perfectly fine—especially if it’s from a reputable manufacturer and you downloaded it from their official site. The error is a safety gate, not a verdict on the driver’s quality.

How to Disable Driver Signature Enforcement

You can bypass the check by booting Windows into a special mode that disables signature enforcement for one session. Here’s how:

Open Settings > System > Recovery (Windows 11) or Update & Security > Recovery (Windows 10).
Under Advanced startup, click Restart now.
After the PC restarts, choose Troubleshoot > Advanced options > Startup Settings > Restart.
When the list of startup options appears, press 7 or F7 to select Disable driver signature enforcement.
Windows will boot normally, but with signature enforcement off. Install your driver now.

This setting only lasts for that boot. The next time you restart, signature enforcement is back on. That’s intentional—it keeps your system secure for everyday use while letting you install that one stubborn driver.

Alternative: Use Advanced Boot Options (Legacy Method)

If you can’t get into Windows normally, you can interrupt the boot process three times to trigger the recovery menu. Turn the PC on, and when the Windows logo appears, press and hold the power button to force shutdown. Do this three times. On the fourth boot, Windows should show the Automatic Repair screen. From there, follow the same path: Troubleshoot > Advanced options > Startup Settings > Restart, then press 7.

This method is useful if you can’t log in or if the error appears during early boot. It’s a bit harsh on the system, but it works when you have no other way in.

What to Do If the Driver Still Won’t Install

Sometimes disabling signature enforcement isn’t enough. Try these steps in order:

Update the driver via Device Manager: Right-click the device in Device Manager, choose Update driver, and select Browse my computer. Point it to the folder with the driver files. Windows may accept it even without the signature.
Use the driver’s own installer: Run the setup file as administrator (right-click > Run as administrator). Some installers handle the signature issue internally.
Check for a signed version: Visit the manufacturer’s website and look for a newer driver or a Windows 10/11 specific version. Many older drivers have been re-signed.
Try compatibility mode: Right-click the installer, go to Properties > Compatibility, and run it in an earlier Windows version mode.

If none of these work, the driver may be genuinely incompatible with your Windows version. In that case, you might need to use older hardware or find a third-party alternative.

Risks and Safety Considerations

Disabling driver signature enforcement weakens your system’s security. An unsigned driver could contain malware or cause instability. Only do this for drivers you trust and have downloaded from the official manufacturer’s site. Never disable signature enforcement permanently—there are registry hacks to do that, but they leave your system vulnerable to kernel-level attacks. The temporary boot method is safer because it reverts automatically.

Also note that the error can appear for other reasons, such as a corrupted driver cache or a Windows update that changed signing policies. If you recently updated Windows and the error appeared, try uninstalling the update first. If the driver is for a printer or audio device, check if the manufacturer has a dedicated uninstaller that removes old drivers completely before reinstalling.

Frequently Asked Questions

Can I permanently disable driver signature enforcement?

Yes, but it’s not recommended. You can use the bcdedit /set nointegritychecks on command in an elevated Command Prompt, or use Advanced Boot options and select Disable driver signature enforcement permanently. However, this leaves your system open to unsigned kernel code, which can be a security risk. It’s better to re-enable it after installing the driver.

Why does the error appear even for drivers from the manufacturer’s website?

Manufacturers sometimes release drivers that are not signed by Microsoft, especially for older hardware or niche devices. The driver may have been signed with a certificate that has expired, or the company never went through Microsoft’s attestation process. The driver itself can be perfectly safe, but Windows still blocks it.

Will this error damage my computer if I ignore it?

No, ignoring the error just means the driver won’t install. Your computer will continue to work normally, but the device won’t function. You can keep using the system without any risk from the driver itself.

Does this error occur on 32-bit Windows?

It’s much less common. 32-bit versions of Windows allow unsigned drivers more freely, though they may still warn you. The strict signature enforcement is primarily for 64-bit systems, which are the standard today.

What if I’m trying to install a driver for a virtual device or a test driver?

If you’re a developer testing a driver, you should use a Windows test-signing mode. Run bcdedit /set testsigning on in an elevated command prompt, then reboot. This allows test-signed drivers. Remember to turn it off with bcdedit /set testsigning off when you’re done.

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 →