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-06-02T18:58:52+00:00

    I've missed where the in-place repair install instructions are in this thread (I went back through the thread again). I think I see where to download an Win 8.1 ISO file with a Win 8 product key. If I am able to download the ISO file, what do I do next to do the in-place repair install? Do you use the Windows refresh functionality? Looks like I need to save the ISO file to a DVD? As I stated in an earlier post, my computer came with Windows 8 on it and I have no media at all other than the Windows 8 recovery thumb drive I made when I first got the computer. Can I use a Windows 8.1 ISO file to do an in-place repair install with the above conditions?

    I think I've found the way to do this via http://www.eightforums.com/tutorials/26095-repair-install-windows-8-a.html.

    It states clearly that "If you have Windows 8.1 Update installed, then you must use a Windows 8.1 Update ISO."

    If I download the ISO for 8.1 will it be the 8.1 update ISO or just the 8.1 ISO? I have 8.1 update installed so it says I need the ISO that contains the update in it? Ronnie - did you have 8.1 update already installed or were you having trouble installing the update? If already installed, wouldn't the ISO install the update too and therefore not need to re-install Kb2919355?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-06-02T18:14:04+00:00

    Since I could never get any firm official answers and did not want to take any chances going forward, I opted to do an in-place repair install per the instructions that I and others referenced in this forum. Unlike a reformat, a repair install simply installs Windows 8.1 over itself, and maintains all your data files, program installations, apps and almost all of your personalization settings.  Since I used an ISO file that was apparently the initial release of Windows 8.1, I had to install over 30 updates, including the dreaded KB2919355 update, which installed fine.  Yes, it took time, but no aggravation trying to find all your program install files or discs and their serial numbers of key codes.  I, as well as others, have had complete success with the in-place repair install .  I can run Disk Cleanup with System Files and any of the DISM commands without any corruption or failure messages.  The "new" DISM log has no Chinese characters.

    Ronnie I appreciate your help with all of this. You have been very dedicated in trying to help fix this issue.

    I've missed where the in-place repair install instructions are in this thread (I went back through the thread again). I think I see where to download an Win 8.1 ISO file with a Win 8 product key. If I am able to download the ISO file, what do I do next to do the in-place repair install? Do you use the Windows refresh functionality? Looks like I need to save the ISO file to a DVD? As I stated in an earlier post, my computer came with Windows 8 on it and I have no media at all other than the Windows 8 recovery thumb drive I made when I first got the computer. Can I use a Windows 8.1 ISO file to do an in-place repair install with the above conditions? (UPDATE: I think I may have figured this out - see following post.)

    I might wait to see what happens with the June updates before doing this if I can, but I greatly appreciate your help.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-06-02T18:02:31+00:00

    Okay, so I was able to successfully install the update, but I should now try to uninstall it (in order to get Dism restorehealth to work? does anyone know where all the Chinese characters are originating?) when I see there are many are having problems installing it to begin with? Would I need to go to my Windows Update and uninstall every patch back to April one at a time and then run restorehealth to see if it works and then reinstall all the patches again? I don't think I want to mess with uninstalling something and run the risk of not being able to reinstall - especially with the way Windows 8/8.1 seems to be working and terrible reliability track record.                 

    I also do not want to re-format or refresh or reset my computer. I bought my computer online thinking it was Windows 7 as advertised and then I get Windows 8. I decided to give it a try and it has been nothing but trouble - seems like every monthly update brings something new that is not good. If I have to refresh or reset, doesn't it return everything to Windows 8? So then I need to re-update to 8.1 again (that took about 6 hours to do last time with all of the driver updates and such - maybe I should just stay at Win 8 but then I have less than 2 years of security updates?) and then go through all the other updates including 8.1 update that took another hour or so to update. Then if it is a re-format/reset, then I have to reinstall everything all over again

    • all my documents and programs which will be another 6 hours or so. And then hope everything worked as planned? Uh huh. One other note, I just found out about this issue a week or two ago and I checked system restore to see if I could go back prior to the Win 8.1 update being installed (April) and I didn't have any restore points prior to that. So that wasn't an option.

    To say the least, I'm not happy with this response. I'm not going to go through all of that just to get dism restorehealth to work (maybe) when I've done nothing wrong or out of the ordinary with my computer - I do the monthly updates and don't fiddle with registries or anything crazy. I think I'd rather leave restorehealth not working and just hope I can continue to use my computer for a while before I have to move on - maybe to a Mac.                                                                                                                 

    Well, I feel your frustration, but an isolated statement from "someone in Product Development" is not necessarily an official response from Microsoft, so I would take it with a grain of salt.

    First of all, as far as I know, it has not yet been established if the DISM error message is actually valid.  That is, is there actually corruption in the component store, or did the update just break the DISM processes so that perhaps it reports an error that doesn't even exist?

    Since I could never get any firm official answers and did not want to take any chances going forward, I opted to do an in-place repair install per the instructions that I and others referenced in this forum.

    Unlike a reformat, a repair install simply installs Windows 8.1 over itself, and maintains all your data files, program installations, apps and almost all of your personalization settings.  Since I used an ISO file that was apparently the initial release of Windows 8.1, I had to install over 30 updates, including the dreaded KB2919355 update, which installed fine.  Yes, it took time, but no aggravation trying to find all your program install files or discs and their serial numbers or key codes.  I, as well as others, have had complete success with the in-place repair install .  I can run Disk Cleanup with System Files and any of the DISM commands without any corruption or failure messages.  The "new" DISM log has no Chinese characters.

    You may be perfectly fine going forward if you decide to simply do nothing.  Perhaps MS will ultimately release a magical fix.  If not, and you encounter problems in the future, you can still try a repair install then.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-06-02T16:35:17+00:00

    Update per following website:

    http://thehotfixshare.net/board/index.php?showtopic=21423

    "I received another call about this support case from someone in Product Development. After a brief discussion, he basically said I (and, by extension, others with this problem) may have to re-format.

    Here are the scenarios as I currently understand them.

    1. If you A) do not yet have kb2919355 installed (because, say, you refused to install it from Windows Update or it did not install successfully); and are unable to successfully run dism /online /cleanup-image /restorehealth, then you will likely have to re-format, regardless of the fix Microsoft will be releasing.
    2. If you installed kb2919355 and cannot uninstall it, you will also likely have to re-format.
    3. If you installed kb2919355, are able to successfully uninstall it, and then successfully run dism /online /cleanup-image /startcomponentcleanup , then you will likely NOT have to re-format.

    Incidentally, he also said that this problem affects a lot of people, although he didn't elaborate as to how many. He did say, however, that many others are unable to install kb2919355 in the first place."

    Okay, so I was able to successfully install the update, but I should now try to uninstall it (in order to get Dism restorehealth to work? does anyone know where all the Chinese characters are originating?) when I see there are many are having problems installing it to begin with? Would I need to go to my Windows Update and uninstall every patch back to April one at a time and then run restorehealth to see if it works and then reinstall all the patches again? I don't think I want to mess with uninstalling something and run the risk of not being able to reinstall - especially with the way Windows 8/8.1 seems to be working and terrible reliability track record.

    I also do not want to re-format or refresh or reset my computer. I bought my computer online thinking it was Windows 7 as advertised and then I get Windows 8. I decided to give it a try and it has been nothing but trouble - seems like every monthly update brings something new that is not good. If I have to refresh or reset, doesn't it return everything to Windows 8? So then I need to re-update to 8.1 again (that took about 6 hours to do last time with all of the driver updates and such - maybe I should just stay at Win 8 but then I have less than 2 years of security updates?) and then go through all the other updates including 8.1 update that took another hour or so to update. Then if it is a re-format/reset, then I have to reinstall everything all over again

    • all my documents and programs which will be another 6 hours or so. And then hope everything worked as planned? Uh huh. One other note, I just found out about this issue a week or two ago and I checked system restore to see if I could go back prior to the Win 8.1 update being installed (April) and I didn't have any restore points prior to that. So that wasn't an option.

    To say the least, I'm not happy with this response. I'm not going to go through all of that just to get dism restorehealth to work (maybe) when I've done nothing wrong or out of the ordinary with my computer - I do the monthly updates and don't fiddle with registries or anything crazy. I think I'd rather leave restorehealth not working and just hope I can continue to use my computer for a while before I have to move on - maybe to a Mac.

    Was this answer helpful?

    0 comments