Microsoft acknowledged a brand new challenge brought on by the June 2025 safety updates, inflicting the DHCP service to freeze on some Home windows Server techniques.
On Home windows Server techniques, the Dynamic Host Configuration Protocol (DHCP) Server service automates assigning IP addresses and different community configurations, decreasing community administration and making certain dependable IP deal with configuration in Home windows networks.
In affected environments, the brand new DHCP recognized challenge confirmed by Microsoft over the weekend prevents renewals of unicast IP addresses from making use of accurately throughout community units.
“The DHCP Server service may intermittently cease responding after putting in this safety replace. This challenge impacts IP renewal for purchasers,” the corporate says in updates added to safety advisories issued throughout this month’s Patch Tuesday.
The listing of affected Home windows variations and the updates inflicting this challenge contains:
“We’re engaged on releasing a decision within the coming days and can present extra data when it’s out there,” Microsoft added.
Throughout this month’s Patch Tuesday, Redmond addressed one other recognized Home windows Server challenge that triggered app or service failures after inflicting some Home windows Server 2025 area controllers to grow to be unreachable after restarts.
The June 2025 cumulative updates additionally mounted authentication issues on Home windows Server area controllers triggered after deploying the April 2025 safety updates.
In Could, Microsoft additionally issued out-of-band updates to handle a bug inflicting some Hyper-V digital machines with Home windows 10, Home windows 11, and Home windows Server to restart or freeze unexpectedly.
One month earlier, the corporate launched one other set of emergency updates that resolved a recognized challenge stopping Home windows containers from launching on Home windows Server 2019, Home windows Server 2022, and Home windows Server 2025 techniques.
These launch issues affected solely containers underneath Hyper-V isolation mode, permitting a number of containers to run concurrently on a single Home windows host inside separate digital machines.