CodingWonders / CodingWonders/MicroWin
Bug Report: Cumulative Update / Preview Update fails with Error 0x800f0991 on Windows 11 25H2 images
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 335
- Forks
- 19
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Issue Checklist
- I checked for duplicate issues.
- I searched for existing discussions.
- I checked for an existing pull request that addresses this issue.
Provide a clear and concise description of the issue.
Description
When creating a custom Windows 11 25H2 image using microwin injected with the latest official drivers, Windows Update fails to install the May 2026 Preview Update (KB5089573) and Cumulative Update (KB5089549).
The update process hangs for a long time before eventually failing with installation error code 0x800f0991. Standard Windows Update repair techniques (like SFC and DISM) fail to resolve the issue, suggesting that a component stripped or modified by microwin during image creation is breaking the servicing stack dependencies required for this update sequence.
Steps to reproduce the issue.
Steps to Reproduce
- Generate a custom Windows 11 25H2 image using
microwin. - Integrate the latest official hardware drivers into the image during the build process.
- Install the resulting OS on a device or virtual machine.
- Check for updates via Windows Update and attempt to install KB5089573 / KB5089549.
Paste the full error output (if available).
No response
Additional context.
No response
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the Windows 11 25H2 image workflow described: build with microwin and injected official drivers, then attempt KB5089573 and KB5089549. Inspect the image-creation and driver-injection paths for servicing components that are stripped or modified, and collect the failure details. Done means identifying the incompatible change and confirming both updates install successfully on a rebuilt image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100