Corruption that DISM is having trouble fixing

Rocky714 0 Reputation points
2024-03-17T18:56:15.95+00:00

Hello,

I can't solve a corruption problem on my Win10 (22H2-19045.3930) Home machine I have that I think DISM should be able to fix. I know that my index is "1" since I didn

Dism /get-wiminfo /wimfile:g:\sources\install.wim

and received, in part

Deployment Image Servicing and Management tool

Version: 10.0.19041.3636

Details for image : g:\sources\install.wim

Index : 1

Name : Windows 10 Home

Description : Windows 10 Home

Size : 15,098,360,792 bytes

I've done the "sfc /scannow" command (no errors) and issued the command

Dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:g:\sources\install.wim:1 /LimitAccess

which returns

[begin screen capture]

[===========================84.9%================= ]

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

Error: 0x800f081f

The source files could not be found.

Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

[end screen capture]

The dism.log and cbs.log files are edited for brevity (and to allow posting) to just before the first "warning" in dism.log and "error" in cbs.log and then pasted in below. I'm pretty sure it does actually find the source files (g:=a mounted ISO for 22H2 and it finds the index number from above). However, the dism.log and cbs.log suggest a file corruption. I can't tell where it's stumbling or how to fix it. I've tried resetting the update catalog but that didn't fix it (and a million other things it seems). Could you provide some advice as to what I might try? In addition to preventing Windows Update from working properly, I think it is related to preventing me from installing slide scanner software from a newly acquired scanner. Thanks in advance for any help you can offer.

[begin dism.log]

[edited for brevity]

2024-03-17 10:42:57, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2024-03-17 10:42:57, Warning DISM DISM Provider Store: PID=2744 TID=3340 Failed to load the provider: C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

2024-03-17 10:42:57, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log

2024-03-17 10:42:57, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log

2024-03-17 10:42:57, Info DISM DISM Manager: PID=13848 TID=7532 Image session successfully loaded from the temporary location: C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC - CDISMManager::CreateImageSession

2024-03-17 10:42:57, Info DISM DISM.EXE: Target image information: OS Version=10.0.19045.3930, Image architecture=amd64

2024-03-17 10:42:57, Info DISM DISM.EXE: Image session version: 10.0.19041.3636

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info CSI 00000001 Shim considered [l:126]'??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.4163_none_7e304ec47c735f2e\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

2024-03-17 10:42:57, Info CSI 00000002 Shim considered [l:123]'??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.4163_none_7e304ec47c735f2e\wcp.dll' : got STATUS_SUCCESS

2024-03-17 10:42:57, Info DISM DISM OS Provider: PID=2744 TID=3340 Determined System directory to be C:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory

2024-03-17 10:42:57, Info DISM DISM Package Manager: PID=2744 TID=3340 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize

2024-03-17 10:42:57, Info CSI 00000001 Shim considered [l:126]'??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.4163_none_7e304ec47c735f2e\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

2024-03-17 10:42:57, Info CSI 00000002 Shim considered [l:123]'??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.4163_none_7e304ec47c735f2e\wcp.dll' : got STATUS_SUCCESS

2024-03-17 10:42:57, Info DISM DISM Package Manager: PID=2744 TID=3340 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize

2024-03-17 10:42:57, Info DISM DISM Package Manager: PID=2744 TID=3340 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info CSI 00000001 Shim considered [l:126]'??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.4163_none_7e304ec47c735f2e\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

2024-03-17 10:42:57, Info CSI 00000002 Shim considered [l:123]'??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.4163_none_7e304ec47c735f2e\wcp.dll' : got STATUS_SUCCESS

2024-03-17 10:42:57, Info DISM DISM Driver Manager: PID=2744 TID=3340 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Warning DISM DISM Provider Store: PID=2744 TID=3340 Failed to load the provider: C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\SysprepProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Transmog Provider: PID=2744 TID=3340 Current image session is [ONLINE] - CTransmogManager::GetMode

2024-03-17 10:42:57, Info DISM DISM Transmog Provider: PID=2744 TID=3340 Audit Mode: [No] - CTransmogManager::Initialize

2024-03-17 10:42:57, Info DISM DISM Transmog Provider: PID=2744 TID=3340 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType

