How to disable driver signature enforcement on Windows 11

Windows 11 blocks unsigned drivers by default to protect system integrity.
You can temporarily disable enforcement using Advanced Startup (WinRE).
Press F7 during Startup Settings to allow unsigned driver installation.
Group Policy offers a more persistent way to allow unsigned drivers.

On Windows 11, you can disable “driver signature enforcement” to install unsigned drivers through the Windows Recovery Environment (WinRE). This security feature ensures that only drivers signed by Microsoft are permitted, safeguarding system integrity.

While it’s recommended to verify the integrity and publisher of any driver to prevent potential system instability or security risks, there are scenarios where installing an unsigned driver may become necessary. For instance, you might need to install an older driver version from a trusted source, use a device lacking a signed driver from its manufacturer, or test a custom, unsigned driver.

Regardless of the reason, Windows 11 includes different ways to disable signature enforcement to install unsigned drivers using recovery settings during startup. However, consider that disabling driver signature enforcement can expose your system to potential security threats. Always ensure that any unsigned drivers you install are from trusted sources.

In this guide, I’ll show you how to disable signature enforcement to allow installing unsigned drivers on Windows 11.

Disable driver signature enforcement on Windows 11 from Advanced Startup
Disable driver signature enforcement on Windows 11 from Group Policy
Pureinfotech’s Take
FAQs about disabling driver signature enforcement on Windows 11

Disable driver signature enforcement on Windows 11 from Advanced Startup

To disable signature enforcement on Windows 11, disable BitLocker (Device Encryption) if applicable, and follow these steps:

1. Open Settings on Windows 11.
2. Click on System.
3. Click the Recovery page.
4. Click the Restart now button for the “Advanced startup” setting under the “Recovery options” section.
5. Click the Restart now button one more time.
6. Click on Troubleshoot.
7. Click on Advanced options.
8. Click on Startup Settings.
9. Click the Restart button.
10. Press “F7” or the “7” key to select the Disable driver signature enforcement option.

Once you complete the steps, Windows 11 will boot normally but with the signature enforcement feature turned off, allowing you to install unsigned drivers on the computer. After the installation, during the next reboot, the driver signature enforcement will be enabled once again, and you’ll need to repeat the instructions to install another driver (if applicable).

Disable driver signature enforcement on Windows 11 from Group Policy

To turn off driver signature enforcement from Group Policy, follow these steps:

Open Start.
Search for gpedit and click the top result to open the Group Policy Editor.

Browse to the following path:

User Configuration > Administrative Templates > System > Driver Installation

Right-click the “Code Signing for Driver Packages” policy and choose the Edit option.
Choose the Enabled option.
Select the Ignore option under the “Options” section to allow the system to proceed with the installation of unsigned drivers.
Click the Apply button.
Click the OK button.
Restart the computer

After you complete the steps, you should be able to install unsigned drivers on the device.

If you want to revert the changes, you can use the same instructions, but in step 5, select the “Not configured” option.

Bcdedit disable driver signature error / Image: Mauro Huculak

You may also use the bcdedit /set testsigning on or the bcdedit /set nointegritychecks on command to disable the security feature. However, since Windows 11 uses Secure Boot, you may encounter errors and other problems running these commands.

Pureinfotech’s Take

Disabling driver signature enforcement on Windows 11 is one of those features that sits at the intersection of flexibility and risk. By design, the system blocks unsigned drivers to maintain stability and prevent malicious code from running at the kernel level. That protection is critical, especially on modern systems where security is tightly integrated with features like Secure Boot.

However, the reality is that not every scenario fits neatly within Microsoft’s rules. If you’re working with legacy hardware, testing custom drivers, or relying on software that hasn’t been updated with proper signatures, this safeguard can quickly turn into a blocker. That’s where the Advanced Startup method becomes the most practical option. It’s temporary, controlled, and resets automatically after reboot, which makes it the safest way to bypass the restriction when you only need a one-time installation.

The Group Policy route, on the other hand, is better suited for power users and network administrators who need a more persistent configuration. It removes friction from repeated installations but also lowers the system’s security baseline, so it should be used with clear intent and only in trusted environments.

The command-line methods using bcdedit sound appealing, but on modern Windows 11 setups, they’re increasingly unreliable due to Secure Boot enforcement. In most cases, they either fail outright or introduce unnecessary complexity compared to the built-in recovery options.

Ultimately, the takeaway is that Windows 11 provides tools to bypass driver signature enforcement, but it expects you to use them responsibly. If you’re not absolutely sure about the source of a driver, forcing it onto the system is rarely worth the potential instability or security exposure.

FAQs about disabling driver signature enforcement on Windows 11

Here’s a list of frequently asked questions (FAQs) and answers about temporarily turning off driver signature enforcement on Windows 11.

What is driver signature enforcement on Windows 11?

Driver signature enforcement is a security feature on Windows 11 that only allows drivers signed by Microsoft to install and run. This helps protect system integrity by blocking unverified or potentially malicious drivers from accessing the kernel and causing instability or security vulnerabilities.

Why does Windows 11 block unsigned drivers?

Windows 11 blocks unsigned drivers to prevent unverified code from running at a low system level. Since drivers interact directly with hardware and the kernel, unsigned versions could introduce malware, crashes, or performance issues, making this restriction essential for maintaining system security and reliability.

How do I disable driver signature enforcement on Windows 11?

You can disable driver signature enforcement by booting into Advanced Startup (WinRE), navigating to Startup Settings, and pressing F7. This temporarily allows unsigned drivers to install. The setting resets automatically after reboot, making it the safest method for one-time installations.

Does disabling driver signature enforcement permanently affect Windows 11?

No, disabling driver signature enforcement through Advanced Startup is temporary and only applies to the current session. After restarting your computer, Windows 11 automatically re-enables the feature, restoring the default security protections without requiring manual intervention.

How do I permanently allow unsigned drivers on Windows 11?

You can allow unsigned drivers more persistently using the Group Policy Editor by enabling the “Code Signing for Driver Packages” policy and selecting “Ignore.” This change reduces security restrictions, so it should only be used in controlled environments or when you fully trust the driver source.

Which is better for disabling driver signature enforcement, Advanced Startup or Group Policy?

Advanced Startup is better for temporary, one-time driver installations because it automatically restores security after reboot. Group Policy is more suitable for repeated use, as it persistently allows unsigned drivers, but it reduces overall system protection and should be used cautiously.

Why don’t bcdedit commands work to disable driver signature enforcement on Windows 11?

Bcdedit commands often fail on Windows 11 because Secure Boot blocks changes that weaken system security. Features like testsigning or nointegritychecks may be ignored or trigger errors, making Advanced Startup or Group Policy the more reliable methods for disabling driver signature enforcement.

Update April 22, 2026: This guide has been updated to ensure accuracy and reflect changes to the process.

Thank you for your feedback!

Tell me why, so I can fix it