KB5077241 appears to damage DISM on 24H2 and 25H2

Question

I really on DISM and SFC to maintain my installations. On every single machine I've allowed this update on, DISM reports corrupt components repairable when using /scanhealth. When running with /restorehealth, it fails every time after installation throwing Error: 0x800f0915 stating "The repair content could not be found anywhere".

I have tested this by making sure all commands run properly before installing this particular update.

Again, EVERY machine I have allowed this on has become unable to /restorehealth via DISM.

Anybody have a fix for this, other than uninstalling Windows?

Answer 1

KB5077241 is an optional preview update, it is basically an early beta release of the March update released in February.

The optional preview updates can be hard to install sometimes, may contain bugs and there is no need to install the optional preview updates.

The best option is to uninstall that update, then below that update is a switch to 'Get the latest updates as soon as they are released', disable that option and restart your PC, that will stop the optional update continually trying to install and wait for the full March update update to be released next week.

Then it would be best to report this problem in that update to the Windows developers on the Feedback Hub app in Windows, so they can investigate and patch this before the March update is released.

Answer 2

KB5077241 appears to leave the component store in a state where the default DISM repair source (Windows Update/component store itself) cannot be used, which is why /ScanHealth reports “repairable” but /RestoreHealth fails with 0x800f0915 (repair content not found).

The supported way to work around this without uninstalling Windows is to supply a known‑good repair source explicitly to DISM instead of relying on Windows Update or the local store.

Use one of these approaches on each affected machine:

1. Run DISM with an alternate repair source
   1. On a healthy machine running the same Windows version/build as the affected one, or from a matching install media, expose a \Windows folder as the repair source (for example by mounting an ISO or sharing the folder).
   2. On the affected machine, open an elevated Command Prompt and run:

            DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\<servername>\c$\Windows /LimitAccess
      

      Replace <servername> with the name of the healthy machine or the path where the mounted image’s Windows directory is located.
   3. After DISM completes successfully, run:

            sfc /scannow
      

   4. Reboot and re‑run:

            DISM /Online /Cleanup-Image /ScanHealth
      

      to confirm the component store is no longer reported as repairable.
   If using offline media instead of another PC, mount the WIM/VHD and point /Source to the mounted Windows directory as documented in the image‑repair guidance.
2. If DISM still cannot repair If /RestoreHealth continues to fail even with a valid /Source, follow the advanced CBS‑corruption procedure:
   1. Analyze %windir%\Logs\CBS\CBS.log to identify specific corrupted files/packages.
   2. Use the documented PowerShell script to extract the required files from the relevant .msu/.cab packages into C:\temp\Source.
   3. Copy the correct versions of the corrupted files into C:\temp\Source.
   4. Run:

            DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\temp\Source\ /LimitAccess
      

   5. Verify with:

            DISM /Online /Cleanup-Image /ScanHealth
      

3. If the image is reported non‑repairable If DISM /Online /Cleanup-Image /CheckHealth reports the image as non‑repairable, the guidance is to discard the image and start again (in‑place repair/clean install), as the component store cannot be brought back to a supported state.

These methods avoid uninstalling Windows outright by either:

• repairing from a known‑good source, or
• performing targeted CBS repair when KB5077241 has broken the normal servicing chain.

---

References:

• Fix Windows Update corruptions and installation failures
• Repair a Windows Image