2024-03-17 10:42:57, Info DISM DISM Transmog Provider: PID=2744 TID=3340 Product Type: [WinNT] - CTransmogManager::Initialize

2024-03-17 10:42:57, Info DISM DISM Transmog Provider: PID=2744 TID=3340 Product Type ServerNT : [No] - CTransmogManager::Initialize

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Connecting to the provider located at C:\Users\Michael\AppData\Local\Temp\A1968B85-C813-4B91-8370-A7D6B6CBE8AC\SetupPlatformProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM Provider Store: PID=2744 TID=3340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2024-03-17 10:42:57, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: IBSManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: AppxManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: AppxManager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: ProvManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: ProvManager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: AssocManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: AssocManager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericManager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: SysprepManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: SysprepManager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.

2024-03-17 10:42:57, Info DISM DISM.EXE: Attempting to add the commands from provider: SetupPlatformManager

2024-03-17 10:42:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: SetupPlatformManager.

2024-03-17 10:42:57, Info DISM DISM Package Manager: PID=2744 TID=3340 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine

2024-03-17 10:42:57, Info DISM DISM Package Manager: PID=2744 TID=3340 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine

2024-03-17 10:42:57, Info DISM DISM Package Manager: PID=2744 TID=3340 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

2024-03-17 10:42:57, Info DISM DISM Package Manager: PID=2744 TID=3340 CBS session options=0x20100! - CDISMPackageManager::Internal_Finalize

2024-03-17 10:43:38, Info DISM DISM Package Manager: PID=2744 TID=9556 Error in operation: unexpected internal XML parser error. (CBS HRESULT=0x800f0900) - CCbsConUIHandler::Error

2024-03-17 10:43:38, Info DISM DISM Package Manager: PID=2744 TID=9556 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error

2024-03-17 10:43:38, Error DISM DISM Package Manager: PID=2744 TID=3340 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

2024-03-17 10:43:38, Error DISM DISM Package Manager: PID=2744 TID=3340 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2024-03-17 10:43:38, Error DISM DISM Package Manager: PID=2744 TID=3340 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)

2024-03-17 10:43:38, Error DISM DISM Package Manager: PID=2744 TID=3340 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

2024-03-17 10:43:38, Error DISM DISM Package Manager: PID=2744 TID=3340 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)

2024-03-17 10:43:38, Error DISM DISM Package Manager: PID=2744 TID=3340 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

2024-03-17 10:43:38, Info DISM DISM Package Manager: PID=2744 TID=3340 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2024-03-17 10:43:38, Info DISM DISM Provider Store: PID=2744 TID=3340 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2024-03-17 10:43:38, Info DISM DISM Provider Store: PID=2744 TID=3340 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

[edited for brevity]

[end dism.log]

[begin cbs.log]

2024-03-17 10:42:57, Info CBS TI: --- Initializing Trusted Installer ---

[edited for brevity]

2024-03-17 10:42:59, Info CSI 0000000b Unable to load manifest for component [l:91 ml:140]'amd64_01ea160ac249bd180394f74d796f47b0_b03f5f7f11d50a3a_4.0.15840.260_none_7fd2ac0d25311261'

2024-03-17 10:42:59, Info CSI 0000000c Manifest hash mismatch. Component: [l:91 ml:140]'amd64_01ea160ac249bd180394f74d796f47b0_b03f5f7f11d50a3a_4.0.15840.260_none_7fd2ac0d25311261'

2024-03-17 10:42:59, Error CSI 0000000d (F) CertCreateCTLContext returned ERROR_INVALID_DATA.

[gle=0x80004005]

2024-03-17 10:42:59, Error CSI 0000000e@2024/3/17:17:42:59.710 (F) Attempting to mark store corrupt with category [l:14 ml:15]'CorruptCatalog'[gle=0x80004005]

