Windivert Driver Cannot Be Installed You Must Restart Your Computer Top
The WinDivert (Windows Packet Divert) driver installation often fails with a persistent restart loop if there are orphaned services, conflicting registry entries, or missing dependencies. Because WinDivert is installed "on-demand" by applications
, the error usually indicates the system is unable to initialize its kernel-mode service. Common Fixes for WinDivert Installation Errors
If you are repeatedly prompted to restart but the driver still won't load, try these steps in order: Remove Orphaned Services
: A "zombie" service from a previous version or failed install can block new instances. Run these commands in a Command Prompt as Administrator to force-remove them: sc stop WinDivert sc stop WinDivert1.4 depending on your version) sc delete WinDivert Clear the Registry
: If the service commands don't work, manually delete the registry key. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDivert and delete the entire folder, then your computer. Disable Memory Integrity
: Modern Windows security features can block third-party drivers. Go to Windows Security > Device Security > Core Isolation and try turning off Memory Integrity Verify File Placement
: WinDivert requires specific files to be in the application's home directory to install correctly on-demand. Ensure WinDivert.dll WinDivert.sys WinDivert.inf
are all present in the folder of the program you are trying to run. Check for Conflicts
: Some antivirus or firewall software (like Sophos) is known to block the WinDivert driver. Temporarily disabling these may allow the driver to load. Test-Signing Mode
: If you are using a custom or older build, you may need to enable Test-Signing mode via the command: Bcdedit.exe -set TESTSIGNING ON followed by a Microsoft Support Why does this happen? According to technical discussions on Stack Overflow Open Command Prompt as Administrator
, the "restart required" message is often a generic Windows response to a driver that failed to initialize due to: Architecture Mismatch : Attempting to load a 32-bit driver on a 64-bit system. Missing Privileges : The application calling the driver must be Run as Administrator Virtualization : WinDivert is often incompatible with environments like or certain setups that do not support standard device drivers. Are you getting a specific error code (like 110, 577, or 1275) along with the restart message? A driver can't load on this device - Microsoft Support
Applies To. Security Windows 10 Windows 11. Our free trial of Microsoft 365 is waiting for you. Unlock now. Windows 11 Windows 10. Microsoft Support WinDivert not working on Windows 10 20H2 #253 - GitHub
The "WinDivert driver cannot be installed" error usually stems from corrupted, blocked, or leftover network-filtering drivers from VPNs or gaming tools, often resolved by launching applications with administrator privileges. Immediate fixes include stopping the WinDivert service, removing ASRock RGB software conflicts, or deleting the WinDivert registry key, as detailed on GitHub basil00/WinDivert issues page Stack Overflow AI responses may include mistakes. Learn more
WinDivert: What is the reason behind the error message "error
This blog post addresses the common "WinDivert driver cannot be installed" error often encountered in tools like GoodbyeDPI, ReQrypt, or custom network applications.
How to Fix: WinDivert Driver Cannot Be Installed (Must Restart)
If you are seeing the message "WinDivert driver cannot be installed, you must restart your computer," you’re likely stuck in a loop. Even after rebooting, the same error pops up. This usually happens because an old version of the driver is "ghosting" in your system or a third-party security tool is blocking the installation. Here is how to break the cycle and get it working. 1. Manually Clear the Old Service
The most common cause is a previous instance of WinDivert that didn't shut down properly. Windows thinks it’s still there, so it won’t let a new one install. Open Command Prompt as Administrator. Type the following commands one by one and hit Enter: sc stop WinDivert sc delete WinDivert Use code with caution. Copied to clipboard If you are using a specific version (like 1.4 or 2.0), try: sc stop WinDivert1.4 sc delete WinDivert1.4 Use code with caution. Copied to clipboard Restart your computer immediately after running these. 2. Check for Conflicts (VPNs & Antivirus)
WinDivert is a powerful packet-interception tool, which means some antivirus programs flag it as suspicious.
NordVPN / X-VPN: Some users report that "NordDivert" or similar modules in VPN apps conflict with standard WinDivert. Try closing your VPN entirely before launching your app. This forces a clean driver reload and often
Antivirus: Temporarily disable your real-time protection or add the folder containing WinDivert64.sys to your exclusions list. 3. The Registry "Deep Clean"
If the sc delete command didn't work, you might need to manually remove the service entry from the Windows Registry. Press Win + R, type regedit, and hit Enter.
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDivert Right-click the WinDivert folder and select Delete. Reboot your PC. 4. Verify Your Files
Ensure you aren't missing the core driver files in your application folder. You should see: WinDivert.dll WinDivert64.sys (for 64-bit systems) WinDivert32.sys (for 32-bit systems)
Tip: Some users find success by copying WinDivert64.sys directly into C:\Windows\System32\drivers, though this should usually be a last resort.
Still stuck? Make sure you are always right-clicking your application and choosing "Run as Administrator." WinDivert requires high-level permissions to interact with your network stack.
Are you using a specific program like GoodbyeDPI or a custom script when this happens? WinDivert not working on Windows 10 20H2 #253 - GitHub
To fix the "WinDivert driver cannot be installed" error without a full system restart, you can try manually cleaning up old service entries and files. This error often occurs because a previous version of the driver is stuck in a "zombie" state or its service is pointing to a path that no longer exists Quick Fix Steps Stop and Delete the Service Command Prompt as Administrator
and run these commands to force-remove the existing driver service: sc stop windivert sc delete windivert Note: If you are using version 1.0, the service name may be WinDivert1.0 Clean the Registry
: If the service commands don't work, manually delete the registry key: (Registry Editor). Navigate to: then power on manually.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDivert Right-click and Check for Residual Files : Ensure there aren't conflicting files in your system folders. Search for WinDivert32.sys WinDivert64.sys in your program directory or C:\Windows\System32\drivers
and remove them if they are not in use by your current application. Security Software
: Check if an antivirus (like Sophos or Windows Defender's Core Isolation) is blocking the driver from loading. Review: WinDivert Rating: ★★★★☆ (Powerful but Temperamental)
WinDivert is an exceptional tool for developers and advanced users who need to capture, divert, and drop network packets on Windows without writing complex kernel-mode drivers. WinDivert not working on Windows 10 20H2 #253 - GitHub
1. Restart your computer first
The message explicitly asks for a restart. That often clears file locks and pending driver operations.
Fix 1: Perform a “Full Shutdown” (Not Restart)
Many users click Restart and still see the error. Why? Windows Fast Startup (enabled by default) hibernates the kernel, leaving driver state intact.
Solution:
- Open Command Prompt as Administrator.
- Type:
shutdown /s /f /t 0 - Wait 30 seconds, then power on manually.
This forces a clean driver reload and often resolves the error after a single cycle.
1. The "Real" Restart (Do not skip)
While it sounds obvious, many users attempt to restart but encounter "Fast Startup" issues in Windows 8, 10, and 11, which do not fully clear the kernel memory.
How to perform a clean restart:
- Open the Start Menu.
- Click the Power button.
- Hold the Shift key on your keyboard and click Restart.
- This will bypass the "Fast Startup" cache and perform a full shutdown and reboot.
- Try the installation again immediately after logging back in.