Sometimes, Windows will block you from installing an unsigned driver, which is a driver you’ve downloaded elsewhere other than through a Windows Update or the device manufacturer’s website. But if you need the driver, and you know it is perfectly safe, you can turn off driver signature enforcement and let it through.
In this guide, we’re going to show you several ways to do it.
How to Disable Driver Signature Enforcement in the Startup Settings
A temporary way to disable driver signature enforcement is through Startup Settings, allowing you to install the unsigned drivers. However, the moment you restart your PC, Windows will re-enable driver signature enforcement. The unsigned drivers you’ve installed will still work, but you may not be able to install new ones.
To disable driver signature enforcement this way, you’ll have toaccess the Startup Settings screen. TheDisable driver signature enforcementoption will be the seventh one, so pressF7or7on your keyboard to select it.
Your computer will then restart, and when it reboots, you’ll be able to install those unsigned drivers.
How to Disable Driver Signature Enforcement in the Local Group Policy Editor
you may also disable driver signature enforcement by tweaking theCode signing for driver packagespolicy in the Local Group Policy Editor (LGPE). Doing this will allow you to install unsigned drivers even if you restart your computer.
Unfortunately, you’re able to only natively access the LGPE if you’re on Windows Pro or Enterprise Edition. However, there is a way toaccess the LGPE on Windows Home.
If you want to enable driver signature enforcement again, go back to step #4 and set the radio button toNot configured.
How to Disable Driver Signature Enforcement in PowerShell
Another way to disable driver signature enforcement is by running the command to turn off integrity checks in PowerShell (you’ll have to run it as an administrator). And just like with the Local Group Policy Editor, it will remain disabled until you enable it again.
Follow the steps below to turn off driver signature enforcement in PowerShell:
you’re able to disable driver signature enforcement byopening Command Prompt as an administratorif you prefer it over PowerShell.
To turn on driver signature enforcement again, replace the command in step #3 withbcdedit /set nointegritychecks off.
One potential problem you may run into when trying to turn off driver signature enforcement this way is an error statingThe value is protected by Secure Boot policy and cannot be modified or deleted.
If that is the case, you can tryturning off Secure Bootand trying again. But if you don’t want to do this, using Startup Settings and the Local Group Policy Editor is perfectly okay.
You can also put Windows in test mode, which disables driver signature enforcement, allowing you to install those unsigned drivers. To enter test mode, follow the steps below (keep in mind that you may run into the Secure Boot error):
Now restart your computer, and when it boots back up, it will be in test mode. After you’re done installing those drivers, don’t forget to disable test mode. The command to do that isbcdedit /set testsigning off.
Now You Can Install Unsigned Drivers on Windows
Installing unsigned drivers on Windows is not recommended, since they can lead to unexpected behavior. However, if you trust the driver, there’s no reason why the OS should block you from installing it. Just use one of the methods mentioned above, and you should be able to install and use unsigned drivers on your Windows PC.
