KB5059087: Cumulative update for Windows Server, version 2025, April 2025. Hyper-V container startup failures fixed

Windows containers in Hyper-V isolation can start again when their update level differs from the host utility virtual machine. The update also improves the servicing stack.

Does it affect you? Applies to: Devices running Windows Server 2025, build 26100.3781.

Review notes Additional details from the official release notes (6) Read notes

This page The update fixes startup failures that could occur in some cases with 2025.04 B container images released April 8, when their update level did not match the hosting utility virtual machine.
In short The fix addresses cases where 2025.04 B container images released April 8 could fail to start because their update level did not match the hosting utility virtual machine.
In detail The fix addresses startup failures that could occur in some cases with 2025.04 B container images released April 8 when their update level did not match the hosting utility virtual machine.
What changes The update fixes cases where 2025.04 B container images released April 8 could fail to start when their update level did not match the hosting utility virtual machine.
What changes The fix addresses startup failures that could occur in some cases with 2025.04 B container images released April 8 when their update level did not match the hosting utility virtual machine.
Known issues The issue can occur when Exchange Server setup forestprep runs with a Windows Server 2025 schema master. Duplicate schema entries can make replication fail across the entire Active Directory enterprise; KB5068861 addresses the issue.

The official sources are linked at the end of the page.

Microsoft publishes separate notes for this KB for Windows 11.

What changes

Fix 1 change

Windows containers

Windows containers in Hyper-V isolation can start when their update level differs from the host utility virtual machine.¹
Fixes startup failures caused by mismatched update levels between Windows containers and the hosting utility virtual machine (UVM).

Improvement 1 change

Servicing stack

For: Windows Server 2025 devices

The servicing stack gets quality improvements to help devices receive and install updates.²
Includes servicing stack update KB5058538, build 26100.3764.

Known issues

Open Affects: Organizations and IT administrators

Active Directory Replication

Active Directory replication might fail with a schema mismatch when a Windows Server 2025 domain controller holds the schema master role. Microsoft says this issue existed since the initial release; KB5068861 addresses it.³

Workaround status No workaround yet

Microsoft has not published a manual workaround for this issue yet. Monitor release health until a resolving update is available.
Open Affects: Organizations and IT administrators

Citrix

Some organizations with Citrix Session Recording Agent version 2411 might fail to install the January 2025 Windows security update. Newer agent versions resolve the issue.⁴

How to apply the workaround Workaround

Use Citrix Session Recording Agent version 2503 or newer.⁴
Open Affects: Everyone

Remote desktop

Remote Desktop sessions on Windows Server 2025 might freeze shortly after connection after KB5051987 and later updates. KB5055523 resolved this issue.⁵

Workaround status No workaround yet

Microsoft has not published a manual workaround for this issue yet. Monitor release health until a resolving update is available.
Open Affects: Everyone

Windows Hello

After a reset that keeps files and uses a local install, Windows Hello face or PIN sign-in might fail on some devices. This affects devices where Secure Launch or DRTM is enabled after installing this update; KB5058411 addresses it.⁶

Workaround status No workaround yet

Microsoft has not published a manual workaround for this issue yet. Monitor release health until a resolving update is available.

Technical details

Data sheet · Security · Downloads · Components Click to collapse or expand

Data sheet

Released: 2025-04-16
Type: Cumulative update

Version	Build	Channel
2025	26100.3781	General availability

Security

No vulnerabilities are listed for this update.

Updated components

157 files changed since the previous update for the same versions.

Top changed components	Files
Kernel	3
File Explorer and shell	2
Graphics and display	2
Hyper-V and virtualization	2
Secure Boot	2
Printing	1

Sources

Microsoft Support: KB5059087

Updated Nov 7, 2026

Cited passages from Microsoft's official notes (6)

1. This update fixes an issue caused by 2025.04 B container images released on April 8, 2025 where Windows containers running in Hyper-V isolation mode could fail to start in some cases if their update level didn’t match that of the hosting utility virtual machine (UVM). support.microsoft.com
2. This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. support.microsoft.com
3. This issue appears to have existed since the initial release of Windows Server 2025, but recent Exchange Server cumulative updates (for Exchange Server SE) have exposed it. support.microsoft.com
4. The issue has been resolved in Citrix Session Recording Agent version 2503, released on April 28, 2025, and newer versions. support.microsoft.com
5. This issue was resolved by Windows update released April 8, 2025 (KB5055523). support.microsoft.com
6. This issue is addressed in KB5058411. support.microsoft.com

Checked automatically: 8 of 8 checks passed, 6 quoted passages · compared with Microsoft's page on Nov 14, 2026

Quotes found in the official pages: passed
Numbers found in the sources: passed
Vulnerabilities from the dossier only: passed
Links to allowed domains only: passed
Every official change covered: passed
Readable plain text: passed
Changes confirmed by the file list: passed
Sources agree: passed

A second AI read the text against the sources: correctness 3/5, clarity 3/5, completeness 4/5. How we work

Published by The Update Bureau. Written with AI from Microsoft's own documents, checked by rules and a second AI. How we work · Report a mistake