/

How to Enable and Disable Driver Verifier in Windows 11 and 10

by Lauren Ballejos, IT Editorial Expert
How to Enable and Disable Driver Verifier in Windows 10 and Windows 11 blog banner image
How to Enable and Disable Driver Verifier in Windows 10 and Windows 11 blog banner image

Try our #1 rated endpoint management platform on G2

NinjaOne dashboard screenshot

Automate the Hardest Parts of IT

Key Points

  • Launch verifier.exe from the Run dialog, Start menu, Task Manager, or an elevated Command Prompt/PowerShell session. You will need administrator rights to do this.
  • Choose “Create custom settings,” select I/O Verification, Force pending I/O requests, and IRP logging, then test non-Microsoft drivers first, since they’re the most common cause of driver-related crashes.
  • Driver Verifier intentionally stresses drivers to detect potential faults, so sluggish performance may occur, and there’s no visible indicator that it’s active.
  • Reopening Driver Verifier and selecting “Delete existing settings,” or running verifier /reset from an elevated Command Prompt or PowerShell.
  • When Driver Verifier causes a boot failure, run verifier /reset from an elevated Command Prompt inside Safe Mode or the Windows Recovery Environment to disable Driver Verifier, then restart Windows.
  • Leaving it enabled longer than needed risks ongoing instability, so disable it as soon as you’ve captured a crash or confirmed the system is stable.

The Windows Driver Verifier is a diagnostic tool built into Windows 11 and Windows 10, which helps you diagnose potential issues with drivers by stress-testing them to detect improper behavior that may lead to system crashes or blue screens. This allows you to identify potentially faulty drivers that may cause system freezing and blue screens so that they can then be updated or removed.

This tutorial demonstrates how to enable and disable Driver Verifier in Windows for overall troubleshooting.

How to open the Windows Driver Verifier

The Windows Driver Verifier is available in all versions of Windows 11 and Windows 10. You will need to be logged in as an administrator to use it.

It is recommended that you create a full backup of your system before you use the Windows Driver Verifier, as it can lead to system instability and crashes that may affect your important data.

There are several methods you can choose from to open the Windows Driver Verifier before configuring and using it.

From the Run dialog or Start menu

You can open the Windows Driver Verifier from the Run dialog:

  • Right-click on the Start button and select Run.
  • In the Run dialog that opens, type the command verifier.exe and then press the Enter key to open the Driver Verifier.

You can alternatively search using the Start menu for verifier and open the Driver Verifier from the search results.

From the Windows Task Manager

You can also open Driver Verifier through Windows Task Manager by following these steps:

  • Press the Ctrl+Shift+Esc key combination to open the Task Manager.
  • On Windows 11, click the Run new task button.
  • On Windows 10, select File > Run new task.
  • In the Run dialog that appears, enter the command verifier.exe, then press OK to open the Driver Verifier.

From the Command Prompt or PowerShell

Open the Command Prompt as an administrator or an elevated PowerShell session, then enter the command verifier.exe.

Improve troubleshooting workflows with automated monitoring and remediaton.

→ Sign up for NinjaOne’s IT management full-access trial

How to enable/turn on the Windows Driver Verifier

While the Driver Verifier is running, it will put extra stress on your drivers in an attempt to get them to fail. This can cause your system to become unstable and use extra resources, possibly making it sluggish. Due to this, you should not leave the Driver Verifier running any longer than necessary to debug system issues.

Note that Driver Verifier does not display an on-screen indicator when active, but you can check its status using verifier /querysettings. Remember to disable it when you’re done troubleshooting.

Once you have opened the Windows Driver Verifier using one of the above methods, you can enable it by following these steps

  • Select Create custom settings (for code developers) and then press Next.

Create custom settings (for code developers) option

  • Check the following options: I/O Verification, Force pending I/O requests, IRP logging, then press Next.

Driver Verifier Manager

  • Choose Select driver names from a list and press Next.

Select driver names from a list

  • After the driver information has loaded, select the drivers you want to verify from the list (it is recommended to start by choosing all non-Microsoft Corporation drivers if diagnosing an unknown issue).