2024-03-17 10:42:59, Error CSI 0000000f@2024/3/17:17:42:59.710 (F) onecore\base\wcp\componentstore\corruptionrepair.cpp(71): Store corruption detected in function `anonymous-namespace'::VerifyManifestAgainstCatalog expression: 0

FileHashMismatch on resource '\winsxs\catalogs\8069e38a733c056ff920575a68ebe5c98df4427f7aa9ec6ed687dd92d6dc10c5.cat'[gle=0x80004005]

2024-03-17 10:42:59, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.

2024-03-17 10:42:59, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240317163526.log to WER report.

2024-03-17 10:42:59, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240316230933.cab to WER report.

2024-03-17 10:42:59, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240316230155.cab to WER report.

2024-03-17 10:42:59, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240316224655.cab to WER report.

2024-03-17 10:42:59, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20240316175437.cab to WER report.

2024-03-17 10:42:59, Info CBS Not able to add current session file to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-03-17 10:42:59, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-03-17 10:42:59, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-03-17 10:42:59, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-03-17 10:42:59, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-03-17 10:42:59, Info CSI 00000010 Warning: Unable to repair manifest for component ([l:91 ml:140]'amd64_01ea160ac249bd180394f74d796f47b0_b03f5f7f11d50a3a_4.0.15840.260_none_7fd2ac0d25311261') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.

2024-03-17 10:43:00, Info CSI 00000011 Manifest hash for component [l:91 ml:140]'amd64_06b49782991b211a921f3dc45e0b0dff_31bf3856ad364e35_4.0.15840.260_none_69324d858fea50d9' does not match expected value.

Expected:{l:32 b:109001837fe82cc321ae140daecae39b58c111847205a2b4702d7d2035a07f77}

Found:{l:32 b:23c65dba292d6a4fb569373e88f8dd2e19de10cbb0d4ad52348b26f166bea4eb}.

2024-03-17 10:43:00, Info CSI 00000012 Unable to load manifest for component [l:91 ml:140]'amd64_06b49782991b211a921f3dc45e0b0dff_31bf3856ad364e35_4.0.15840.260_none_69324d858fea50d9'

2024-03-17 10:43:00, Info CSI 00000013 Manifest hash mismatch. Component: [l:91 ml:140]'amd64_06b49782991b211a921f3dc45e0b0dff_31bf3856ad364e35_4.0.15840.260_none_69324d858fea50d9'

2024-03-17 10:43:00, Info CSI 00000014 Manifest hash for component [l:91 ml:140]'amd64_06b49782991b211a921f3dc45e0b0dff_31bf3856ad364e35_4.0.15840.260_none_69324d858fea50d9' does not match expected value.

Expected:{l:32 b:109001837fe82cc321ae140daecae39b58c111847205a2b4702d7d2035a07f77}

Found:{l:32 b:23c65dba292d6a4fb569373e88f8dd2e19de10cbb0d4ad52348b26f166bea4eb}.

2024-03-17 10:43:00, Info CSI 00000015 Unable to load manifest for component [l:91 ml:140]'amd64_06b49782991b211a921f3dc45e0b0dff_31bf3856ad364e35_4.0.15840.260_none_69324d858fea50d9'

2024-03-17 10:43:00, Info CSI 00000016 Manifest hash mismatch. Component: [l:91 ml:140]'amd64_06b49782991b211a921f3dc45e0b0dff_31bf3856ad364e35_4.0.15840.260_none_69324d858fea50d9'

2024-03-17 10:43:00, Error CSI 00000017 (F) CertCreateCTLContext returned ERROR_INVALID_DATA.

[gle=0x80004005]

2024-03-17 10:43:00, Error CSI 00000018@2024/3/17:17:43:00.247 (F) Attempting to mark store corrupt with category [l:14 ml:15]'CorruptCatalog'[gle=0x80004005]

2024-03-17 10:43:00, Error CSI 00000019@2024/3/17:17:43:00.247 (F) onecore\base\wcp\componentstore\corruptionrepair.cpp(71): Store corruption detected in function `anonymous-namespace'::VerifyManifestAgainstCatalog expression: 0

FileHashMismatch on resource '\winsxs\catalogs\8069e38a733c056ff920575a68ebe5c98df4427f7aa9ec6ed687dd92d6dc10c5.cat'[gle=0x80004005]

2024-03-17 10:43:00, Info CSI 0000001a Warning: Unable to repair manifest for component ([l:91 ml:140]'amd64_06b49782991b211a921f3dc45e0b0dff_31bf3856ad364e35_4.0.15840.260_none_69324d858fea50d9') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.

