Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11If Windows blocks an older or test driver, use Disable driver signature enforcement from Startup Settings. In Windows 11 or Windows 10, open Settings > System > Recovery > Advanced startup > Restart now, then choose the Startup Settings option and press F7. The change applies only to that boot session; it is not a permanent repair and should not become your normal security configuration.
What disabling driver signature enforcement actually does
Windows uses driver-signing enforcement to stop kernel-mode drivers without an acceptable cryptographic signature from loading. A driver runs with deep system privileges, so Windows checks that it was signed by an authority trusted through Microsoft’s driver-signing process and that its code has not been altered. The Startup Settings choice temporarily relaxes that load-time check so you can install or test a driver during one troubleshooting session.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The F7 option does not rewrite the driver, approve it permanently, or change the driver’s files. After you restart normally, Windows returns to its standard policy and can block the same driver again. Microsoft’s test-signing documentation states: “This setting doesn’t persist across system restarts.” Treat the option as a controlled diagnostic step, not a routine way to make unsupported hardware work indefinitely.
Use Startup Settings and press F7
This is the appropriate route when you need a single boot with enforcement disabled, such as testing a legacy driver or confirming that a signature check is the reason installation fails. Save open work first. If device encryption or BitLocker asks for a recovery key during the recovery process, have that key available before you begin.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Windows 11 and current Windows 10 path
- Open Settings.
- In Windows 11, select System > Recovery. In Windows 10, open Update & Security > Recovery if that is how your build labels the page.
- Under Advanced startup, select Restart now. Windows will reboot into the Windows Recovery Environment.
- On the recovery screen, select Troubleshoot, then Advanced options.
- Select Startup Settings. If the option is not immediately shown, choose See more recovery options or the equivalent link on your build.
- Select Restart. The next screen lists numbered startup choices.
- Press F7, or press the number assigned to Disable driver signature enforcement. On some keyboards you must hold Fn while pressing F7.
Menu wording and ordering can vary between Windows editions, firmware, and feature updates. Follow the labels displayed on your computer; the important destination is Startup Settings and the choice named Disable driver signature enforcement.
Install or test the driver in that session
Once Windows finishes starting, perform the driver installation or test that was blocked. Use the device maker’s installer or Device Manager’s normal driver-update flow, and record exactly which package and version you used. If the device works only during this boot, that confirms the signature policy is involved but does not establish that the driver is safe or compatible with every Windows update.
Return to normal enforcement
When you are finished, restart Windows normally from the Start menu. Do not select another recovery option to keep the relaxed setting. A normal restart is the boundary that restores the default enforcement behavior.
What the F7 choice does not do
- It is not permanent. The setting is tied to the current system session and is cleared by a normal restart.
- It is not test-signing mode. Test-signing is a separate boot configuration intended for developers who create and validate test-signed kernel drivers.
- It is not a compatibility guarantee. A driver can still fail because it targets an older Windows architecture, lacks required components, conflicts with another driver, or is simply defective.
- It does not bypass every protection. Secure Boot, device security policies, virtualization-based protections, and installer checks can still affect what loads.
If Startup Settings or F7 is missing
Recovery menus look different
Windows may display a blue recovery menu with slightly different labels, especially after a failed boot or on a manufacturer-customized installation. Look for the sequence that leads to Troubleshoot, Advanced options, and Startup Settings. Do not choose System Restore, Startup Repair, or UEFI Firmware Settings unless that is the action you actually intend.
The keyboard does not select F7
Try the number shown beside the option, an external USB keyboard, or the laptop’s Fn key combination. A wireless keyboard may not be initialized early enough in recovery. Connect it before selecting Restart, or use a wired keyboard.
BitLocker requests a recovery key
Recovery operations can trigger a BitLocker key prompt because the boot environment has changed. This is a security check, not evidence that the driver operation failed. Retrieve the recovery key from the organization or account that manages the device. Do not repeatedly guess keys; stop and confirm the correct key first.
The driver still will not load
Check whether the error names a different requirement, such as an incompatible architecture, a missing catalog file, a blocked vulnerable driver, or a device that is disabled in firmware. F7 only addresses the specific signature-enforcement check. Review the exact message in Device Manager or the installer log and obtain a package built for your Windows version and processor architecture.
Test-signing mode: a different tool for driver developers
Developers who build their own test-signed kernel-mode drivers may need Windows test-signing mode. It is designed for repeated development and debugging, not as a consumer replacement for a release-signed driver. Microsoft documents the BCDEdit setting as testsigning [on | off]; changing it requires a restart.
Enable and disable test-signing
From an elevated Command Prompt, the documented form is:
bcdedit /set testsigning onRestart to apply the configuration. When testing is complete, turn it off and restart again:
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
bcdedit /set testsigning offUse this only on a machine and driver build you understand. Test-signing can display a desktop watermark and leaves the system in a development-oriented state until you disable it. It is not equivalent to pressing F7 once, because it changes boot configuration and is intended to remain active across restarts until reversed.
Do not copy nointegritychecks commands casually
BCDEdit also documents nointegritychecks [on | off]. Microsoft states that nointegritychecks cannot be set while Secure Boot is enabled. Boot configuration changes can also require temporarily suspending BitLocker and changing Secure Boot, depending on the option and the machine. A forum command that combines several switches may therefore fail, weaken protection, or leave the computer unable to start as expected. Do not use such combinations as a generic solution to an installer error.
Choose the route that matches your goal
| Route | Primary purpose | How long it lasts | Security posture | Best fit |
|---|---|---|---|---|
| Startup Settings, F7 | One-time troubleshooting or installation test | Current boot session only; cleared by restart | Reduced protection during that session | A user diagnosing whether signature enforcement causes a specific failure |
| Test-signing mode | Development and testing of test-signed kernel drivers | Until the BCDEdit setting is turned off and Windows is restarted | Development configuration; not suitable for routine production use | Driver developers working with their own test certificates and builds |
| Release-signed or WHCP-signed driver | Supported day-to-day operation | Normal Windows operation | Standard integrity protections remain enabled | Anyone who needs the device to work reliably after every reboot |
Why Microsoft recommends keeping enforcement enabled
Kernel Code Integrity helps ensure that kernel drivers retain their integrity and carry a signature from an authority trusted by Microsoft. Disabling that control widens the set of code that can run at kernel privilege, increasing exposure to tampered, malicious, or unstable drivers. Microsoft Support says: “We recommend keeping it enabled and working with driver publishers to obtain WHCP-signed drivers instead.”
That recommendation matters even if F7 solves the immediate installation problem. A driver that loads only when enforcement is disabled may stop working after an update, fail security audits, or introduce crashes that are difficult to diagnose. Keep the temporary session limited to the installation or test, then return to normal startup.
Get a lasting fix from the driver publisher
Identify the exact hardware
Record the device name, hardware ID, Windows edition and version, processor architecture, and the error text. Device Manager can show the hardware ID under Properties > Details > Hardware Ids. This prevents downloading a package for a similar but incompatible revision.
Free tools Windows power users keep installed
One-click scans. No signup required.
Ask for a supported signed package
Contact the device manufacturer or the driver publisher and request a release-signed, WHCP-signed driver for your specific Windows version. Ask whether the package supports Windows 11, Windows 10, or both, and whether a firmware update is required. Keep the installer’s version and release date with your support record.
Remove obsolete packages carefully
If several failed attempts have installed partial packages, use Device Manager’s uninstall option only when you know which device entry is affected. Restart, then install the supported package according to the publisher’s instructions. Do not delete unrelated driver-store entries or disable enforcement globally just to hide a warning.
Replace unsupported hardware when necessary
Some older devices have no maintained signed driver for current Windows releases. If the publisher confirms that no supported package exists, the practical long-term choices are a supported operating-system configuration or hardware with a maintained driver. Windows’ security controls cannot turn an abandoned driver into a supported one.
Windows Driver Policy is not the same as F7
Microsoft’s Windows Driver Policy documentation describes a separate, update-dependent policy transition. For devices with the July 2026 update or later, Microsoft documents an administrator process to remove that policy and a restart to apply the change. Older devices have additional startup protection and require a different procedure involving Secure Boot. Those controls concern policy administration, not the temporary Startup Settings choice.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The policy evaluation criteria include 250 hours of active use and at least three reboot sessions for Windows client devices (two for Windows Server), alongside other requirements. These figures do not control F7 and do not mean that waiting 250 hours will make an unsigned driver load. If an error explicitly identifies Windows Driver Policy, follow the documentation for that policy and your update level rather than substituting the one-boot F7 method.
Quick Recap
A safe decision checklist
- Use F7 only when you need to confirm or work around a signature check for one session.
- Save work and prepare for a possible BitLocker recovery-key prompt before entering recovery.
- Install only the driver package you intended to test, and note its source and version.
- Restart normally as soon as the test is complete.
- Use test-signing only for genuine driver development, and turn it off when development is finished.
- Never assume a command involving
nointegritychecksis harmless; Secure Boot and BitLocker can change the outcome. - For permanent use, obtain a release-signed or WHCP-signed driver from the publisher, or move to supported hardware.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
