Windows Server 2025 LTSC container images incompatible with Windows 11 25H2
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, go
- Domain
- infrastructure, operating-systems
Research direction
No source files, tests, or entry points are named. Start by reproducing the failure with Windows 11 25H2, the Windows Server 2025 LTSC image, Docker 29.0.1, and both isolation modes, then compare against the working LTSC 2022 image. Done means the incompatibility is explained and a verified fix or supported workaround is identified.
Written by the indexing model from the issue text.
Description
- Host OS: Windows 11 25H2 (Build 26200.7171)
- Container Image: mcr.microsoft.com/windows/servercore:ltsc2025 (Build 26100.7171)
- Error: hcsshim::PrepareLayer failed in Win32: The container image contains a layer with an unrecognized format. (0xc0370112)
- Docker Version: 29.0.1
- Isolation Mode: Both process and hyperv fail
- Workaround: LTSC 2022 works fine
- Impact: Cannot develop/test applications targeting Windows Server 2025
- Dominant language
- Go
- Stars
- 694
- Forks
- 304
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 28
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/hcsshim
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/hcsshim#2831 · 3 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/hcsshim#2823 · 8 comments ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Maintainers usually reply within 2 days
All issues in microsoft/hcsshim
Similar issues
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netdata/netdata#24062 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
meshery/meshery#22119 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
automation documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day