Disabling Defender services like WinDefend, WdBoot, WdFilter, WdNisSvc, WdNisDrv, and MDCoreSvc is NOT a reliable or clean way to prevent Defender from scanning anything, especially temporarily. These services are tightly integrated with Windows security infrastructure and protected by Tamper Protection, service hardening, and kernel-mode drivers.
| WinDefend | Core Microsoft Defender Antivirus service |
| WdBoot | Boot-time protection driver |
| WdFilter | Real-time scanning filter driver |
| WdNisSvc | Network Inspection Service |
| WdNisDrv | Network Inspection Driver |
| MDCoreSvc | Microsoft Defender Core Service (used in newer builds) |
Why disabling them is problematic
Tamper Protection blocks service manipulation, even from SYSTEM-level processes unless you unload WdFilter.sys and modify registry keys in Safe Mode.
Disabling services via registry (Start=4) or permissions hacks can break Defender in unpredictable ways, potentially causing:
- Update failures
- Broken Windows Security UI
- Inability to re-enable Defender cleanly
Re-enabling them requires rebooting and restoring multiple registry keys, which is messy and error-prone.
What actually happens when you install ESET (or any third-party AV)
Microsoft Defender Antivirus (WinDefend) enters passive mode, not disabled.
Core services like WdFilter and WdBoot may remain loaded, especially for compatibility and fallback.
Tamper Protection remains active unless manually disabled.
Windows Security Center still monitors Defender status, and Defender can reassert itself if ESET is uninstalled or fails.
So yes, Defender steps aside, but it's not disabled in the sense that those services are removed or neutered. It's more like a bouncer letting another guard take the shift—but still watching from the corner.
Why "Just disable services" is a dangerous mentality
Disabling services manually is like pulling fuses out of your car because you don't like the dashboard lights. Sure, it might stop the blinking, but now your airbags won't deploy.
Here's what people forget:
Windows services are interdependent.
Disabling one can cause cascading failures in:
- Updates
- Security features
- Device drivers
- Event logging
- Network stack
And worst of all: Windows doesn't always fail gracefully. It might seem fine until one day, you'll learn it the hard way the fact that Defender is so deeply interwoven with the whole Windows OS that microscopic fps improvements that can be measured in the 0.1% lows of
some games titles with "optimizations" are for those who will insist on the benefits of carrying water to the sea. So much so, we even have a name for it. It's called "optimization theater", and I have seen lots of it. The popcorn industry loves it to bits. Literally.