2024-03-17 10:43:00, Info CSI 0000001b Manifest hash for component [l:91 ml:140]'amd64_0777159b27be54861a1934033a01b6f5_b77a5c561934e089_4.0.15840.260_none_e45fbe5e0651f98a' does not match expected value.

Expected:{l:32 b:cb38a8a55f4302613614687b0719e88e5d79f9cc4680f1ba411ee4d14366c840}

Found:{l:32 b:d07bdfd8af965e4283a5f77274fc59bee1379af9f221358b81099df31f696345}.

2024-03-17 10:43:00, Info CSI 0000001c Unable to load manifest for component [l:91 ml:140]'amd64_0777159b27be54861a1934033a01b6f5_b77a5c561934e089_4.0.15840.260_none_e45fbe5e0651f98a'

2024-03-17 10:43:00, Info CSI 0000001d Manifest hash mismatch. Component: [l:91 ml:140]'amd64_0777159b27be54861a1934033a01b6f5_b77a5c561934e089_4.0.15840.260_none_e45fbe5e0651f98a'

2024-03-17 10:43:00, Info CSI 0000001e Manifest hash for component [l:91 ml:140]'amd64_0777159b27be54861a1934033a01b6f5_b77a5c561934e089_4.0.15840.260_none_e45fbe5e0651f98a' does not match expected value.

Expected:{l:32 b:cb38a8a55f4302613614687b0719e88e5d79f9cc4680f1ba411ee4d14366c840}

Found:{l:32 b:d07bdfd8af965e4283a5f77274fc59bee1379af9f221358b81099df31f696345}.

2024-03-17 10:43:00, Info CSI 0000001f Unable to load manifest for component [l:91 ml:140]'amd64_0777159b27be54861a1934033a01b6f5_b77a5c561934e089_4.0.15840.260_none_e45fbe5e0651f98a'

2024-03-17 10:43:00, Info CSI 00000020 Manifest hash mismatch. Component: [l:91 ml:140]'amd64_0777159b27be54861a1934033a01b6f5_b77a5c561934e089_4.0.15840.260_none_e45fbe5e0651f98a'

2024-03-17 10:43:00, Error CSI 00000021 (F) CertCreateCTLContext returned ERROR_INVALID_DATA.

[gle=0x80004005]

2024-03-17 10:43:00, Error CSI 00000022@2024/3/17:17:43:00.249 (F) Attempting to mark store corrupt with category [l:14 ml:15]'CorruptCatalog'[gle=0x80004005]

