Windows Component Store Size

Discussion in 'Windows 11' started by gjohnson5, Jan 6, 2023.

  1. gjohnson5

    gjohnson5 MDL Member

    Jul 25, 2013
    132
    54
    10
    #1 gjohnson5, Jan 6, 2023
    Last edited: Jan 14, 2023
    I've read that this component store size is excessive and should be fixed
    Code:
    F:\Downloads\22623.1095_amd64_en-us_professional_d817b5cd_convert>DISM.exe /online /cleanup-image /AnalyzeComponentStore
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22623.1095
    
    [===========================99.6%========================= ]
    
    Component Store (WinSxS) information:
    
    Windows Explorer Reported Size of Component Store : 15.10 GB
    
    Actual Size of Component Store : 13.86 GB
    
        Shared with Windows : 6.12 GB
        Backups and Disabled Features : 5.13 GB
        Cache and Temporary Data : 2.60 GB
    
    Date of Last Cleanup : 2022-12-29 10:09:46
    
    Number of Reclaimable Packages : 4
    Component Store Cleanup Recommended : Yes
    
    The operation completed successfully.
    F:\Downloads\22623.1095_amd64_en-us_professional_d817b5cd_convert>
    
    Any ideas on reducing the size other than reinstalling?
     
  2. My side on 11 22h2 BB OS component store minimized to 890mb ;)
     
  3. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    2,372
    1,590
    90
    use dism++ to clean check all
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,197
    84,763
    340
    Do not do it
     
  5. Mouri_Naruto

    Mouri_Naruto MDL Developer

    Jul 10, 2014
    525
    1,791
    30
    #5 Mouri_Naruto, Jan 9, 2023
    Last edited: Jan 10, 2023
    I don't think use DISM++ to cleanup SxS is safe because it have some bugs when cleaning SxS for Windows 11 images, and it's almost abandoned. (I am one of developers (not the author), but I have no interest for closed source projects at current and no chance to make it open source. I am trying to develop an open source alternative.)

    I think it's OK to use DISM.exe to cleanup SxS.

    Kenji Mouri
     
  6. gjohnson5

    gjohnson5 MDL Member

    Jul 25, 2013
    132
    54
    10
     
  7. gjohnson5

    gjohnson5 MDL Member

    Jul 25, 2013
    132
    54
    10
    Tried something that may be seen as stupid but what the heck.
    Not advocating anyone else do this. This is just for informational purposes / discussion only.

    in regedit I set

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Configuration

    Set DisableResetBase to 0
    Set SupersededActions to 1

    Built UUPdump ISO from 22621.1192_amd64_en-us_professional_6966a29a_convert
    Ran Setup from the ISO

    This must have nuked my Samsung nvme drivers because I received an Inaccessble_Boot_Device error.
    Windows reverted. I dism the cab files from the UUP's folder. Windows came back up and....

    C:\windows\System32>f:\clean_windows.bat

    C:\windows\System32>sfc/scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files and successfully repaired them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    C:\windows\System32>Dism /Online /Cleanup-Image /CheckHealth

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1

    Image Version: 10.0.22623.1192

    No component store corruption detected.
    The operation completed successfully.

    C:\windows\System32>Dism /Online /Cleanup-Image /ScanHealth

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1

    Image Version: 10.0.22623.1192

    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.

    C:\windows\System32>DISM /online /cleanup-image /restorehealth /source:WIM:G:\sources\install.wim:1 /limitaccess

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1

    Image Version: 10.0.22623.1192

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\windows\System32>DISM.exe /online /cleanup-image /AnalyzeComponentStore

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1

    Image Version: 10.0.22623.1192

    [==========================100.0%==========================]

    Component Store (WinSxS) information:

    Windows Explorer Reported Size of Component Store : 9.50 GB

    Actual Size of Component Store : 8.78 GB

    Shared with Windows : 6.07 GB
    Backups and Disabled Features : 2.32 GB
    Cache and Temporary Data : 381.75 MB

    Date of Last Cleanup : 2023-01-13 16:09:02

    Number of Reclaimable Packages : 0
    Component Store Cleanup Recommended : No

    The operation completed successfully.

    C:\windows\System32>DISM.exe /online /cleanup-image /startcomponentcleanup

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1

    Image Version: 10.0.22623.1192

    [===== 10.0% ]

    [==========================100.0%==========================]
    The operation completed successfully.

    C:\windows\System32>

     
  8. gjohnson5

    gjohnson5 MDL Member

    Jul 25, 2013
    132
    54
    10
    Definitly a failed experiment. Sometimes you just need to listen to more experienced people instead of trying things on your own. Anyway, had to restore from a 2-week-old backup because the latest beta build wouldnt install. Any the component size after restoring is worse than before.

    Code:
    C:\windows\System32>f:\clean_windows.bat
    
    C:\windows\System32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\windows\System32>Dism /Online /Cleanup-Image /CheckHealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22623.1325
    
    No component store corruption detected.
    The operation completed successfully.
    
    C:\windows\System32>Dism /Online /Cleanup-Image /ScanHealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22623.1325
    
    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.
    
    C:\windows\System32>DISM /online /cleanup-image /restorehealth /source:WIM:G:\sources\install.wim:1 /limitaccess
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22623.1325
    
    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    
    C:\windows\System32>DISM.exe /online /cleanup-image /AnalyzeComponentStore
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22623.1325
    
    [===========================99.6%========================= ]
    
    Component Store (WinSxS) information:
    
    Windows Explorer Reported Size of Component Store : 13.98 GB
    
    Actual Size of Component Store : 12.66 GB
    
        Shared with Windows : 6.16 GB
        Backups and Disabled Features : 5.60 GB
        Cache and Temporary Data : 894.61 MB
    
    Date of Last Cleanup : 2023-02-03 21:40:10
    
    Number of Reclaimable Packages : 2
    Component Store Cleanup Recommended : Yes
    
    The operation completed successfully.
    
    C:\windows\System32>DISM.exe /online /cleanup-image /startcomponentcleanup
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22623.1325
    
    [=====                      10.0%                          ]
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\windows\System32>
    
     
  9. berr1sfueller

    berr1sfueller MDL Senior Member

    Nov 17, 2022
    413
    450
    10
    Keyword is experiment. Research. Sometimes that's how to treat these things whether or not there's already a consensus that says otherwise.
    Expeditions happen in the same area twice. Prior experiments are often repeated. People cannot be expected to learn everything vicariously and you'll never break new ground without research. Also it's rewarding to be a pioneer.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    3,706
    2,662
    120
    The command to cleanup the component store is ONE, and is there since Win 8.1

    dism /online /Cleanup-Image /StartComponentCleanup /ResetBase

    You don't need anything else (assuming your component store is in sane status).

    ------------------------------------------------------------------------------------------

    On Vista/Win7/Win8 you can use the (brilliant) WinsxsLite 1.88. Which serves the same purpose in a different way.

    But keep in mind that although it can cleanup AMD64 installs it must be run from a x86 OS