Windows 11 Update Error 0x800f081f Component Store Corruption

Manon David 60 Reputation points
2026-09-28T10:25:44.6966667+00:00

Automated patch deployment fails on remote laptops with missing source files error. How do we run DISM /Online /Cleanup-Image /RestoreHealth via management agents?

Windows for business | Windows 365 Enterprise
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Hoang Le 6,275 Reputation points Independent Advisor
    2026-09-28T11:00:45.8266667+00:00

    Hello Manon David,

    If automated patch deployment is failing with DISM error 0x800F081F (CBS_E_SOURCE_MISSING) or "The source files could not be found", the recommended approach is to execute DISM /Online /Cleanup-Image /RestoreHealth through your management agent under the Local System context and allow access to Windows Update as the repair source whenever internet connectivity is available. Microsoft identifies 0x800F081F as a missing repair source condition and recommends using DISM to repair the component store before retrying patch installation.

    For managed devices that cannot reach Windows Update, deploy a command such as DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:\\server\share\install.wim:<index> /LimitAccess, ensuring the WIM source matches the exact Windows edition and build installed on the endpoint. The management platform (Intune, MECM/SCCM, Ivanti, PDQ, etc.) should run the command with administrative privileges and capture logs from C:\Windows\Logs\DISM\dism.log and C:\Windows\Logs\CBS\CBS.log for validation. After DISM completes successfully, trigger sfc /scannow and rerun the failed update deployment to confirm the component store corruption has been remediated. This is the Microsoft-supported method for repairing Windows Update corruption and resolving missing source file failures.

    If my answer is useful for you, please hit Accept the answer to support me.

    Thank you.

    HL.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-09-28T10:26:05.6266667+00:00

    Run the command in an elevated context on each device:

    DISM.exe /Online /Cleanup-Image /RestoreHealth

    Then run:

    sfc /scannow

    After that, retry Windows Update.

    Key points for managed remote laptops:

    1. The command must run with administrator privileges.
    2. For online image repair, DISM works best when the device can reach Microsoft Update to download missing or corrupted files.
    3. If the laptop cannot use Windows Update as the repair source, specify a repair source with /Source and block Windows Update lookup with /LimitAccess, for example:
    DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\<servername>\c$\windows /LimitAccess
    1. The repair source computer or source files must match the same operating system version, and the repair source should be patched to the latest cumulative update. If the target OS is patched higher than the source, repair can fail because the required updated files are not present in the source.
    2. DISM supports /CheckHealth, /ScanHealth, and /RestoreHealth under /Cleanup-Image:
      • /CheckHealth checks whether the image is flagged as corrupted and whether it is repairable.
      • /ScanHealth scans for component store corruption.
      • /RestoreHealth scans and performs repair automatically.
    3. For repeated 0x800f081f cases, that error maps to CBS_E_SOURCE_MISSING, which indicates component store corruption or missing repair source files.
    4. DISM writes details to %windir%\Logs\CBS\CBS.log.

    A practical sequence for deployment through a management agent is:

    1. Run an elevated command prompt or elevated script step.
    2. Execute:
    DISM.exe /Online /Cleanup-Image /ScanHealth
DISM.exe /Online /Cleanup-Image /CheckHealth
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
    1. If /RestoreHealth returns source file errors, rerun it with a valid /Source path and /LimitAccess.
    2. Retry the update installation.

    If a local source is used instead of Windows Update, Group Policy can be used to configure the preferred repair source under:

    Computer Configuration > Administrative Templates > System > Specify settings for optional component installation and component repair

    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.