DISM /restoreHealth fails with 0x800f081f AFTER 8.1 update successfully installed

Anonymous
2014-04-11T16:18:28+00:00

I'm concerned about having a machine in a broken state going forward, though.

here's what I ran:

C:\Windows\Logs\CBS>dism /online /cleanup-image /restoreHealth

Deployment Image Servicing and Management tool

Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

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

The restore operation failed. Either the repair source was not found or the comp

onent store cannot be repaired.

Error: 0x800f081f

DISM failed. No operation was performed.

For more information, review the log file.

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

************************************************************************************

here is the DISM.log:

2014-04-11 11:38:04, Info                  DISM   PID=11556 TID=8436 Scratch directory set to 'C:\Users\tripp\AppData\Local\Temp'. - CDISMManager::put_ScratchDir

2014-04-11 11:38:04, Info                  DISM   PID=11556 TID=8436 DismCore.dll version: 6.3.9600.17031 - CDISMManager::FinalConstruct

2014-04-11 11:38:04, Info                  DISM   PID=11556 TID=8436 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadLocalImageSession

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Getting Provider DISMLogger - CDISMProviderStore::GetProvider

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Getting Provider DISMLogger - CDISMProviderStore::GetProvider

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:04, Info                  DISM   DISM Manager: PID=11556 TID=8436 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Getting Provider DISMLogger - CDISMProviderStore::GetProvider

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:04, Info                  DISM   DISM.EXE: 

2014-04-11 11:38:04, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->

2014-04-11 11:38:04, Info                  DISM   DISM.EXE: 

2014-04-11 11:38:04, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.3.9600, Running architecture=amd64, Number of processors=8

2014-04-11 11:38:04, Info                  DISM   DISM.EXE: Dism.exe version: 6.3.9600.17031

2014-04-11 11:38:04, Info                  DISM   DISM.EXE: Executing command line: dism  /online /cleanup-image /restoreHealth

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Getting Provider FolderManager - CDISMProviderStore::GetProvider

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:04, Info                  DISM   DISM Provider Store: PID=11556 TID=8436 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:04, Info                  DISM   DISM Manager: PID=11556 TID=8436 physical location path: C:\ - CDISMManager::CreateImageSession

2014-04-11 11:38:04, Info                  DISM   DISM Manager: PID=11556 TID=8436 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation

2014-04-11 11:38:05, Info                  DISM   DISM Manager: PID=11556 TID=8436 Successfully loaded the ImageSession at "C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38" - CDISMManager::LoadRemoteImageSession

2014-04-11 11:38:05, Info                  DISM   DISM Image Session: PID=8880 TID=212 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\OSProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:05, Info                  DISM   DISM OS Provider: PID=8880 TID=212 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect

2014-04-11 11:38:05, Info                  DISM   DISM OS Provider: PID=8880 TID=212 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect

2014-04-11 11:38:05, Info                  DISM   DISM OS Provider: PID=8880 TID=212 Host OS verion is 6.3 - CDISMOSServiceManager::SetDllSearchPath

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\LogProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\PEProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:05, Warning               DISM   DISM Provider Store: PID=8880 TID=212 Failed to Load the provider: C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Getting Provider DISMLogger - CDISMProviderStore::GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM Manager: PID=11556 TID=8436 Image session successfully loaded from the temporary location: C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38 - CDISMManager::CreateImageSession

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Getting Provider OSServices - CDISMProviderStore::GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM.EXE: Target image information: OS Version=6.3.9600.17031, Image architecture=amd64

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:05, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Package Manager: PID=8880 TID=212 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize

2014-04-11 11:38:06, Info                  DISM   DISM Package Manager: PID=8880 TID=212 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize

2014-04-11 11:38:06, Info                  DISM   DISM Package Manager: PID=8880 TID=212 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\IBSProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM OS Provider: PID=8880 TID=212 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive

2014-04-11 11:38:06, Info                  DISM   DISM Driver Manager: PID=8880 TID=212 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\Wow64provider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Warning               DISM   DISM Provider Store: PID=8880 TID=212 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)

2014-04-11 11:38:06, Warning               DISM   DISM Provider Store: PID=8880 TID=212 Failed to Load the provider: C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\Wow64provider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\EmbeddedProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Warning               DISM   DISM Provider Store: PID=8880 TID=212 Failed to Load the provider: C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\AppxProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\AssocProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\GenericProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Loading Provider from location C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Connecting to the provider located at C:\Users\tripp\AppData\Local\Temp\DA023AD7-BFB2-4FA5-9784-B6E1ED49DF38\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

2014-04-11 11:38:06, Info                  DISM   DISM Transmog Provider: PID=8880 TID=212 Current image session is [ONLINE] - CTransmogManager::GetMode

