Start Component Cleanup - Access Denied - Error Code 5

Running Windows 10 Pro. V21H1 Build 19043.1110

When I run

dism /online /cleanup-Image /StartComponentCleanup

it ends at 23% Access denied - Error Code 5

I ran an Inplace Repair which processed successfully.
I quit MalwareBytes (just in case it was protecting something)

Ran chkdsk /scan - Windows has scanned file system and found no errors

Ran sfc /scannow - found corruption and repaired (this was almost directly after inplace)

Reran sfc /scanow - no integrity erros found

Ran dism /online /cleanup-Image /checkhealth - No component store corruption detected

Ran dism /online /cleanup-image /scanhealth - No component store corruption detected

Ran dism /online /restorehealth - the restore operation completed successfully

Ran dism /online / cleanup-image /analzecomponentstore

Reported size 7.61 GB
Actual size 7.54GB
Date of last cleanup 2021-04-09
Component Store Cleanup Recommended: Yes

Ran dism /online /cleanup-image /startcomponentcleanup

Fails at 23.7%

Error code 5

Access denied.




I should mention I've run this several times and the component store has come down in size from 9.24 GB. (Actual size 8.88). These numbers were from right after the inplace. Then I executed all the commands above.


The error in the CBS log that kicks the issues off is

CSI 00000038@2021/7/14:13:40:36.746 (F) onecore\base\wcp\sil\systemisolationlayer.cpp(351): Error STATUS_CANNOT_DELETE originated in function Windows::Rtl::SystemImplementation::MarkFileDeletePending expression: (null)
[gle=0x80004005]

then

2021-07-14 09:40:39, Error CSI 00000039 (F) STATUS_CANNOT_DELETE #6586874# from Windows::Rtl::SystemImplementation::MarkFileDeletePending(...)[gle=0xd0000121]

2021-07-14 09:40:39, Error CSI 0000003a (F) STATUS_CANNOT_DELETE #6586873# from Windows::Rtl::SystemImplementation::CDirectory:eleteExistingFile(...)[gle=0xd0000121]

2021-07-14 09:40:39, Error CSI 0000003b (F) STATUS_CANNOT_DELETE #6586872# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff:eleteExistingFile(flags = (MissingFileIsOk|MarkDeletePending|OpenForBackup|DeleteIfReadOnly|SharingViolationIsOk|Transactional ConflictIsOk), oa = @0x84c5dac370->SIL_OBJECT_ATTRIBUTES {s:40; on:"03d9a1a4bd0c6336069f06358119566d6cfd783c06fb8ac1f7c2f77c7f246d14.cat"; aOBJ_CASE_INSENSITIVE)}, disp = Invalid)
[gle=0xd0000121]

2021-07-14 09:40:43, Error CSI 0000003c (F) STATUS_CANNOT_DELETE #4076988# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 0[gle=0xd0000121]

2021-07-14 09:40:43, Error CSI 0000003d (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #4076900# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x80070005]

2021-07-14 09:40:43, Error CSI 0000003e (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #4076898# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 22, pSink = NULL, disp = 0)[gle=0x80070005]

2021-07-14 09:40:43, Error CSI 0000003f (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #4076897# 22220901 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000016, pSink = NULL, disp = 0)
[gle=0x80070005]

After a restart the /StartComponentCleanup was the first DISM command run. Processed successfully.

x 2

Caledon Ken said:

After a restart the /StartComponentCleanup was the first DISM command run. Processed successfully.

Glad you've solved this.

Bet it was that zero bytes temp file.

Could be but I didn't delete it. Wanted to see what processes were creating what files. Your excellent idea of sorting using TreeSize to see owners and permission was very helpful.