Choose the entire folder where your application (e.g., GoodbyeDPI, Requiem, or your specific VPN/proxy tool) is located. 5. Disable Driver Signature Enforcement
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
Ensure that your Windows system and drivers are up-to-date, as outdated versions can cause compatibility issues.
Note: If this fixes the issue, you should look for an updated version of your application that includes a properly signed, modern WinDivert driver, as keeping signature enforcement disabled permanently lowers system security. Conclusion Choose the entire folder where your application (e
now. This ensures the Windows Service Control Manager completely purges the driver from the registry. 3. Disable Driver Blocklists or Core Isolation
Windows maintains a PendingFileRenameOperations registry key (under HKLM\SYSTEM\CurrentControlSet\Control\Session Manager ). If a previous installation attempted to overwrite windivert64.sys but the file was in use, Windows schedules a replacement on next reboot. Subsequent installers detect this pending operation and demand a reboot before proceeding.
Before modifying drivers, ensure no hidden processes are still trying to use WinDivert. Open ( Ctrl + Shift + Esc ). Note: If this fixes the issue, you should
If the error persists after reboot, check driver signature:
Type the following command to delete the service registry entry: sc delete windivert Use code with caution.
If the software was closed improperly during a previous session, the WinDivert driver might still be locked in a "stopping" or "zombie" state. You need to manually terminate it. Press Ctrl + Shift + Esc to open the . after doing this
WinDivert is often "portable" and requires its driver files to be in the same directory as the .exe that calls it. Ensure these three files are in your program folder: WinDivert.dll
WinDivert.exe -uninstall
Look for background processes associated with network bypass tools, VPNs, proxies, or custom firewalls (e.g., goodbyedpi.exe , clash.exe , requiem.exe ). Right-click the process and select .
Sometimes, after doing this, you may need to reset your Windows network stack to clear any leftover issues. You can do this by running the commands netsh winsock reset and netsh int ip reset in an , then restarting.