2024-03-17 10:43:00, Error CSI 00000023@2024/3/17:17:43:00.249 (F) onecore\base\wcp\componentstore\corruptionrepair.cpp(71): Store corruption detected in function `anonymous-namespace'::VerifyManifestAgainstCatalog expression: 0

FileHashMismatch on resource '\winsxs\catalogs\8069e38a733c056ff920575a68ebe5c98df4427f7aa9ec6ed687dd92d6dc10c5.cat'[gle=0x80004005]

2024-03-17 10:43:00, Info CSI 00000024 Warning: Unable to repair manifest for component ([l:91 ml:140]'amd64_0777159b27be54861a1934033a01b6f5_b77a5c561934e089_4.0.15840.260_none_e45fbe5e0651f98a') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.

2024-03-17 10:43:00, Info CSI 00000025 Manifest hash for component [l:91 ml:140]'amd64_0fc4e5c9b9e429caef3af79b14353e5a_b03f5f7f11d50a3a_4.0.15840.260_none_a1201b9645c30fc3' does not match expected value.

Expected:{l:32 b:c15919ea82f8a471c2c268bb3c987f4890e3f082a3ac56f09801f8ad69385278}

Found:{l:32 b:b57cceac5243ea773def6e4a96db5bd89d900f7a41429431c2719f43d523c83f}.

2024-03-17 10:43:00, Info CSI 00000026 Unable to load manifest for component [l:91 ml:140]'amd64_0fc4e5c9b9e429caef3af79b14353e5a_b03f5f7f11d50a3a_4.0.15840.260_none_a1201b9645c30fc3'

2024-03-17 10:43:00, Info CSI 00000027 Manifest hash mismatch. Component: [l:91 ml:140]'amd64_0fc4e5c9b9e429caef3af79b14353e5a_b03f5f7f11d50a3a_4.0.15840.260_none_a1201b9645c30fc3'

2024-03-17 10:43:00, Info CSI 00000028 Manifest hash for component [l:91 ml:140]'amd64_0fc4e5c9b9e429caef3af79b14353e5a_b03f5f7f11d50a3a_4.0.15840.260_none_a1201b9645c30fc3' does not match expected value.

Expected:{l:32 b:c15919ea82f8a471c2c268bb3c987f4890e3f082a3ac56f09801f8ad69385278}

[edited for brevity]

[end cbs.log]

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,575 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Wesley Li 8,780 Reputation points
    2024-03-21T02:20:34.4666667+00:00

    Hello

    You could try to extract the wim with command "dism.exe /mount-wim /wimfile:winpe.wim /index:1 /mountdir:c:\MyMountDir" then try to fix with this source.

    For adavanced troubleshooting, you could try to capture the process monitor log with the fixing process.

    There should be more exact information for the exact corrupted file path (not found). But this may be complicated.

    Or you could try to perform an in-place upgrade repair with an iso installation.

    0 comments No comments

  2. Rocky714 0 Reputation points
    2024-03-22T04:03:03.0133333+00:00

    The command "dism.exe /mount-wim /wimfile:winpe.wim /index:1 /mountdir:c:\MyMountDir" appeared to fail with a "Error: 2, The system cannot find the file specified" message. The dism.log contained the following.

    2024-03-21 19:02:33, Warning DISM DISM Provider Store: PID=7376 TID=12712 Failed to load the provider: C:\Windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    and

    2024-03-21 19:02:33, Warning DISM DISM Provider Store: PID=7376 TID=12712 Failed to load the provider: C:\Windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    Nothing else of note was in the log but nothing significant seemed to happen to fix the problem so I guess these were necessary but not executed and therefore nothing was fixed.

    I tried to use Process Monitor to see what was going on with the error but there was just way too information (multiple megabytes of text-like data in the PLM file and way too little expertise on my part) to know what I was looking for. There are plenty of errors (non-"SUCCESS"es) but many seem run of the mill that it's hard to tell which are significant and which are not. DISM runs long enough that it's hard to pinpoint the precise time of the error so it's largely hopeless for me.

    I'm pretty resigned to having to do an in-place upgrade repair but looking at the instructions (at https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html), I think I have a problem. The instructions say that the build of the iso image from which upgrade repair will done needs to be greater that or equal to that of the install. For some reason, the latest build image I have on hand is 22H2 19041 while my install is that of 22H2 19045 (could that be why the DISM repairs fail?). I tried looking for a download of a 19045 iso but could not find any. My install is from 2 years ago so I probably recycled the USB drive of the original install. I saw allusions to Microsoft not distributing different build images anymore. Is that true? If so, I'm truly scr**ed. This whole escapade was started because I couldn't seem to install the software of a new slide scanner I bought. I've been engaging with their tech support but I'm already past when I can return the scanner. They don't yet know I've been diverted by this corruption issue - so I don't know if it's their software or Windows. If I can't fix this, I've got a very expensive door stop.

    I implore any that can help find/provide a 19045 Win 10 Home build image 19045 to help (if that's truly what it takes) or alternative fix method. Continuing thanks to Wesley and in advance to any others that can help.

    -Rocky714

    0 comments No comments

  3. Rocky714 0 Reputation points
    2024-03-27T01:57:25.9833333+00:00

    Well, there doesn't seem to be much response. Can I infer that my only option at this point is to start from scratch with a complete reinstall with the only build (19041) build of Windows 10 I have access to? I don't like the idea but if that's my only option, I guess I have to take it.

    The only remaining question I'd have is whether entering my license will cause an issue at install time. I'll be entering my existing license on another install albeit on the existing machine. Will it be understood as an existing registration or will it think that it's another registration and complain that I'm trying something that's not permitted. Thanks.

    -Rocky714

    0 comments No 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.