builtbybel / builtbybel/FlyOOBE
DISM and Windows Update issues after upgrading to Windows 11 25H2 via Flyoobe
- Dominant language
- C#
- Stars
- 7.3k
- Forks
- 379
- PR merge metrics
- No merged PRs in 30d
Description
I upgraded my system to Windows 11 25H2 (build 26200.6584) using the Flyoobe tool.
Since the upgrade, all DISM commands fail with error `0x80070057` (“The repair content could not be found”).
The log shows DISM version 10.0.26100.5074, while my system build is 10.0.26200.6584, it seems the Servicing Stack wasn’t fully updated.
Also, the cumulative update KB5065789 fails to install with error `0x80070306`.
Questions:
1. Is this partial Servicing Stack version intentional in Flyoobe (for compatibility reasons)?
2. Is there a supported way to sync or update the Servicing Stack / DISM to match build 26200?
Thanks in advance for clarifying and helping investigate this. 🙏
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the reported Flyoobe upgrade path and the DISM log showing version 10.0.26100.5074 on build 10.0.26200.6584. Check whether the partial Servicing Stack version is intentional and investigate the KB5065789 failure with errors 0x80070057 and 0x80070306; done means documenting the supported sync or recovery path.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100