Services Known to Conflict with WinDivert in Zapret: How to Identify and Fix Them

The most common WinDivert conflicts in Zapret come from Adguard, Killer networking software, Intel Connectivity services, Check Point security, SmartByte, VPN clients, and other WinDivert-based bypasses like GoodbyeDPI, all of which can be detected and removed using the built-in service.bat diagnostics.

Flowseal/zapret-discord-youtube relies on the WinDivert driver to intercept and modify network packets. When another application installs a competing low-level network filter, the driver cannot bind to the network stack and the bypass fails. The repository includes a diagnostic routine in service.bat that automatically checks for these services known to conflict with WinDivert and offers to remove them.

Why WinDivert Conflicts Occur

WinDivert operates at the Windows Filtering Platform (WFP) layer. Only one driver can occupy a specific packet-filtering slot at a time. If a security suite, VPN, or network-optimization tool has already registered a hook, WinDivert64.sys fails to load. This results in connection errors or silent failures when launching Zapret.

Specific Services That Block WinDivert

The service.bat script (lines 53-136 and 564-630) maintains an allowlist of known incompatible services. When you run diagnostics, it checks for the following processes and drivers:

Adguard (AdguardSvc.exe)

Detected in service.bat at lines 53-60. Adguard’s network filter occupies the same WFP layer WinDivert requires.

Resolution: Stop and delete the service:

sc stop AdguardSvc
sc delete AdguardSvc

Alternatively, uninstall Adguard completely.

Killer Networking Software (Killer)

Detected in service.bat at lines 63-70. The Killer driver loads a packet-filtering module that prevents WinDivert’s driver registration.

Resolution: Remove the service:

sc stop "Killer"
sc delete "Killer"

Intel Connectivity Network Service

Detected in service.bat at lines 73-80. This Intel utility installs a low-level network filter that clashes with WinDivert.

Resolution: Stop and delete the service:

sc stop "Intel Connectivity Network Service"
sc delete "Intel Connectivity Network Service"

Check Point Security (TracSrvWrapper, EPWD)

Detected in service.bat at lines 83-99. Check Point products load their own packet-filter drivers that block WinDivert.

Resolution: Stop and delete the wrapper service:

sc stop TracSrvWrapper
sc delete TracSrvWrapper

If the service persists, uninstall the Check Point component from Control Panel.

SmartByte

Detected in service.bat at lines 103-110. SmartByte’s network-optimization driver conflicts with WinDivert’s packet interception.

Resolution: Disable the service:

sc stop SmartByte
sc delete SmartByte

VPN Clients (Generic)

Detected in service.bat at lines 119-136. Virtual adapters from VPN software can prevent WinDivert from binding to the network stack.

Resolution: Shut down all VPN clients and disable virtual adapters:

netsh interface set interface "OpenVPN" admin=disable

Replace "OpenVPN" with the actual name of your VPN adapter.

Other WinDivert-Based Bypasses (GoodbyeDPI, discordfix_zapret, winws1, winws2)

Detected in service.bat at lines 564-630. These tools also use WinDivert; only one instance can be loaded simultaneously.

Resolution: Use the Run Diagnostics option in service.bat to automatically stop and delete these services, or manually run:

sc stop GoodbyeDPI
sc delete GoodbyeDPI

Automated Detection with service.bat

The fastest way to identify conflicts is to use the built-in diagnostics:

1. Run service.bat from an elevated command prompt.
2. Select option 10 (Run Diagnostics).
3. The script checks for every service listed above and prints coloured warnings (e.g., call :PrintRed "[X] Killer services found. Killer conflicts with zapret").
4. When prompted, allow the script to execute net stop and sc delete commands automatically.

If a service cannot be removed automatically because it is protected by its parent application, the script will instruct you to uninstall the software manually via Settings > Apps.

Manual Resolution Steps

If you prefer manual intervention or the automated removal fails, use these standard Windows service commands.

Stop and remove a specific conflicting service:

sc stop "ServiceName"
sc delete "ServiceName"

Disable a VPN adapter by name:

netsh interface set interface "AdapterName" admin=disable

Verify WinDivert can load after cleanup by checking the bin/WinDivert64.sys driver status or simply re-launching service.bat and selecting the start option.

Summary

• WinDivert requires exclusive access to the Windows Filtering Platform; only one low-level filter can operate at a time.
• Known conflicts include AdguardSvc.exe, Killer, Intel Connectivity Network Service, Check Point (TracSrvWrapper), SmartByte, VPN clients, and other bypass tools like GoodbyeDPI.
• Detection is automated via service.bat (lines 53-136 and 564-630) using the Run Diagnostics menu.
• Resolution typically involves running sc stop followed by sc delete for the offending service, or uninstalling the parent application entirely.

Frequently Asked Questions

Can I run Zapret with a VPN active?

Generally no. VPN clients install virtual network adapters and filtering drivers that occupy the same network layer as WinDivert. You must shut down all VPN services (sc stop or disable adapters) before starting Zapret. Some users report success with split-tunneling configurations, but standard operation requires the VPN to be disabled.

Why does Adguard specifically block WinDivert?

Adguard uses the Windows Filtering Platform to inspect HTTPS traffic for ad blocking. Because it registers at the same driver level as WinDivert (as seen in service.bat lines 53-60), the two cannot coexist. You must remove or disable Adguard’s service (AdguardSvc.exe) to free the WFP slot for Zapret.

How do I know if a service is conflicting without running diagnostics?

Symptoms include immediate connection failures when launching Zapret, error messages about driver installation, or silence in the console logs. The definitive method is to run service.bat and select Run Diagnostics (option 10), which explicitly checks service.bat lines 53-136 for the known conflicting service signatures.

Is it safe to delete these Windows services?

Deleting services like Killer, SmartByte, or Intel Connectivity removes network-optimization features but will not break core Windows networking. Always stop the service first (sc stop) to test stability before deleting it (sc delete). If you encounter issues, you can reinstall the parent software later. System-critical services cannot be deleted this way, so the command is safe for the third-party applications listed.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}