WinSxs corrupt

Al T 0 Reputation points
2026-09-07T04:05:14.8566667+00:00
  • The WinSxS component store has deeper corruption
  • The servicing stack is damaged
  • DISM can’t access the repair source it needs
  • A pending update is blocking repairs

what is the step by step fix plz

Microsoft Security | Microsoft Authenticator
0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-09-07T04:05:42.3966667+00:00
    1. Back up the OS disk first. Some repair steps change servicing state and package data.
    2. Reset the Windows Update servicing stack.
      • On an Azure VM, run the Azure VM Windows Update Reset Tool first.
      • If running locally, reset Windows Update components:
    net stop wuauserv
net stop bits
net stop cryptSvc

ren %windir%\SoftwareDistribution SoftwareDistribution.old
ren %windir%\System32\catroot2 catroot2.old

net start cryptSvc
net start bits
net start wuauserv
    • Restart Windows, then try the repair again.
    1. Run DISM to scan and repair the component store.
      • Open an elevated Command Prompt and run:
    DISM.exe /Online /Cleanup-Image /ScanHealth
DISM.exe /Online /Cleanup-Image /RestoreHealth
    • If corruption is found and repaired, continue with SFC.
    1. Run System File Checker.
    sfc /scannow
    • Wait until verification reaches 100%.
    • If SFC reports it repaired files, restart and test Windows Update again.
    1. If DISM cannot access the repair source, use a known-good Windows installation source.
      • Mount or attach Windows media that matches the same OS version and build.
      • Find the drive letter, for example E:.
      • Run:
    DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess
    • Then run:
    sfc /scannow
    1. Check CBS.log to identify the exact corruption.
      • Review:
        • C:\Windows\Logs\CBS\CBS.log
        • C:\Windows\Logs\DISM\dism.log
      • Search CBS.log for Error, CORRUPT, MISSING, or HRESULT.
      • Important patterns:
        • STATUS_SXS_COMPONENT_STORE_CORRUPT or HRESULT_FROM_WIN32(14098): usually repairable with /RestoreHealth
        • CBS_E_SOURCE_MISSING (0x800F081F): repair source is missing, use /Source
        • CBS_E_IMAGE_UNSERVICEABLE (0x800F0830): servicing stack is too damaged for normal repair
        • PSFX_E_MATCHING_BINARY_MISSING: in-place upgrade is typically required
    2. If CBS.log identifies a specific corrupted package, remove and repair it.
      • Warning: package removal changes installed update state.
    DISM.exe /Online /Remove-Package /PackageName:<package-name-from-log>
DISM.exe /Online /Cleanup-Image /RestoreHealth
    1. If the issue is still not fixed, perform an in-place upgrade.
      • This is the documented next step when the servicing stack is too damaged or the image is unserviceable.
    2. If more investigation is needed, collect these logs before escalation:
      • C:\Windows\Logs\CBS\CBS.log
      • C:\Windows\Logs\CBS\CbsPersist_*.cab
      • C:\Windows\Logs\DISM\dism.log
      • SFC details:
    findstr /c:"[SR]" C:\Windows\Logs\CBS\CBS.log > C:\sfcdetails.txt

    Do not delete files directly from C:\Windows\WinSxS. That can severely damage Windows and prevent boot or future updates.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.