New Windows Server Update Issue: DHCP Service Freezing After Patch Tuesday

Microsoft has recently confirmed a new issue impacting Windows Server systems after installing the latest security updates from June 2024. The problem causes the DHCP (Dynamic Host Configuration Protocol) service to intermittently stop working, which can lead to significant network problems for connected devices.

This is a crucial development for IT administrators, as a malfunctioning DHCP service prevents devices from correctly obtaining or renewing network addresses, potentially disrupting network access and communication. Microsoft is aware of the issue and is currently working on a fix.

What’s Happening with DHCP?

The core issue is that the DHCP Server service on some Windows Server systems may become unresponsive periodically. This happens after applying specific security updates released as part of the June 2024 Patch Tuesday rollout.

When the DHCP service freezes, it struggles to perform its main job: automatically assigning IP addresses and other network settings (like subnet masks and default gateways) to client devices on the network. While existing clients might retain their IP addresses for a while, the problem specifically impacts the renewal process for unicast IP addresses, meaning devices might eventually lose their network configuration or fail to get a new one if needed.

Think of DHCP as the network’s helpful librarian, handing out unique “addresses” (IPs) to every device (computers, phones, printers) so they can find each other and the internet. If the librarian suddenly stops responding, new devices can’t get addresses, and devices whose addresses are expiring can’t renew them, effectively losing their place in the network.

Which Windows Server Versions Are Affected?

Microsoft has identified the specific Windows Server versions and the corresponding updates causing this DHCP issue. The affected platforms include:

  • Windows Server 2022 (KB5039227)
  • Windows Server 2019 (KB5039217)
  • Windows Server 2016 (KB5039220)
  • Windows Server 2012 R2 (KB5039221, KB5039232)

Administrators running these versions who have applied the June 2024 security updates should be aware of this potential problem.

Windows Server logo representing the operating system affected by the recent update issueWindows Server logo representing the operating system affected by the recent update issue

Microsoft Is Working on a Resolution

Fortunately, Microsoft has acknowledged the issue and confirmed that they are developing a fix. According to their update on the security advisories, they are “working on releasing a resolution in the coming days and will provide more information when it is available.”

This means affected organizations will likely need to wait for an upcoming out-of-band update or next month’s Patch Tuesday release to fully resolve the problem without uninstalling the problematic security patches (which isn’t recommended due to security risks).

Not the First Recent Hiccup for Windows Server

This DHCP problem is the latest in a series of issues that have affected Windows Server systems following recent updates. Microsoft has been busy addressing various post-update complications:

  • Just last month, emergency updates were issued to fix a bug causing some Hyper-V virtual machines on Windows Server (and Windows 10/11) to freeze or restart unexpectedly.
  • In April, another set of emergency updates was needed to fix a problem that prevented Windows containers from launching on certain Windows Server versions when using Hyper-V isolation mode.
  • Microsoft also recently fixed authentication problems on domain controllers that were triggered by the April 2024 updates.
  • Additionally, a previous issue that caused some Windows Server 2025 domain controllers to become unreachable after restarts, leading to application or service failures, was also addressed by Microsoft.

This pattern highlights the complexities involved in updating critical server infrastructure and the ongoing need for administrators to stay vigilant and test updates in non-production environments where possible.

Staying Ahead of Server Issues

While waiting for Microsoft’s official fix, administrators experiencing the DHCP issue should monitor their server logs and potentially consider temporary workarounds if network disruption is severe. Keeping up-to-date with Microsoft’s known issues page and security advisories is crucial during these times.

This latest DHCP problem is a reminder that even routine security updates can sometimes introduce unexpected behavior. Stay tuned for further announcements from Microsoft regarding the release of the fix.