Note
- Original publish date: April 16, 2025
- KB ID: 5059118
Windows Server containers
This out-of-band (OOB) update addresses a known issue where Hyper-V isolated containers may fail to start in certain scenarios. For more details on how this issue affects each Windows Server product, please refer to the section below titled Available Windows Server container images.
As part of this OOB release, we have updated the Windows Server Base OS container images. With these updates, you can either automate the build process for updated container images or manually pull the latest versions. Unlike Windows Server or Windows client, Windows Server containers do not include a servicing stack and do not support in-place updates. Instead, we rebuild and publish updated Windows Server Base OS container images each month to incorporate the latest fixes.
For more information on update best practices, see Update Windows Server containers.
Available Windows Server container images
Note
Note 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). The mismatch caused compatibility problems between system files, leading to startup failures. With this update, containers now correctly access the necessary system files from the host, improving reliability and compatibility across different Windows versions.
| Container |
Version |
KB |
Architecture |
Languages |
Windows Server 2025 Server Core Container
Windows Server Core |
10.0.26100.3781 |
Cumulative LCU: KB5059087
SSU version 10.0.26100.3764
(included in LCU) |
x64 |
en-us |
Windows Server 2025 Nano Server Container
Nano Server |
10.0.26100.3781 |
Cumulative LCU: KB5059087
SSU version 10.0.26100.3764
(included in LCU) |
x64 |
en-us |
Windows Server 2025 Container
Windows Server |
10.0.26100.3781 |
Cumulative LCU: KB5059087
SSU version 10.0.26100.3764
(included in LCU) |
x64 |
en-us |
End of support for Windows Server 2025
Support for Windows Server 2025 will end in October 2034
After October 10, 2034, Microsoft will no longer provide free software updates from Windows Update, technical assistance, or security fixes for Windows Server 2025. We recommend that you upgrade to a later version of Windows Server.
Note
Note 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). The mismatch caused compatibility problems between system files, leading to startup failures. With this update, containers now correctly access the necessary system files from the host, improving reliability and compatibility across different Windows versions.
| Container |
Version |
KB |
Architecture |
Languages |
Windows Server 2022 Server Core Container
Windows Server Core |
10.0.20348.3566 |
Cumulative LCU: KB5059092
SSU version 10.0.20348.3440
(included in LCU) |
x64 |
en-us |
Windows Server 2022 Nano Server Container
Nano Server |
10.0.20348.3566 |
Cumulative LCU: KB5059092
SSU version 10.0.20348.3440
(included in LCU) |
x64 |
en-us |
Windows Server 2022 Container
Windows Server |
10.0.20348.3566 |
Cumulative LCU: KB5059092
SSU version 10.0.20348.3440
(included in LCU) |
x64 |
en-us |
End of support for Windows Server 2022
Note
- Support for Windows Server 2022 will end in October 2031
- After October 14, 2031, Microsoft will no longer provide free software updates from Windows Update, technical assistance, or security fixes for Windows Server 2022. We recommend that you upgrade to a later version of Windows Server.
Note
Note 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). The mismatch caused compatibility problems between system files, leading to startup failures. With this update, containers now correctly access the necessary system files from the host, improving reliability and compatibility across different Windows versions.
| Note For all Windows Server 2019 images (Windows Server, Nano Server, and Windows Server Core), we now default to tag LTSC2019. However, you can continue to use the 1809 tag (as before) to pull the latest Nano Server and Windows image. |
| Container |
Version |
KB |
Architecture |
Languages |
Windows Server 2019 Server Core Container
Windows Server Core |
10.0.17763.7249 |
Cumulative LCU: KB5059091
SSU version 10.0.17763.7125
(included in LCU) |
x64 |
en-us |
Windows Server 2019 Nano Server Container
Nano Server |
10.0.17763.7249 |
Cumulative LCU: KB5059091
SSU version 10.0.17763.7125
(included in LCU) |
x64 |
en-us |
Windows Server 2019 Windows Container
Windows |
10.0.17763.7249 |
Cumulative LCU: KB5059091
SSU version 10.0.17763.7125
(included in LCU) |
x64 |
en-us |
End of support for Windows Server 2019
Note
Note There is not an out-of-band container image for Windows Server 2016. Please use the container image from the April 8, 2025 release (listed below).
| Container |
Version |
KB |
Architecture |
Languages |
Windows Server 2016 Server Core Container
Windows Server Core |
10.0.14393.7969 |
Cumulative LCU: KB5055521
SSU: KB5055661 |
x64 |
cs-cz, de-de, en-us, es-es, fr-fr, hu-hu, it-it, ja-jp, ko-kr, nl-nl, pl-pl, pt-br, pt-pt, ru-ru, sv-se, tr-tr, zh-cn, zh-tw |
End of support for Windows Server 2016
References
Windows and containers
Update Windows Server containers
For information on .NET Framework support, see dotnet/framework.
