Solved Dism /online /Cleanup-Image /StartComponentCleanup /ResetBase not working

Scott · Jul 16, 2022

Tried to cleanup my component store but the command isn't working. Any suggestions?

Analyze and Clean Up Component Store (WinSxS folder) in Windows 11

This tutorial will show you how to analyze and clean up the component store (WinSxS folder) to reduce its size in Windows 10 and Windows 11. The WinSxS folder is located in the Windows folder, for example C:\Windows\WinSxS. It’s the location for Windows Component Store files. The Windows...

www.elevenforum.com

Tekkie Boy · Jul 16, 2022

The Resetbase option has been disabled in Windows for a long time.

Resetbase has often done more harm than good in the past.

In the worst case, a system was no longer bootable.

cereberus · Jul 16, 2022

Tekkie Boy said:
The Resetbase option has been disabled in Windows for a long time.

View attachment 34137

Resetbase has often done more harm than good in the past.

In the worst case, a system was no longer bootable.

It is the SPSuperseded option that is no longer working.

I run mine regularly and the component store is kept around 6.6 GB. OP's is around 12 GB which is very large.

Something is not correct.

Tekkie Boy · Jul 16, 2022

@Scott

I tested it in a VM, the cleanup itself works, but as already written, Resetbase is ignored because it is disabled.

What do you get after the following commands?

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /CheckHealth

x BlueRobot · Jul 16, 2022

@Scott

Your best option at the moment is to take a look at the DISM log which should be available here:

Rich (BB code):

%systemroot%\Logs\DISM

However, I would not personally recommend using the /ResetBase switch unless you understand what it actually does.

x BlueRobot · Jul 16, 2022

Tekkie Boy said:
What do you get after the following commands?

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /CheckHealth

Why are you recommending both? The /CheckHealth switch does the same /ScanHealth but will actually check the integrity of the Component Store.

Josey Wales · Jul 16, 2022

I run this command

Code:

Dism.exe /online /Cleanup-Image /StartComponentCleanup

Scott · Jul 16, 2022

Josey Wales said:
I run this command

Code:

Dism.exe /online /Cleanup-Image /StartComponentCleanup

Same result. /CheckHealth and /ScanHealth both came back good.

Scott · Jul 16, 2022

Scott · Jul 16, 2022

Here's my dism log

Scott · Jul 16, 2022

From the log:

x BlueRobot · Jul 16, 2022

Scott said:
From the log:

View attachment 34187

That's fine and will not be the issue.

x BlueRobot · Jul 16, 2022

Rich (BB code):

