Windows Update continuously fails and DISM reports component store corruption.

Tommy Freddle 0 Reputation points
2026-10-22T08:58:08.66+00:00

I have a new company workstation but the same thing happened with the old ones on our domain. Windows Update does not properly install patches. Most of the time it simply fails immediately, then when I try to run a scan, DISM reports that the component store is corrupted. It marks it as having a problem, like I need to restore from a clean source image, but I don't know how to identify the affected components or how to use a repair source that matches our installed OS version. I have Windows 11 Enterprise.

Windows for business | Windows 365 Enterprise
0 comments No comments

1 answer

Sort by: Newest
  1. Domic Vo 35,620 Reputation points Independent Advisor
    2026-10-22T09:43:23.1833333+00:00

    Hello,

    Since this affects both new and existing domain-joined workstations, check whether domain policies or WSUS configuration are preventing Windows from accessing the repair files. DISM reporting component store corruption does not necessarily mean Windows must be reinstalled.

    Run the following commands in an elevated Command Prompt:

    DISM /Online /Cleanup-Image /ScanHealth
    DISM /Online /Cleanup-Image /RestoreHealth
    

    If repair fails, run winver to identify your Windows 11 build and use matching installation media for the same release, architecture, and language. Check the available image indexes with DISM /Get-WimInfo /WimFile:D:\sources\install.wim, then repair using the correct Enterprise index:

    DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:<index> /LimitAccess
    

    Replace <index> with the correct index. If the media contains install.esd, use Source:esd: instead. The repair source must contain the components required by your installed OS.

    After DISM succeeds, run sfc /scannow and retry Windows Update. Since multiple computers are affected, also review domain policies controlling component repair and Windows Update sources.

    Please share the exact DISM error code and relevant entries from C:\Windows\Logs\DISM\dism.log so we can identify the root cause.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

    Domic Vo.

    Was this answer helpful?

    0 comments No comments

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.