Microsoft broke DHCP for Windows Server last Patch Tuesday

Microsoft Acknowledges DHCP Service Disruption Following June Patch Update

In a recent development, Microsoft has acknowledged that the updates released on June 10 during Patch Tuesday may inadvertently disrupt the Dynamic Host Configuration Protocol (DHCP) service on various versions of Windows Server, specifically 2025, 2022, 2019, and 2016. The company has stated that “the DHCP Server service might intermittently stop responding after installing this security update,” which poses a significant challenge for network administrators.

The DHCP service plays a vital role in network management by automatically assigning IP addresses to devices connected to a network. This process allows clients to periodically check in with the server to refresh or renew their IP addresses, ensuring seamless connectivity. While administrators have the option to assign fixed IP addresses, leveraging DHCP simplifies the administrative workload, making it an essential component of networking infrastructure.

Despite its long-standing reliability since the early days of Windows NT, the recent update has left many users frustrated, as evidenced by a surge of complaints on social media platforms. The core issue arises when clients are unable to renew their IP addresses, leading to potential disruptions in network connectivity shortly after the patch installation.

Currently, there appears to be no viable workaround for affected users, other than rolling back the patch—a less than ideal solution given that the update also includes critical security fixes. Microsoft has assured its users that they are actively working on a resolution and will provide further information in the coming days.

It is worth noting that the impact of this issue seems to vary among users. While some have reported significant problems on supported servers, others have experienced no disruptions at all. This discrepancy presents a dilemma for administrators, as the identification of the issue may prompt them to consider postponing the update until a fix is confirmed. The potential ramifications of a network outage could be severe for organizations reliant on stable connectivity.

Moreover, it is a common practice for administrators to test updates in a controlled environment before deploying them in production settings. Given the current circumstances, enterprises are likely to be less forgiving of any disruptions attributed to unverified code from Microsoft, particularly when faced with unexpected connectivity issues.

The June 2025 Patch Tuesday update is quickly becoming a notable case study in the realm of IT management. In addition to the DHCP service complications, Microsoft has also faced challenges with its Surface Hub v1 devices, necessitating an out-of-band update to mitigate further damage. As the situation unfolds, the tech giant’s response will be closely monitored by both users and industry experts alike.

Winsage
Microsoft broke DHCP for Windows Server last Patch Tuesday