Share via

Is it a trivial uncoordination that makes Image Repair to fail and to lead to in-place reinstallation?

Claus Debanker 101 Reputation points
2025-06-01T09:07:05.68+00:00

By trying for example to add a package Rsat.WSUS.Tools~~~~0.0.1.0 from a mounted source with limited access, I find that is successful. When however there 's an issue with a specific one -Microsoft.Windows.StorageManagement&Microsoft.OneCore.StorageManagement- have I not a diagnostic track for addressing the problem with "source file not found" in analyzing component store?

Screenshot 2025-05-31 194546 The said package fails also with-no-limited-access and displays a message about the component being corrupted (or the operation to have failed); furthermore the SeaGate tools fail by a long shot to read correctly the space numbers for only one basic storage disk which disk is perfectly in line with the Check Disk utility (completes /scan in few seconds).

It seems if I could do something about the storage package, I would fix the problem with error 2 in DISM (System File Scan and Component Cleanup complete successfuly or to no integrity violations).

Windows 10 Setup
Windows 10 Setup
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
2,064 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. BblytheX 395 Reputation points Microsoft External Staff
    2025-06-03T03:44:40.4766667+00:00

    Hi Claus Debanker:

    Based on your description and DISM logs, the core issue revolves around the StorageManagement capability installation failures and potential component store corruption.

    Here's a structured diagnostic and repair approach:

    1. Verify Capability Names & Source Path
    • Correct capability names (note the syntax uses ~~~~, not ---), cmd Correct format: dism /online /add-capability /capabilityname:Microsoft.OneCore.StorageManagement~~~~0.0.1.0 dism /online /add-capability /capabilityname:Microsoft.Windows.StorageManagement~~~~0.0.1.0
    • Validate source structure: Ensure G:\ contains:
      • \sources\sxs folder (for Windows 10/11)
      • Or \x86\optionalfeatures / \amd64\optionalfeatures for legacy media.
    1. Repair Component Store Corruption

    Run these commands as Administrator, cmd to reset component store corruption:

    dism /online /cleanup-image /startcomponentcleanup

    dism /online /cleanup-image /restorehealth /source:G:\sources\install.wim:1 /limitaccess

    Follow with SFC scan:

    sfc /scannow

    Replace G:\sources\install.wim:1 with your image index (use dism /get-wiminfo /wimfile:G:\sources\install.wim to verify).

    1. Check System Volume Information (SVI)
    • Reset SVI permissions (common fix for WU/DISM issues): cmd: takeown /f "C:\System Volume Information" /r /d y icacls "C:\System Volume Information" /reset /t /c /l
    • Clear SVI restore points temporarily via: cmd: vssadmin delete shadows /all /quiet
    1. Forced Capability Installation

    If the standard install fails, force-extract the package, cmd to find the .cab file in G:\sources\sxs (e.g., Microsoft-OneCore-StorageManagement-Package~.cab):

    dism /online /add-package /packagepath:"G:\sources\sxs<cab_file>.cab"

    1. Diagnose Hardware/Driver Issues
    • Check storage drivers: cmd: pnputil /enum-drivers driverquery /v | findstr /i "stor"
    • Test disk health with manufacturer tools (SeaGate tools failing suggests driver/controller issues):
      • Use storcli64 (SeaGate CLI) or smartctl (from smartmontools).
    • Update disk controller drivers via Device Manager or OEM website.
    1. Advanced Component Store Reset

    If DISM/SFC report corruption repeatedly, cmd to backup then purge component store:

    ren C:\Windows\System32\catroot2 catroot2.bak

    ren C:\Windows\WinSxS pending.xml.bak

    Reinitialize Windows Update components:

    net stop wuauserv

    net stop cryptsvc

    net stop bits

    del /q "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader*"

    net start wuauserv

    net start cryptsvc

    net start bits

    More recommendations:

    1. Review DISM logs (C:\Windows\Logs\DISM\dism.log) for specific file errors.
    2. Test with a known-good source: Use a Windows ISO matching your OS build.
    3. Check for pending updates: Some corruptions resolve after cumulative updates.

    The SeaGate tool issue is likely separate (driver/firmware related), but fixing the StorageManagement capability may resolve underlying system-level storage reporting inconsistencies. Focus on component store repair and validating your installation source structure first.

    Please feel free to let me know if you still have any questions.

    Best regards,

    BblytheX

    0 comments

Your answer

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