Emergency Windows Server Updates Fix Container Launch Failures

Here is a summary of the main article "New Windows Server emergency updates fix container launch issue" from BleepingComputer:
Summary:

• Microsoft has released emergency, out-of-band (OOB) Windows Server updates to fix a known issue that was causing Windows containers running under Hyper-V isolation mode to fail to launch. This problem was introduced by the 2025.04 B container images released on April 8, 2025, and happened when the update level of the container didn’t match the host’s utility virtual machine (UVM), leading to compatibility problems and startup failures.
• The emergency updates ensure that containers now correctly access the necessary system files from the host, improving reliability and compatibility across different Windows Server versions.
• Impacted OS versions: Windows Server 2019, Windows Server 2022, and Windows Server 2025.
• These updates are not available via Windows Update and must be manually downloaded and installed from the Microsoft Update Catalog using the provided standalone MSU packages.
• Microsoft provides specific guidance for applying the updates with the Deployment Image Servicing and Management (DISM.exe) tool.
• Additional context: Microsoft has had earlier incidents where updates caused issues with Hyper-V VMs on Windows Server, resulting in similar emergency out-of-band fixes.

References for the updates:

• Windows Server 2025 (KB5059087)
• Windows Server 2022 (KB5059092 and KB5059091)

For more details and direct links, see the full article: BleepingComputer source.

---

Source: www.bleepingcomputer.com https://www.bleepingcomputer.com/ne...9AF6BAgJEAI&usg=AOvVaw1gZ3lJ-MLiPVN5Yg042-WI/

 

[ChatGPT]

Here is a summary of the original BleepingComputer article “New Windows Server emergency updates fix container launch issue” (April 17, 2025):

• Microsoft has released emergency updates for Windows Server to fix a critical issue that prevented Windows containers, running under Hyper-V isolation mode, from launching.
• The problem was caused by a mismatch between system file versions in containers and their host (Utility Virtual Machine), which resulted in startup failures for containers.
• With the emergency update, containers can now access necessary system files from the Windows Server host correctly, thus restoring compatibility and reliability.
• Emergency updates are available for:
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025 (specifically KB5059087 for 2025, KB5059092 and KB5059091 for 2022)
• These updates are not automatically delivered via Windows Update—they must be downloaded and installed manually from the Microsoft Update Catalog.
• Microsoft provides instructions on using the DISM (Deployment Image Servicing and Management) tool to apply these updates to running systems or image media.
• Background: Microsoft recently tackled other Windows Server/Hyper-V issues (including authentication bugs and VM start errors in prior security updates).

For additional details and the original guide, see the article here: BleepingComputer article link

---

Source: www.bleepingcomputer.com https://www.bleepingcomputer.com/ne...9AF6BAgJEAI&usg=AOvVaw1gZ3lJ-MLiPVN5Yg042-WI/