2014-04-11 11:38:06, Info                  DISM   DISM Transmog Provider: PID=8880 TID=212 Audit Mode: [No] - CTransmogManager::Initialize

2014-04-11 11:38:06, Info                  DISM   DISM Transmog Provider: PID=8880 TID=212 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType

2014-04-11 11:38:06, Info                  DISM   DISM Transmog Provider: PID=8880 TID=212 Product Type: [WinNT] - CTransmogManager::Initialize

2014-04-11 11:38:06, Info                  DISM   DISM Transmog Provider: PID=8880 TID=212 Product Type ServerNT : [No] - CTransmogManager::Initialize

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IBSManager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericManager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericManager.

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager

2014-04-11 11:38:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2014-04-11 11:38:06, Info                  DISM   DISM Package Manager: PID=8880 TID=212 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine

2014-04-11 11:38:06, Info                  DISM   DISM Package Manager: PID=8880 TID=212 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine

2014-04-11 11:38:06, Info                  DISM   DISM Package Manager: PID=8880 TID=212 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

2014-04-11 11:38:06, Info                  DISM   DISM Package Manager: PID=8880 TID=212 CBS session options=0x48100! - CDISMPackageManager::Internal_Finalize

2014-04-11 11:47:13, Info                  DISM   DISM Package Manager: PID=8880 TID=212  - CDISMPackageManager::Internal_Finalize

2014-04-11 11:47:13, Info                  DISM   DISM Package Manager: PID=8880 TID=212 <----- Starting corruption detect/repair info -----> - CDISMPackageManager::Internal_Finalize

2014-04-11 11:47:13, Info                  DISM   DISM Package Manager: PID=8880 TID=212  - CDISMPackageManager::Internal_Finalize

2014-04-11 11:47:13, Info                  DISM   DISM Package Manager: PID=8880 TID=212 

=================================

Checking System Update Readiness.

Summary:

Operation: Detect and Repair 

Operation result: 0x0

Last Successful Step: Entire operation completes.

Total Detected Corruption:     0

     CBS Manifest Corruption:     0

     CBS Metadata Corruption:     0

     CSI Manifest Corruption:     0

     CSI Metadata Corruption:     0

     CSI Payload Corruption:     0

Total Repaired Corruption:     0

     CBS Manifest Repaired:     0

     CSI Manifest Repaired:     0

     CSI Payload Repaired:     0

     CSI Store Metadata refreshed:     True

Total Operation Time: 546 seconds.

  • CDISMPackageManager::Internal_Finalize

2014-04-11 11:47:13, Info                  DISM   DISM Package Manager: PID=8880 TID=212  - CDISMPackageManager::Internal_Finalize

2014-04-11 11:47:13, Info                  DISM   DISM Package Manager: PID=8880 TID=212 <----- Ending corruption detect/repair info -----> - CDISMPackageManager::Internal_Finalize

2014-04-11 11:47:13, Info                  DISM   DISM Package Manager: PID=8880 TID=212  - CDISMPackageManager::Internal_Finalize

2014-04-11 11:47:13, Info                  DISM   DISM Package Manager: PID=8880 TID=212 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock

2014-04-11 11:47:13, Error                 DISM   DISM Package Manager: PID=8880 TID=212 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

2014-04-11 11:47:13, Info                  DISM   DISM Package Manager: PID=8880 TID=212 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2014-04-11 11:47:13, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F081F

2014-04-11 11:47:13, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2014-04-11 11:47:13, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2014-04-11 11:47:13, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2014-04-11 11:47:13, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider

2014-04-11 11:47:13, Info                  DISM   DISM Package Manager: PID=8880 TID=212 Finalizing CBS core. - CDISMPackageManager::Finalize

2014-04-11 11:47:13, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider

2014-04-11 11:47:13, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider

2014-04-11 11:47:13, Info                  DISM   DISM Provider Store: PID=8880 TID=212 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider

2014-04-11 11:4

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2014-11-29T15:17:47+00:00

 get error 87 when I run the above statement in command prompt running as admin.

Make sure that the cmd window title is:  Administrator: Command Prompt.

Also, I don't think case is a factor but all the help does show it so it may be an idea to fix that too.

Here is another related command which could give you more information

    Dism.exe  /Online  /Cleanup-Image /AnalyzeComponentStore

Otherwise use the  DISM.log  to find out what is going on.  You could also run ProcMon to help find and supplement any other diagnostics which are available.

Good luck

Robert

Was this answer helpful?

10+ people found this answer helpful.
0 comments

