How to Fix DHCP Server Freezing After June 2025 Windows Update

Introduction

In June 2025, Microsoft rolled out several cumulative updates across its Windows Server platforms including Windows Server 2016, 2019, 2022, and the newer 2025 edition. These updates were designed to improve system stability, patch known security vulnerabilities, and offer performance enhancements. But instead of bringing relief, they introduced a frustrating and disruptive issue for many IT administrators: DHCP Server services began to freeze or crash unexpectedly.

For organizations relying on dynamic IP address assignments, a non-functioning DHCP service isn’t a minor glitch it’s a network-wide disruption. If you’ve been experiencing DHCP server freeze-ups after installing these updates, you’re not alone and this blog is here to walk you through why it’s happening and, more importantly, how to fix it.

Understanding the Problem

After installing one of the following updates:

• KB5061010 – Windows Server 2016
  
• KB5060531 – Windows Server 2019
  
• KB5060526 – Windows Server 2022
  
• KB5060842 – Windows Server 2025
  

many users began reporting that their DHCP server became unresponsive, especially during heavy load times or after a server reboot.

Common symptoms include:

• DHCP snap-in fails to launch or shows “Not Responding”
  
• IP address leases are not being assigned
  
• Clients fall back to APIPA addresses (169.x.x.x)
  
• Event Viewer logs show Event IDs 10020, 10050, or timeouts
  
• Hyper-V environments showing increased DHCP latency
  

Why This Is Happening

Microsoft has acknowledged that a bug in these cumulative updates is causing DHCP server instability. The issue appears to stem from:

• Improper memory handling during service start
  
• Service dependency mismanagement, where DHCP may wait indefinitely for other services like RPC or Netlogon
  
• Conflicts with domain controller or Hyper-V services, especially on servers running multiple roles
  

What’s troubling is that this problem affects servers even after clean boots, indicating it’s not just a local cache or misconfiguration issue it’s a systemic problem with how the update interacts with core networking components.

7 Step-by-Step Fixes That Work

Let’s move into solutions. Below are seven carefully structured steps that can help you fix, mitigate, or temporarily work around the DHCP server freeze issue on your Windows Server.

1. Restart the DHCP Service (Short-Term Relief)

Sometimes, a simple service restart can temporarily unfreeze the DHCP service:

Using Command Prompt:

bash

CopyEdit

net stop dhcpserver

net start dhcpserver

Or via GUI:

1. Press Win + R → type services.msc
   
2. Locate DHCP Server → Right-click → Click Restart
   

Note: This doesn’t address the root cause but can restore functionality briefly.

2. Roll Back the Update (When Stability is Critical)

If your DHCP Server is mission-critical, it’s safer to uninstall the update until Microsoft provides an official patch.

Using PowerShell:

powershell

CopyEdit

wusa /uninstall /kb:5060842 /quiet /norestart

Replace the KB number based on your version (e.g., 5060531 for Server 2019).

After uninstalling, reboot the server and monitor DHCP functionality.

3. Check for Emergency Hotfix or Out-of-Band Update

Microsoft sometimes releases out-of-band (OOB) updates to quickly address major bugs.

• Visit: Windows Update Catalog
  
• Search the problematic KB number (e.g., KB5060842)
  
• Monitor TechNet or Microsoft Learn for any new KB patches or registry-based workarounds
  

As of June 20, 2025, no hotfix has been officially released, but updates may drop soon.

4. Isolate DHCP Role (Best Practice in Complex Setups)

If DHCP is installed on a multi-role server (e.g., Domain Controller + DNS + DHCP), consider migrating the DHCP role to a dedicated server. Here’s why:

• Less competition for network resources
  
• Reduced likelihood of service conflicts
  
• Better logging and performance monitoring
  

You can use Windows Server Manager → Add Roles & Features → Move DHCP role to a new server.

5. Enable Verbose DHCP Logging for Diagnosis

To better understand the failure pattern:

Registry Tweak:

1. Press Win + R, type regedit
   
2. Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Parameters

3. Right-click → New → DWORD (32-bit) Value → Name it: EnableAuditLog → Set Value = 1
   
4. Restart the DHCP service
   

Now, check the logs located at:
%SystemRoot%\System32\Dhcp\DhcpSrvLog-*.log

This will help identify exactly when and why the service is freezing.

6. Temporarily Use Static IPs (As a Fallback Plan)

While not ideal long-term, you can assign static IPs to your critical infrastructure (servers, printers, cameras) to reduce DHCP load and minimize operational risks.

• Go to Network Settings → IPv4 → Manual IP Configuration
  
• Use a consistent range outside your DHCP scope
  

This helps maintain connectivity even if DHCP continues to fail.

7. Contact Microsoft Support with Logs and Diagnostics

If you’ve tried everything and DHCP is still failing, open a ticket with Microsoft and provide:

• DHCP logs from C:\Windows\System32\Dhcp
  
• Event Viewer snapshots (Application + System logs)
  
• Update history (run Get-HotFix in PowerShell)
  
• Network configuration (via ipconfig /all and Get-NetIPConfiguration)
  

Microsoft may provide a private hotfix or registry-level workaround before public release.

Best Practices for Future Updates

While bugs happen, proactive steps can prevent widespread disruption in production environments:

1. Always Stage Updates

Use Windows Server Update Services (WSUS) or Microsoft Intune to test updates in sandboxed environments before pushing them to production servers.

2. Backup Before Patch Tuesday

Perform a System State Backup of domain controllers and DHCP servers before applying monthly updates.

3. Deploy a DHCP Failover Partner

Enable DHCP failover between two servers (Split Scope or Load Balanced) so if one fails, the other continues to assign IPs.

4. Subscribe to Microsoft’s Known Issues Feed

Keep tabs on real-time bugs at the Microsoft Release Health Dashboard

Conclusion

The DHCP server freezing issue caused by June 2025’s cumulative Windows updates is a reminder that even the most routine patches can carry unexpected consequences. For businesses large and small, dynamic IP allocation is a foundational service, and when it goes down, everything else suffers.

But the good news is: you’re not helpless. By rolling back updates, isolating DHCP roles, enabling verbose logging, and preparing your network for redundancy, you can safeguard your systems against these disruptive glitches.

Until Microsoft officially patches this bug, use the steps above as your action plan — and stay one step ahead of chaos.