Forum Discussion

PCS-Sydney's avatar
PCS-Sydney
Copper Contributor
Jul 03, 2023

Windows Server 2019 DISM hang

Hoping someone might be able to offer guidance on this.

 

We have a Windows Server 2019 that won't run DISM or SFC.

 

DISM hangs when performing scanhealth - command issued was DISM /ONLINE /CLEANUP-IMAGE /SCANHEALTH

 

Log file is as follows - the command hangs at the last line and was left for over 30 minutes;

 

2023-07-03 11:04:50, Info DISM PID=17380 TID=10904 Scratch directory set to 'C:\Users\ADMINI~1.STP\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2023-07-03 11:04:50, Info DISM PID=17380 TID=10904 DismCore.dll version: 10.0.17763.1697 - CDISMManager::FinalConstruct
2023-07-03 11:04:50, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2023-07-03 11:04:50, Info DISM PID=17380 TID=10904 Successfully loaded the ImageSession at "C:\Windows\system32\Dism" - CDISMManager::LoadLocalImageSession
2023-07-03 11:04:50, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=17380 TID=10904 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=17380 TID=10904 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=17380 TID=10904 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2023-07-03 11:04:50, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2023-07-03 11:04:50, Info DISM DISM Manager: PID=17380 TID=10904 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2023-07-03 11:04:50, Info DISM DISM.EXE:
2023-07-03 11:04:50, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2023-07-03 11:04:50, Info DISM DISM.EXE:
2023-07-03 11:04:50, Info DISM DISM.EXE: Host machine information: OS Version=10.0.17763, Running architecture=amd64, Number of processors=8
2023-07-03 11:04:50, Info DISM DISM.EXE: Dism.exe version: 10.0.17763.3406
2023-07-03 11:04:50, Info DISM DISM.EXE: Executing command line: dism /online /cleanup-image /scanhealth
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=17380 TID=10904 Connecting to the provider located at C:\Windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Manager: PID=17380 TID=10904 physical location path: C:\ - CDISMManager::CreateImageSession
2023-07-03 11:04:50, Info DISM DISM Manager: PID=17380 TID=10904 Event name for current DISM session is Global\{00FFE5F9-237F-47CD-83C4-E72653F743A0} - CDISMManager::CheckSessionAndLock
2023-07-03 11:04:50, Info DISM DISM Manager: PID=17380 TID=10904 Create session event 0x210 for current DISM session and event name is Global\{00FFE5F9-237F-47CD-83C4-E72653F743A0} - CDISMManager::CheckSessionAndLock
2023-07-03 11:04:50, Info DISM DISM Manager: PID=17380 TID=10904 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2023-07-03 11:04:50, Info DISM DISM Manager: PID=17380 TID=10904 Successfully loaded the ImageSession at "C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A" - CDISMManager::LoadRemoteImageSession
2023-07-03 11:04:50, Info DISM DISM Image Session: PID=22184 TID=21716 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM OS Provider: PID=22184 TID=21716 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2023-07-03 11:04:50, Info DISM DISM OS Provider: PID=22184 TID=21716 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2023-07-03 11:04:50, Warning DISM DISM Provider Store: PID=22184 TID=21716 Failed to load the provider: C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2023-07-03 11:04:50, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2023-07-03 11:04:50, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
2023-07-03 11:04:50, Info DISM DISM Manager: PID=17380 TID=10904 Image session successfully loaded from the temporary location: C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A - CDISMManager::CreateImageSession
2023-07-03 11:04:50, Info DISM DISM.EXE: Target image information: OS Version=10.0.17763.4377, Image architecture=amd64
2023-07-03 11:04:50, Info DISM DISM.EXE: Image session version: 10.0.17763.1697
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.4121_none_5703f42b990865ed\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2023-07-03 11:04:50, Info CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.4121_none_5703f42b990865ed\wcp.dll' : got STATUS_SUCCESS
2023-07-03 11:04:50, Info DISM DISM Package Manager: PID=22184 TID=21716 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2023-07-03 11:04:50, Info CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.4121_none_5703f42b990865ed\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2023-07-03 11:04:50, Info CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.4121_none_5703f42b990865ed\wcp.dll' : got STATUS_SUCCESS
2023-07-03 11:04:50, Info DISM DISM Package Manager: PID=22184 TID=21716 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2023-07-03 11:04:50, Info DISM DISM Package Manager: PID=22184 TID=21716 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.4121_none_5703f42b990865ed\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2023-07-03 11:04:50, Info CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.4121_none_5703f42b990865ed\wcp.dll' : got STATUS_SUCCESS
2023-07-03 11:04:50, Info DISM DISM Driver Manager: PID=22184 TID=21716 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Warning DISM DISM Provider Store: PID=22184 TID=21716 Failed to load the provider: C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\SysprepProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Transmog Provider: PID=22184 TID=21716 Current image session is [ONLINE] - CTransmogManager::GetMode
2023-07-03 11:04:50, Info DISM DISM Transmog Provider: PID=22184 TID=21716 Audit Mode: [No] - CTransmogManager::Initialize
2023-07-03 11:04:50, Info DISM DISM Transmog Provider: PID=22184 TID=21716 GetProductType: ProductType = [ServerNT] - CTransmogManager::GetProductType
2023-07-03 11:04:50, Info DISM DISM Transmog Provider: PID=22184 TID=21716 Product Type: [ServerNT] - CTransmogManager::Initialize
2023-07-03 11:04:50, Info DISM DISM Transmog Provider: PID=22184 TID=21716 Product Type ServerNT : [Yes] - CTransmogManager::Initialize
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Connecting to the provider located at C:\Users\ADMINI~1.STP\AppData\Local\Temp\EF5B444A-079D-4C72-91C7-34216362472A\SetupPlatformProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM Provider Store: PID=22184 TID=21716 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2023-07-03 11:04:50, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: IBSManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: AppxManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: ProvManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: ProvManager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: AssocManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericManager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: SysprepManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: SysprepManager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2023-07-03 11:04:50, Info DISM DISM.EXE: Attempting to add the commands from provider: SetupPlatformManager
2023-07-03 11:04:50, Info DISM DISM.EXE: Succesfully registered commands for the provider: SetupPlatformManager.
2023-07-03 11:04:50, Info DISM DISM Package Manager: PID=22184 TID=27600 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2023-07-03 11:04:50, Info DISM DISM Package Manager: PID=22184 TID=27600 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2023-07-03 11:04:50, Info DISM DISM Package Manager: PID=22184 TID=27600 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2023-07-03 11:04:50, Info DISM DISM Package Manager: PID=22184 TID=27600 CBS session options=0x100! - CDISMPackageManager::Internal_Finalize

 

 

2 Replies

  • Hi PCS-Sydney,

    Can you reboot the server and retry the command? Possibly, you will have to reboot a couple of times until DISM finishes.
    Can you run successfully: DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH?

    • PCS-Sydney's avatar
      PCS-Sydney
      Copper Contributor
      Since posting this, we've done some more digging, and found we could get DISM running - to a point, where it would crash with a specific error.

      Despite reboots etc, this did not allow further progress.

      Given the complexities, this was given over to Microsoft Professional Services for investigation under a support ticket.

      This appears to relate to missing files from an update, and we're working with them to rectify this.

      Many thanks for the reply and suggestion on this case!

Resources