95 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-05-05T01:56:32+00:00

    Can I have an amen, brother!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-05-02T03:00:33+00:00

    I'm also having this issue and decided to refresh my PC.

    Issue is unavoidable unless you won't clean your disk after updating the update 1 for Windows 8.1

    Best thing to do right now is avoid deleting any windows update via disk cleanup or any third party software that cleans the windows update folder or so.

    Nice work Microsoft. Giving us an update with a new troublesome features.

    I had no problem installing the 8.1 update per se, however shortly afterwards I ran Disk Cleanup including system files with windows updates.  Then when I ran DISM /online /cleanup-image /scanhealth (or restorehealth), it said DISM failed with error 0x800f081f.

    After much reading of various forums, and trying most everything to no avail, I restored my PC to a pre-update image that I had saved and installed the updates again.  This time I did not run Disk Cleanup, and the DISM commands showed no component store corruption.  I then ran DISM /online /cleanup-image /analyzecomponentstore and it suggested that I do a cleanup.  So, I ran DISM /online /cleanup-image/startcomponentcleanup and it failed saying the component store was corrupted.  The DISM scanhealth or restorehealth gave me the same 0x800f081f error again.  So, I again restored my pre-update image, ran windows update again.  This time I only ran the DISM check, scan or restore health commands and they all completed without error.

    So, it appears that if Disk Cleanup w/System Files or DISM /online /cleanup-image /startcomponentcleanup command is run in attempts to cleanup the component store, it actually corrupts it. or at lease tells us it's corrupted.

    By the way, when I ran either Disk Cleanup or the DISM cleanup on my pre-update restored image, they ran fine and did not corrupt the component store.

    I've even disabled the scheduled task in task scheduler that periodically is supposed to clean the component store, however that task did not introduce any corruption when I tested it.  I appears that only running the DISM /online /Cleanup-Image /StartComponentCleanup or Disk Cleanup with the system files option corrupts the component store.

    I'm afraid that this could be a serious problem going forward.  While most posts refer to the inability to update to KB2919355, I think that the component store corruption issue has gone largely un-noticed, but may be at the root of the problem.

    So, for those of you who successfully refreshed or re-installed your OS, did anyone try to reclaim disk space by running either the disk cleanup (including system and windows update files) or the DISM cleanup commands mentioned above?  If so, did you still get the component store corruption error?

    Of course, I don't suggest trying it unless you have a backup image or at least a good system restore point.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-04-25T13:04:44+00:00

    Billchitbill is correct:

    1. had already run chkdsk /f, no issues
    2. had already run sfc /scannow, no issues
    3. had booted in safe mode with network access
    4. had tried a million other things I'd seen on this forum and on eightforums.com

    was worried that this will prevent future updates since this is the new baseline.  After spending many hours on it, I gave up & reinstalled.  Thanks, MS.

    Glad your reinstall worked. After many unsuccessful attempts I was finally able to install KB2919355. I managed to fix some corruption in the store by manually extracting some files from a prior update, I won't bore you with the long and tedious details. After restoring those files I ran sfc /scannow which showed no problem. I then ran Dism /Restorehealth and received Error 0x800f081f. I then reviewed the CBS.log to get an idea what the problem was. Here is the result from the log:

    Summary:

    Operation: Detect and Repair 

    Operation result: 0x0

    Last Successful Step: Entire operation completes.

    Total Detected Corruption: 0

    CBS Manifest Corruption: 0

    CBS Metadata Corruption: 0

    CSI Manifest Corruption: 0

    CSI Metadata Corruption: 0

    CSI Payload Corruption: 0

    Total Repaired Corruption: 0

    CBS Manifest Repaired: 0

    CSI Manifest Repaired: 0

    CSI Payload Repaired: 0

    CSI Store Metadata refreshed: True

    Note the log reports no corruption even though RestoreHealth indicates via the command line there is a problem. I then decided to again attempt to install KB2919355 which successfully installed. I have had no problems since. 

    I have found several references to discussions to the effect the update may have introduced a bug wherein RestoreHealth generates the error message when in reality there is no error. Since the update, every time I run RestoreHealth I receive the same error message but the CBS.log shows no corruption. 

    Here is a another reference to the issue on another forum:

    http://superuser.com/questions/744055/component-store-is-corrupted-0x800f081f

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-04-25T09:40:30+00:00

    This is a sort of polite test reply. I tried replying last week, but I had been locked out of the thread for whatever reason.

      I've tried every suggestion in this thread and several others, and the only thing that worked reliably was to do a system restore. I hate doing those for an update, and I'd hoped someone had found the answer.

    Was the "USERPROFILES" (C:\users) moved? No, but I robocopied it anyway per the instructions of some site, to D:. It only created a directory so gigantic and nested, windows refused to delete it (unless I again used "robocopy").

    Was Chkdsk OK? yes.

    SFC Scan? Yes, but the DISM command to erase old/unused update packages seemed to mess it up again.

    I will never run that command again, apparently it messes with something that then appears missing to windows.

    And now if this goes through, I wanted to thank the OP and some of the users here.

    If it doesn't, no biggie.

    Was this answer helpful?

    0 comments