Listen to this Post
Introduction
A recent Windows Update has introduced an intermittent failure in the DHCP Server service across multiple Windows Server versions, affecting client IP renewals. Microsoft has acknowledged the issue and is working on a resolution. This article explores the affected systems, temporary workarounds, and best practices for maintaining DHCP reliability.
Learning Objectives
- Identify affected Windows Server versions and updates.
- Apply temporary fixes to stabilize DHCP services.
- Implement monitoring to detect DHCP failures proactively.
1. Affected Systems and Updates
Microsoft has confirmed the issue impacts the following Windows Server versions and updates:
– Windows Server 2016: KB5061010
– Windows Server 2019: KB5060531
– Windows Server 2022: KB5060526
– Windows Server 2025: KB5060842
Actionable Step:
To check if your system has the problematic update, run this PowerShell command:
Get-HotFix -Id KB5061010, KB5060531, KB5060526, KB5060842
If the output shows any of these KBs, your server may experience DHCP instability.
2. Temporary Workaround: Restart DHCP Service
If clients report IP renewal failures, restart the DHCP service:
Restart-Service DHCPServer -Force
Explanation:
This forces the DHCP service to reload, resolving temporary unresponsiveness. Schedule this during maintenance windows to minimize disruption.
3. Monitor DHCP Server Health
Use the following command to check DHCP lease status:
Get-DhcpServerv4Scope -ComputerName [bash] | Get-DhcpServerv4Lease -ComputerName [bash]
Step-by-Step:
1. Replace `
` with your DHCP server’s hostname.</h2>
<ol>
<li>Review the output for leases stuck in "Pending" or "Expired" states. </li>
</ol>
<h2 style="color: yellow;">4. Roll Back the Problematic Update</h2>
If the DHCP issue is critical, uninstall the update:
[bash]
wusa /uninstall /kb:5061010 /quiet
Note: Test this in a non-production environment first.
5. Enable DHCP Audit Logging
Configure logging to track DHCP events:
Set-DhcpServerAuditLog -ComputerName [bash] -Enable $true
Log Location:
`%windir%\System32\Dhcp\AuditLog`
6. Implement DHCP Failover
To mitigate single-point failures, set up DHCP failover:
Add-DhcpServerv4Failover -Name "DHCP-Failover" -PartnerServer [bash] -ScopeId [bash] -SharedSecret "YourSecret"
Best Practice: Use a hot standby server for seamless client transitions.
7. Block the Update via Group Policy
Prevent further installations of the faulty update:
New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Force Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "ExcludeWUDriversInQualityUpdate" -Value 1
What Undercode Say
- Key Takeaway 1: Microsoft’s DHCP bug underscores the importance of testing updates in staging environments before deployment.
- Key Takeaway 2: Proactive monitoring and failover configurations are critical for maintaining network stability.
Analysis:
This incident highlights the fragility of core networking services in Windows Server environments. While Microsoft works on a patch, administrators must balance security updates with operational reliability. Long-term, automating rollback procedures and investing in redundant DHCP architectures can reduce downtime.
Prediction
Future Windows Updates may incorporate more robust pre-release testing for DHCP services. Organizations should prioritize patch management solutions that allow granular control over update deployment.
IT/Security Reporter URL:
Reported By: Charlescrampton Not – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅
