Windows 11 25H2 CBS store corruption — missing superseded Hyper-V 4202 manifest

Question

Windows 11 25H2 CBS store corruption — missing superseded Hyper-V 4202 manifest

prabodh pt 0

Issue

I need assistance repairing the Windows servicing/component store without reinstalling/resetting Windows and without losing installed applications, files, or settings.

My current system is:

Windows 11 Pro 25H2 x64
OS Build: 26200.9445
Current servicing state includes KB5124008
The CBS component-store corruption detector reports one missing package manifest:

CBS reports:

The package is superseded by later Windows updates, but CBS still requires its manifest during servicing-store consistency checking.

What I have already established

The missing package corresponds to KB5058499 / OS Build 26100.4202, Windows 11 24H2 x64.

I have the official Microsoft KB5058499 MSU:

The MSU was extracted and contains the official package metadata.

The exact package MUM was recovered:

The corresponding CAT was recovered and its Microsoft signature verifies successfully.

The MUM contains:

The KB's PSF/CIX also contains genuine 4202 Hyper-V payload information, including:

with CIX-recorded SHA-256:

The associated driver payload metadata is also present in the official PSF.

Repair attempts already performed

DISM /Online /Cleanup-Image /ScanHealth
- Reports component store corruption/repairable state.
1. DISM /Online /Cleanup-Image /RestoreHealth
  - Repeatedly fails with:

Official KB5058499 MSU through WUSA:
- Does not apply because the system is now 25H2/build 26200.9445.
1. DISM /Add-Package against the KB5058499 MSU:
  - Does not repair/register the obsolete 24H2 package on the current 25H2 installation.
  1. The original 25H2 ISO is no longer available.

I do not want to perform an in-place upgrade, Reset this PC, clean installation, or other reinstall/recovery procedure.

Request to Microsoft

Please provide the authoritative servicing package/CAB or Microsoft-supported servicing procedure required to restore/register:

on my current Windows 11 25H2 build 26200.9445 system.

I specifically need the package metadata/manifest required by CBS, not merely the individual payload DLL/SYS files.

I can provide the complete relevant CBS.log, DISM logs, the recovered signed MUM/CAT, and the PSF/CIX evidence if required.

Please advise the supported method to repair this specific CBS manifest corruption while preserving the existing Windows installation, installed applications, user files, and settings.Issue

I need assistance repairing the Windows servicing/component store without reinstalling/resetting Windows and without losing installed applications, files, or settings.

My current system is:

Windows 11 Pro 25H2 x64
OS Build: 26200.9445
Current servicing state includes KB5124008
The CBS component-store corruption detector reports one missing package manifest:

CBS reports:

The package is superseded by later Windows updates, but CBS still requires its manifest during servicing-store consistency checking.

What I have already established

The missing package corresponds to KB5058499 / OS Build 26100.4202, Windows 11 24H2 x64.

I have the official Microsoft KB5058499 MSU:

The MSU was extracted and contains the official package metadata.

The exact package MUM was recovered:

The corresponding CAT was recovered and its Microsoft signature verifies successfully.

The MUM contains:

The KB's PSF/CIX also contains genuine 4202 Hyper-V payload information, including:

with CIX-recorded SHA-256:

The associated driver payload metadata is also present in the official PSF.

Repair attempts already performed

DISM /Online /Cleanup-Image /ScanHealth
- Reports component store corruption/repairable state.
1. DISM /Online /Cleanup-Image /RestoreHealth
  - Repeatedly fails with:

Official KB5058499 MSU through WUSA:

Does not apply because the system is now 25H2/build 26200.9445.

DISM /Add-Package against the KB5058499 MSU:

Does not repair/register the obsolete 24H2 package on the current 25H2 installation.

  1.  The original 25H2 ISO is no longer available.

I do not want to perform an in-place upgrade, Reset this PC, clean installation, or other reinstall/recovery procedure.

Request to Microsoft

Please provide the authoritative servicing package/CAB or Microsoft-supported servicing procedure required to restore/register:

on my current Windows 11 25H2 build 26200.9445 system.

I specifically need the package metadata/manifest required by CBS, not merely the individual payload DLL/SYS files.

I can provide the complete relevant CBS.log, DISM logs, the recovered signed MUM/CAT, and the PSF/CIX evidence if required.

Please advise the supported method to repair this specific CBS manifest corruption while preserving the existing Windows installation, installed applications, user files, and settings.

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Ramesh Srinivasan 86,840 Independent Advisor

Hi Prabodh,

A repair install via Settings will keep your apps, files, and settings intact. More info:

Fix issues by reinstalling the current version of Windows

If you don't want to perform a repair installation, please do the following:

Run:

DISM /Online /Cleanup-Image /RestoreHealth

After it completes, upload the CBS.log file (C:\Windows\Logs\CBS\CBS.log) in your next reply.

If the file is too large, you may share it on OneDrive and post the link here.

Ramesh Srinivasan 86,840 Reputation points Independent Advisor

2026-09-09T09:51:33.19+00:00

Request to Microsoft

Please note that this is a peer-to-peer support forum, and there is no guarantee that the Microsoft support team will see your thread.

I'd be glad to help if you run the above-mentioned command and upload the CBS.log file.
prabodh pt 0 Reputation points

2026-09-09T10:12:39.23+00:00
Hi Ramesh,

Thank you for your response and for pointing me to the repair-install option.

I have already run DISM /Online /Cleanup-Image /RestoreHealth. It completes with 0x800f0915, stating that the required repair source could not be found.

I have also checked the resulting CBS.log. CBS identifies a specific missing servicing manifest:

CBS reports:

I have located the corresponding official Microsoft KB5058499 package material, including the signed .mum and .cat, and the PSF/CIX also contains the associated 4202 Hyper-V payload information.

My preference is not to perform a repair installation unless there is no other supported solution, because I would first like to repair this specific CBS manifest corruption while keeping the existing installation intact.

Could you please advise whether Microsoft has a supported way to restore/register this specific missing 4202 servicing manifest, or provide the appropriate servicing package/source required by CBS?
Ramesh Srinivasan 86,840 Reputation points Independent Advisor

2026-09-09T10:14:37.3566667+00:00

Could you please advise whether Microsoft has a supported way to restore/register this specific missing 4202 servicing manifest, or provide the appropriate servicing package/source required by CBS?

I can try to source the missing manifests. But the CBS.log file is needed. Please upload it.
prabodh pt 0 Reputation points

2026-09-09T10:22:14.14+00:00

Hi Ramesh,

Thank you for offering to help source the missing manifests.

I have uploaded a focused excerpt from my CBS log containing the relevant entries around the servicing corruption and the missing manifest. The full CBS log is larger than the Microsoft Q&A attachment limit, so I extracted the relevant section for easier review.

The system is currently running Windows 11 25H2, build 26200.9445. DISM RestoreHealth has already been attempted and cannot locate the required repair source.

I would greatly appreciate it if you could review the attached CBS evidence and, if possible, help identify or source the missing manifests needed to repair the component store without performing a repair installation.

Thank you again for taking the time to look into this.CBS_relevant.txt
Ramesh Srinivasan 86,840 Reputation points Independent Advisor

2026-09-09T10:24:00.9+00:00

Hi Prabodh,

Unfortunately, the excerpt posted is insufficient.

Please upload the entire CBS.log file on OneDrive or GoFile.io and post the link here.
prabodh pt 0 Reputation points

2026-09-09T11:48:00.6566667+00:00

Hi Ramesh,

Thank you. I have now uploaded the complete CBS.log to GoFile as requested.

Please find it here: https://gofile.io/d/u9i9IOG1

I hope the complete log provides the information needed to identify and source the missing servicing manifests. Thank you again for your help.
Ramesh Srinivasan 86,840 Reputation points Independent Advisor

2026-09-09T11:50:42.2766667+00:00

Hi Prabodh,

The link throws the following error.

Can you try uploading it again?
prabodh pt 0 Reputation points

2026-09-09T12:09:44.9266667+00:00

https://gofile.io/d/xag9K0In
Ramesh Srinivasan 86,840 Reputation points Independent Advisor

2026-09-09T12:14:43.3533333+00:00
Thanks for the log file. I've sourced the manifest.

Download SFCFix.exe by niemiro of Sysnative forums, and save this to your Desktop.

Download the file, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.

On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip. Drag the file SFCFix.zip onto the file SFCFix.exe and release it. See illustration image

When you see the prompt "Will you allow SFCFix to communicate with Sysnative servers?", type "n" for no. Press Enter to continue.

SFCFix will now process the script. It will take some time to complete. Upload the output file SFCFix.txt.

Run the following command:

DISM.exe /Online /Cleanup-image /Restorehealth

Let me know if that fixes the issue.

Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to provide accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as PUPs (Potentially Unwanted Products).
prabodh pt 0 Reputation points

2026-09-09T12:43:14.19+00:00

Hi Ramesh,

Thank you very much for taking the time to review the complete CBS.log and for sourcing the missing manifest and providing the SFCFix package.

I’ll follow your instructions and run the repair tomorrow. I’ll then upload the SFCFix.txt output and run the DISM RestoreHealth command as requested.

I’ll revert with the results tomorrow.

Thank you again for your help and for taking the time to work through this issue.
Ramesh Srinivasan 86,840 Reputation points Independent Advisor

2026-09-09T12:44:19.6533333+00:00

Hi Prabodh,

Ok. Good luck and keep me posted.

Regards,
prabodh pt 0 Reputation points

2026-09-10T08:38:02.2766667+00:00

Hi Ramesh,

Thank you again for sourcing the missing manifest.

I wanted to give you an update before proceeding further.

SFCFix successfully restored both the CAT and MUM for the missing 4202 Hyper-V package into the Windows servicing packages directory.

I then ran DISM RestoreHealth. The process ran for several hours and eventually stalled at 67.5%, so I stopped it.

The interesting part is that the CBS log from this run shows that corruption detection completed with zero detected corruptions. It subsequently reported that a metadata/file-flag repair operation was required.

There are also some later errors concerning an old KB3025096 package, but those entries were generated by the Windows Update Agent / Appraiser Driver Scan, rather than the DISM repair session, so I don't believe they are related to the RestoreHealth stall.

Could you please advise whether, now that the 4202 manifest has been successfully restored and CBS reports zero detected corruptions, I should run DISM RestoreHealth again?

I don't want to make any further changes until I have your recommendation.

Thank you again for your help.
Ramesh Srinivasan 86,840 Reputation points Independent Advisor

2026-09-10T08:53:50.2666667+00:00
Hi Prabodh,

Could you please advise whether, now that the 4202 manifest has been successfully restored and CBS reports zero detected corruptions, I should run DISM RestoreHealth again?

Please run the following command instead:

DISM /Online /Cleanup-Image /ScanHealth

If it reports any corruption, please upload the latest CBS.log file.
prabodh pt 0 Reputation points

2026-09-10T09:23:46.26+00:00
Hi Ramesh,

I ran the ScanHealth command as requested.

It completed successfully and reported “No component store corruption detected.”

Therefore, I have not run RestoreHealth again and have not made any further changes.

Thank you very much for helping identify and restore the missing manifest. This appears to have resolved the component-store corruption.

Please let me know if you recommend any further verification.

Running log

Missing 4202 manifest → restored by SFCFix

RestoreHealth → stalled at 67.5%

ScanHealth → 100%, no component store corruption

Current component store status → Healthy
Ramesh Srinivasan 86,840 Reputation points Independent Advisor

2026-09-10T09:25:26.1+00:00

I'm glad to hear that @prabodh pt

Thank you for the feedback!

If all is resolved, feel free to mark the answer for this thread. Otherwise, please let me know if there's anything else I can help you with.