Select driver names from a list

  • Click Finish.
  • You’ll be asked to reboot, after which the Driver Verifier will run in the background until you disable it.

How to disable/turn off the Windows Driver Verifier

If your system crashes immediately after boot, or becomes unresponsive after enabling the Windows Driver Verifier, you may need to use Safe Mode or the Windows Recovery Environment to disable it.

Disable Windows Driver Verifier using the graphical interface

You can disable the Windows Driver Verifier after you have finished troubleshooting by opening the Driver Verifier interface using one of the methods described above, then selecting Delete Existing Settings, and finally clicking the Finish button. Restart your computer to apply the changes.

Delete existing settings

Disable the Driver Verifier via the Command Prompt or PowerShell

You can also execute the following command in the Command Prompt or PowerShell to disable the Windows Driver Verifier:

verifier /reset

Reboot your PC after running this command.

Disable Driver Verifier from Safe Mode

To disable the Driver Verifier from safe mode, follow these steps:

  • Reboot your PC into Safe Mode.
  • Once in Safe Mode, follow the instructions above for disabling the Windows Driver Verifier using the command prompt or PowerShell.
  • Reboot your Windows PC normally.

Disable Driver Verifier from the Windows Recovery Environment (WinRE)

You can also disable the Windows Driver Verifier from the Windows recovery environment if it is causing your device to fail to boot:

  • If your system fails to boot several times in succession, it will automatically enter the Windows recovery environment (alternatively, you can hold the shift key while selecting restart from the start menu to reboot into WinRE).
  • In the Windows Recovery environment, select Troubleshoot, and then Advanced Options.

Select Troubleshoot

  • Open the Command Prompt.

Select Advanced options

  • Your PC will reboot, and you will be prompted to enter the login credentials for an administrative user.
  • When the command prompt appears, enter the command verifier /reset.
  • Reboot your device.

Empower your IT team with a cross-platform, single-click remote access software.

💡 Learn more about NinjaOne Remote®

Diagnosing Windows system stability and driver issues remotely

NinjaOne provides tools for remotely monitoring, detecting, and remediating system stability issues, including problems with drivers on Windows 11 and Windows 10 devices.

You can collect information about system instability (including crashes and blue screens), and deploy supported driver updates or configure automatic remediation steps, helping you identify and address issues remotely, potentially before users need to contact your help desk.

FAQs

You should only leave the Driver Verifier running for up to 24 to 48 hours or until your system crashes. Do not run Driver Verifier permanently, as doing so can lead to unexpected instability, performance degradation, and frequent blue screen crashes. This is because Driver Verifier intentionally stresses drivers, especially if you have any non-Microsoft ones, to expose faults. Leaving it enabled beyond the troubleshooting window can disrupt normal operations

Yes. Driver Verifier deliberately stresses installed drivers with tighter memory checks, forced I/O requests, and other extreme conditions to expose bugs that wouldn’t surface during normal use, and any driver that fails produces an immediate blue screen rather than a quiet error.

No. Driver Verifier should only run on individual devices you’re actively troubleshooting, not on production systems or machines people rely on for daily work. Because it intentionally forces crashes to catch faulty drivers, leaving it enabled on a production machine risks unplanned downtime, data loss from unsaved work, and repeated blue screens that disrupt the user rather than help IT.

If your PC becomes unresponsive or fails to boot after enabling Driver Verifier, start Windows in Safe Mode or access the Windows Recovery Environment (WinRE). If Windows is accessible, hold Shift while selecting Restart to enter WinRE. Otherwise, Windows may automatically enter recovery mode after repeated startup failures. Open Command Prompt with administrator privileges and run verifier /reset, then restart your PC to apply the changes.

You might also like

Ready to simplify the hardest parts of IT?

NinjaOne Terms & Conditions

By clicking the “I Accept” button below, you indicate your acceptance of the following legal terms as well as our Terms of Use:

  • Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms.
  • Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party.
  • Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library belonging to or under the control of any other software provider.
  • Warranty Disclaimer: The script is provided “as is” and “as available”, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations.
  • Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks.
  • Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script.
  • EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).