Why DNS Client Service Stops Itself After 24H2 in Windows 11

After installing the Windows 11 24H2 update, some business users find the DNS Client service stops automatically minutes after startup. This causes web pages to fail to load, VPN connections to drop, and internal network resources to become unreachable. The root cause is a compatibility change in the 24H2 servicing stack that conflicts with certain third-party security or network filtering drivers. This article explains why the service stops, provides a step-by-step fix, and covers related failure patterns you may encounter.

Why the DNS Client Service Stops After 24H2

The DNS Client service, also known as Dnscache, caches DNS lookups to speed up name resolution. After the Windows 11 24H2 update, the servicing stack introduces stricter memory integrity checks and driver signature enforcement. Third-party network filtering drivers — such as those from VPN clients, advanced firewall suites, or parental control software — may not fully comply with these new checks. When the driver loads and interacts with the DNS Client service, the service detects an instability or security violation and stops itself to prevent further system disruption. The service does not restart automatically because its default recovery settings in Windows 11 24H2 are set to “Take No Action” for the first failure.

What Changed in 24H2

Microsoft hardened the kernel-mode driver environment in 24H2 by enabling mandatory driver signing and deprecating older hash-based signature algorithms. Drivers that use legacy signatures or that hook into the DNS resolution stack without updated certificates trigger a service crash. The DNS Client service is a protected service, so it stops rather than allowing a potentially malicious driver to continue operating.

Which Drivers Are Affected

Common drivers that cause this issue include those from Cisco AnyConnect, Check Point Endpoint Security, McAfee Web Gateway, and some corporate proxy clients. If you run any software that intercepts DNS traffic at the kernel level, it is likely affected.

Steps to Fix the DNS Client Service Stopping After 24H2

1. Check the DNS Client service status
   Open Services.msc by pressing Win + R and typing services.msc. Locate “DNS Client” and verify that its Status is blank and Startup Type is Automatic. If the service is stopped, right-click it and select Start.
2. Set the service recovery options
   Right-click DNS Client and select Properties. Go to the Recovery tab. Set First failure, Second failure, and Subsequent failures to “Restart the Service.” Set Reset fail count after to 1 day. Click Apply and OK.
3. Verify the startup type is Automatic
   In the DNS Client Properties General tab, ensure Startup type is set to Automatic. If it was changed to Manual or Disabled, select Automatic, click Apply, and then Start the service.
4. Identify the conflicting driver
   Open Event Viewer by pressing Win + X and selecting Event Viewer. Navigate to Windows Logs > System. Look for Error events with Source “Service Control Manager” and Event ID 7034 or 7031 that reference Dnscache. Note the Module name or Driver name in the event details.
5. Update or disable the conflicting driver
   Contact your software vendor for an updated driver compatible with Windows 11 24H2. As a temporary workaround, disable the driver by opening Device Manager, expanding Network adapters, right-clicking the related virtual adapter, and selecting Disable device. Restart your computer.
6. Disable Mandatory ASLR for the driver
   Open Windows Security. Go to App & browser control > Exploit protection > System settings. Scroll to “Force randomization for images (Mandatory ASLR).” Click Edit, then clear the check box for the specific driver executable. This step requires Advanced IT admin knowledge and should be tested in a lab first.
7. Restart the DNS Client service from Command Prompt
   Open Command Prompt as Administrator. Type net stop Dnscache && net start Dnscache and press Enter. This forces the service to restart immediately.

Related Failure Patterns After 24H2

VPN Client Fails to Resolve Internal Hostnames

If the DNS Client service stops, your VPN client cannot resolve internal domain names. The VPN connection appears active but you cannot ping or access servers by name. To verify, run nslookup internal-server-name in Command Prompt. If it returns “DNS request timed out,” the DNS Client service is likely stopped. Follow the recovery steps above and then restart the VPN client.

Web Browsers Show DNS_PROBE_FINISHED_NO_INTERNET

Even with a working internet connection, browsers display this error when the DNS Client service is not running. The browser cannot resolve domain names locally. Check the service status and start it. If the error persists, flush the DNS cache by running ipconfig /flushdns in Command Prompt as Administrator.

Network Discovery Stops Working in File Explorer

When the DNS Client service stops, Network Discovery cannot resolve other computers on the local network. File Explorer shows no devices under Network. Restart the service and then enable Network Discovery by going to Settings > Network & internet > Advanced network settings > Advanced sharing settings > Turn on network discovery.

DNS Client Service Recovery Options Comparison

Item	Default 24H2 Behavior	Recommended Fix Behavior
First failure action	Take No Action	Restart the Service
Second failure action	Take No Action	Restart the Service
Subsequent failures action	Take No Action	Restart the Service
Reset fail count after	86400 seconds (1 day)	86400 seconds (1 day)
Startup type	Automatic	Automatic

The table shows that the only change needed is the recovery action. The startup type and reset interval remain appropriate for business environments.

You can now identify why the DNS Client service stops after the 24H2 update and apply the recovery settings to keep it running. Next, check your third-party network drivers for compatibility with 24H2. For advanced protection, consider using the built-in Windows Defender Firewall with DNS-over-HTTPS enabled in Settings > Network & internet > DNS server assignment > Edit > Preferred DNS encryption.