2022-07-12 14:42:41, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2022-07-12 14:42:41, Info                  DISM   DISM.EXE: 
2022-07-12 14:42:41, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.22000, Running architecture=amd64, Number of processors=12
2022-07-12 14:42:41, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.22000.653
2022-07-12 14:42:41, Info                  DISM   DISM.EXE: Executing command line: dism.exe  /online /Cleanup-Image /StartComponentCleanup
2022-07-12 14:42:41, Info                  DISM   DISM Manager: PID=4352 TID=7388 physical location path: C:\ - CDISMManager::CreateImageSession
2022-07-12 14:42:41, Info                  DISM   DISM Manager: PID=4352 TID=7388 Event name for current DISM session is Global\{594F4FF0-9F9B-4621-9B51-A5C5FBE053F9} - CDISMManager::CheckSessionAndLock
2022-07-12 14:42:41, Info                  DISM   DISM Manager: PID=4352 TID=7388 Create session event 0x20c for current DISM session and event name is Global\{594F4FF0-9F9B-4621-9B51-A5C5FBE053F9}  - CDISMManager::CheckSessionAndLock
2022-07-12 14:42:41, Info                  DISM   DISM Manager: PID=4352 TID=7388 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2022-07-12 14:42:41, Info                  DISM   DISM Manager: PID=4352 TID=7388 Successfully loaded the ImageSession at "C:\Users\scott\AppData\Local\Temp\4651765B-BBCC-41D1-B6D3-F11AF71ED843" - CDISMManager::LoadRemoteImageSession
2022-07-12 14:42:41, Info                  DISM   DISM Image Session: PID=13136 TID=2364 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2022-07-12 14:42:41, Info                  DISM   DISM OS Provider: PID=13136 TID=2364 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2022-07-12 14:42:41, Info                  DISM   DISM OS Provider: PID=13136 TID=2364 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2022-07-12 14:42:41, Info                  DISM   DISM Provider Store: PID=13136 TID=2364 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2022-07-12 14:42:41, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2022-07-12 14:42:41, Info                  DISM   DISM Provider Store: PID=13136 TID=2364 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2022-07-12 14:42:41, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2022-07-12 14:42:41, Info                  DISM   Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2022-07-12 14:42:41, Info                  DISM   DISM Manager: PID=4352 TID=7388 Image session successfully loaded from the temporary location: C:\Users\scott\AppData\Local\Temp\4651765B-BBCC-41D1-B6D3-F11AF71ED843 - CDISMManager::CreateImageSession
2022-07-12 14:42:41, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.22000.795, Image architecture=amd64
2022-07-12 14:42:41, Info                  DISM   DISM.EXE: Image session version: 10.0.22000.1
2022-07-12 14:42:41, Info                  DISM   DISM Transmog Provider: PID=13136 TID=2364 Current image session is [ONLINE] - CTransmogManager::GetMode
2022-07-12 14:42:41, Info                  DISM   DISM Transmog Provider: PID=13136 TID=2364 Audit Mode: [No] - CTransmogManager::Initialize
2022-07-12 14:42:41, Info                  DISM   DISM Transmog Provider: PID=13136 TID=2364 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
2022-07-12 14:42:41, Info                  DISM   DISM Transmog Provider: PID=13136 TID=2364 Product Type: [WinNT] - CTransmogManager::Initialize
2022-07-12 14:42:41, Info                  DISM   DISM Transmog Provider: PID=13136 TID=2364 Product Type ServerNT : [No] - CTransmogManager::Initialize
2022-07-12 14:42:41, Info                  CSI    00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.795_none_047def894cac2b60\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2022-07-12 14:42:41, Info                  CSI    00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.795_none_047def894cac2b60\wcp.dll' : got STATUS_SUCCESS
2022-07-12 14:42:41, Info                  DISM   DISM Driver Manager: PID=13136 TID=2364 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2022-07-12 14:42:41, Info                  CSI    00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.795_none_047def894cac2b60\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2022-07-12 14:42:41, Info                  CSI    00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.795_none_047def894cac2b60\wcp.dll' : got STATUS_SUCCESS
2022-07-12 14:42:41, Info                  DISM   DISM OS Provider: PID=13136 TID=2364 Determined System directory to be C:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory
2022-07-12 14:42:41, Info                  DISM   DISM Package Manager: PID=13136 TID=2364 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2022-07-12 14:42:41, Info                  CSI    00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.795_none_047def894cac2b60\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2022-07-12 14:42:41, Info                  CSI    00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.795_none_047def894cac2b60\wcp.dll' : got STATUS_SUCCESS
2022-07-12 14:42:41, Info                  DISM   DISM Package Manager: PID=13136 TID=2364 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2022-07-12 14:42:41, Info                  DISM   DISM Package Manager: PID=13136 TID=2364 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
2022-07-12 14:42:41, Info                  DISM   DISM Package Manager: PID=13136 TID=2364 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2022-07-12 14:42:41, Info                  DISM   DISM Package Manager: PID=13136 TID=2364 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2022-07-12 14:42:41, Info                  DISM   DISM Package Manager: PID=13136 TID=2364 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2022-07-12 14:42:41, Info                  DISM   DISM Package Manager: PID=13136 TID=2364 CBS session options=0x400100! - CDISMPackageManager::Internal_Finalize
2022-07-12 14:44:23, Info                  DISM   DISM Package Manager: PID=13136 TID=6264  Error in operation: the operation could not be complete due to locked resources. (CBS HRESULT=0x800f0806) - CCbsConUIHandler::Error
2022-07-12 14:45:29, Info                  CSI    00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.795_none_047def894cac2b60\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2022-07-12 14:45:29, Info                  CSI    00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22000.795_none_047def894cac2b60\wcp.dll' : got STATUS_SUCCESS
2022-07-12 14:45:29, Info                  DISM   DISM Package Manager: PID=13136 TID=2364 Finalizing CBS core. - CDISMPackageManager::Finalize
2022-07-12 14:45:29, Info                  DISM   DISM Manager: PID=4352 TID=7388 Closing session event handle 0x20c - CDISMManager::CleanupImageSessionEntry
2022-07-12 14:45:29, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.

Are you running any third-party software and have you rebooted your computer since this error has begun occurring?

Scott · Jul 16, 2022

x BlueRobot said:
Are you running any third-party software and have you rebooted your computer since this error has begun occurring?

Rebooted multiple times, and yes 3rd party software (but not antivirus).

Scott · Jul 17, 2022

Just did a in-place upgrade install/repair. Good-to-go now. Thanks @Brink for the tutorial.

x BlueRobot · Jul 17, 2022

I'm glad you managed to get the issue resolved!

Solved Dism /online /Cleanup-Image /StartComponentCleanup /ResetBase not working

Well-known member

My Computers

A member

My Computer

Well-known member

My Computer

A member

My Computer

Account Closed

My Computer

Account Closed

My Computer

Endeavor to Persevere

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

Attachments

My Computers

Well-known member

My Computers

Account Closed

My Computer

Account Closed

My Computer

Well-known member

My Computers

Well-known member

My Computers

Account Closed

My Computer

Similar threads