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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-06-02T22:43:59+00:00

     does anyone know where all the Chinese characters are originating?

    For DISM you could use its /LogLevel: and /LogPath: operands to avoid it.

    Otherwise I would wonder if you had some of the real corruption that this poster saw regarding dism.exe itself.

    http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/issue-with-installing-updates-on-windows-81/24b91da6-fdbe-42dd-96c6-3cc91062054b?page=5&tm=1401734795434

    Care to check your results for the same Powershell pipeline?

    PS C:\windows> dir -Filter "*dism.exe" -Recurse  -ErrorAction:SilentlyContinue ft Length, FullName -AutoSize -HideTableHeaders

    Note that shows you the complete command line including the prefix, so you know where to start it from.  In view of the fact that we were both having problems with Authorization (which accounts for the ErrorAction switch) it would probably be a good idea to do this in the Administrator Powershell window.  Then in order to get back to the desired directory level all you would need to enter from being at the Admin default of  $env:windir\System32  would be:  cd ..

    BTW the AutoSize switch only sizes according to the size of the window so it may help to make your window bigger than it already is, e.g. if necessary wider than Maximized.

    HTH

    Robert

    This seems a bit too complicated for me at this point in the game. A lot of what you just explained was like a different language to me. I'm not sure I understand the differences between powershell and system levels and from my experience in the past with other computers, if I'm not completely comfortable with something, don't do it as I might make things worse off. I do appreciate your willingness to help. Maybe someone else with more experience can try this out?

    I really don't know how "real" corruption could've taken place as I've done all updates per the book as far as I know.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-06-03T02:11:11+00:00

    I do not know if you can use an OEM key code to activate it.

    My computer came with Windows 8 on it (Toshiba 64bit computer) and the product ID has "oem" within the numbers. So I assume the product key I have is an oem copy? UPDATE: I've looked through comments and it looks like OEM product key works for some and not others??? Maybe I'm missing something, but it sounds like I'm out of luck until I see for certain an OEM key code will work (I was able to get the key code by downloading some software).

    Here's what one of the links states about OEMs . . .

    • "Microsoft made all Windows 8.1 media reject Windows 8.0 OEM/Retail product keys. → Workaround involves installation with generic product key and activating with Windows 8.0 product key.
    • Microsoft unfortunately made the retail downloader inaccessible for major OEM vendor and small system builder OEM Product Keys. → No current fix to use the downloader except to use a retail key if you have one or obtain a MSDN/Technet .iso from unofficial sources

    Note the download requires a retail product key (Windows 8.0 or 8.1) and will not work with OEM Product Keys from major vendors which are hidden and reside within the system BIOS or minor system builder OEM licenses with a 25 digit product code.

    The .iso obtained via this method is locked to the Windows edition (Core or Professional) unlike a MSDN/Technet .iso. It is however possible to download a retail .iso and use it to clean install on an OEM system providing both license are Windows 8.0/8.1 (C0re) or both licenses are Windows 8.0/8.1 Professional.

    The fact is OEMs do not always install Windows properly and this combined with the forcing of such a critical update via the Microsoft store leads to a very negative migration to Windows 8.1 for many a user."

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-06-03T03:02:42+00:00

    Okay, looks like I can't even download the ISO file. When I enter the Product Key, the downloader states "This product key cannot be used to install a retail version of Windows 8."

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-06-03T18:58:44+00:00

    I do not know if you can use an OEM key code to activate it.

    My computer came with Windows 8 on it (Toshiba 64bit computer) and the product ID has "oem" within the numbers. So I assume the product key I have is an oem copy? UPDATE: I've looked through comments and it looks like OEM product key works for some and not others??? Maybe I'm missing something, but it sounds like I'm out of luck until I see for certain an OEM key code will work (I was able to get the key code by downloading some software).

    Here's what one of the links states about OEMs . . .

    • "Microsoft made all Windows 8.1 media reject Windows 8.0 OEM/Retail product keys. → Workaround involves installation with generic product key and activating with Windows 8.0 product key.
    • Microsoft unfortunately made the retail downloader inaccessible for major OEM vendor and small system builder OEM Product Keys. → No current fix to use the downloader except to use a retail key if you have one or obtain a MSDN/Technet .iso from unofficial sources

    Note the download requires a retail product key (Windows 8.0 or 8.1) and will not work with OEM Product Keys from major vendors which are hidden and reside within the system BIOS or minor system builder OEM licenses with a 25 digit product code.

    The .iso obtained via this method is locked to the Windows edition (Core or Professional) unlike a MSDN/Technet .iso. It is however possible to download a retail .iso and use it to clean install on an OEM system providing both license are Windows 8.0/8.1 (C0re) or both licenses are Windows 8.0/8.1 Professional.

    The fact is OEMs do not always install Windows properly and this combined with the forcing of such a critical update via the Microsoft store leads to a very negative migration to Windows 8.1 for many a user."

    Okay, looks like I can't even download the ISO file. When I enter the Product Key, the downloader states "This product key cannot be used to install a retail version of Windows 8."

    Wow, I'm glad you checked into that.  Since I had originally purchased a retail copy of Windows 8 Pro to upgrade my Windows 7 PC, it was not an issue for me.  That is a really sad decision on Microsoft's part, but considering the way some OEM's customize (and sometimes butcher) their Windows software, I guess I can understand some of the logic behind it.  However, if Microsoft refuses to make the ISO or disk available, then it should at least be offered by the OEM PC manufacturer.  Have you tried to contact your PC manufacturer?  Of course, if you were going to re-format and re-install from scratch, you probably already have a hidden "recovery" partition on your hard drive.  So, you could do a clean install of Windows 8.0 again and then update to 8.1 via the Windows Store.  But you would lose everything.

    I understand that Microsoft faces many more challenges than Apple.  The only way to use OSX (legally) is to purchase a Mac computer, so Apple controls the hardware and software.  Microsoft simply licenses their software and the individual manufacturers can pretty much do anything they want with it.

    That being said, Microsoft should still make the retail ISO's available for OEM PC customers rather than forcing them to buy a retail version or spend a fortune to join MSDN.

    It appears that if your PC vendor can't (or won't) help, you'll need to spend the $120 for a retail version, if you currently have plain vanilla Windows 8.1, or $200 if you have Windows 8.1 Pro.  They are often offered at discounted prices.  IIRC, you cannot do a repair install (upgrade) from a higher version (Pro) to a lower version (Standard).  My guess is that your laptop did NOT come with Pro.  The good thing about "upgrading" to a retail version is that after you do, you're all set for future upgrades, including Windows 9.

    Was this answer helpful?

    0 comments