Windows 10: Win 10 1903 Stuck in Critical Process died loop - DISM fails with error 193

Discus and support Win 10 1903 Stuck in Critical Process died loop - DISM fails with error 193 in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi there, Following a power cut yesterday my build 1903 win10 machine has been stuck in a Critical process died reboot loop. Running automatice... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by TazmanTony69, May 7, 2020.

  1. TAZMANTONY69
    TazmanTony69 Win User

    Win 10 1903 Stuck in Critical Process died loop - DISM fails with error 193


    Hi there,


    Following a power cut yesterday my build 1903 win10 machine has been stuck in a Critical process died reboot loop.


    Running automatice recovery from a winpe usb fails , so moved onto the manual recommend steps.


    Created a WinRE USB from another machine , trying to repair using dsim with an install.esd from the ISO and stuck getting an error 193.

    I've attached the dism.log from the WinPE environment below. Any tips /help gratefully received.

    DISM.EXE: Unable to start the servicing process for the image at 'd:\'. HRESULT=800700C1


    Final version of the dism command below, but lots of flavours tried, without scratchdir/windir/sysdrive all with the same error.


    dism /image:d:\ /windir:windows /sysdrivedir:d: /restorehealth /limitaccess /source:ESD:f:\install.esd:6 /scratchdir:c:\


    The windows image is on the D: drive , the install.esd was set as a source from the F: drive on another USB.


    SFC /scannow also fails with a "windows resource protection could not start the repair service" . I've checked the the trustedmodule service is started in the WinPE env as suggested by many.





    2020-05-08 01:24:07, Info DISM PID=1956 TID=1180 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager:Win 10 1903 Stuck in Critical Process died loop - DISM fails with error 193 :put_ScratchDir

    2020-05-08 01:24:07, Info DISM PID=1956 TID=1180 DismCore.dll version: 10.0.18362.1 - CDISMManager::FinalConstruct

    2020-05-08 01:24:07, Info DISM PID=1956 TID=1180 Scratch directory set to 'c:\'. - CDISMManager:Win 10 1903 Stuck in Critical Process died loop - DISM fails with error 193 :put_ScratchDir

    2020-05-08 01:24:07, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

    2020-05-08 01:24:07, Info DISM PID=1956 TID=1180 Successfully loaded the ImageSession at "X:\windows\system32\Dism" - CDISMManager::LoadLocalImageSession

    2020-05-08 01:24:07, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

    2020-05-08 01:24:07, Info DISM DISM Provider Store: PID=1956 TID=1180 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

    2020-05-08 01:24:07, Info DISM DISM Provider Store: PID=1956 TID=1180 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2020-05-08 01:24:07, Info DISM DISM Provider Store: PID=1956 TID=1180 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

    2020-05-08 01:24:07, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

    2020-05-08 01:24:07, Info DISM DISM Manager: PID=1956 TID=1180 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession

    2020-05-08 01:24:07, Info DISM DISM.EXE:

    2020-05-08 01:24:07, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->

    2020-05-08 01:24:07, Info DISM DISM.EXE:

    2020-05-08 01:24:07, Info DISM DISM.EXE: Host machine information: OS Version=10.0.18362, Running architecture=amd64, Number of processors=4

    2020-05-08 01:24:07, Info DISM DISM.EXE: Dism.exe version: 10.0.18362.1

    2020-05-08 01:24:07, Info DISM DISM.EXE: Executing command line: dism /image:d:\ /windir:windows /sysdrivedir:d: /restorehealth /limitaccess /source:ESD:f:\install.esd:6 /scratchdir:c:\

    2020-05-08 01:24:07, Info DISM DISM Provider Store: PID=1956 TID=1180 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection

    2020-05-08 01:24:07, Info DISM DISM Provider Store: PID=1956 TID=1180 Connecting to the provider located at X:\windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2020-05-08 01:24:07, Warning DISM DISM Provider Store: PID=1956 TID=1180 Failed to load the provider: X:\windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProviderhr:0x8007007e

    2020-05-08 01:24:07, Info DISM DISM Provider Store: PID=1956 TID=1180 Connecting to the provider located at X:\windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2020-05-08 01:24:07, Info DISM DISM Provider Store: PID=1956 TID=1180 Connecting to the provider located at X:\windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2020-05-08 01:24:07, Info DISM DISM Provider Store: PID=1956 TID=1180 Connecting to the provider located at X:\windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2020-05-08 01:24:07, Info DISM DISM Provider Store: PID=1956 TID=1180 Connecting to the provider located at X:\windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2020-05-08 01:24:07, Warning DISM DISM Provider Store: PID=1956 TID=1180 Failed to load the provider: X:\windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProviderhr:0x8007007e

    2020-05-08 01:24:07, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

    2020-05-08 01:24:07, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

    2020-05-08 01:24:07, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager

    2020-05-08 01:24:07, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager

    2020-05-08 01:24:07, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager.

    2020-05-08 01:24:07, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager

    2020-05-08 01:24:07, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.

    2020-05-08 01:24:07, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager

    2020-05-08 01:24:07, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager

    2020-05-08 01:24:07, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.

    2020-05-08 01:24:07, Info DISM DISM Provider Store: PID=1956 TID=1180 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection

    2020-05-08 01:24:07, Info DISM DISM FFU Provider: PID=1956 TID=1180 [d:\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize

    [1956] [0x8007007b] FIOReadFileIntoBuffer:1381: The filename, directory name, or volume label syntax is incorrect.

    [1956] [0xc142011c] UnmarshallImageHandleFromDirectory:641

    [1956] [0xc142011c] WIMGetMountedImageHandle:2897

    2020-05-08 01:24:07, Info DISM DISM WIM Provider: PID=1956 TID=1180 [d:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize

    2020-05-08 01:24:07, Info DISM DISM VHD Provider: PID=1956 TID=1180 [d:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

    2020-05-08 01:24:07, Info DISM DISM FFU Provider: PID=1956 TID=1180 [d:\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize

    2020-05-08 01:24:07, Info DISM DISM Imaging Provider: PID=1956 TID=1180 The provider FfuManager does not support CreateDismImage on d:\ - CGenericImagingManager::CreateDismImage

    2020-05-08 01:24:07, Info DISM DISM VHD Provider: PID=1956 TID=1180 [d:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

    2020-05-08 01:24:07, Info DISM DISM Imaging Provider: PID=1956 TID=1180 The provider VHDManager does not support CreateDismImage on d:\ - CGenericImagingManager::CreateDismImage

    [1956] [0x8007007b] FIOReadFileIntoBuffer:1381: The filename, directory name, or volume label syntax is incorrect.

    [1956] [0xc142011c] UnmarshallImageHandleFromDirectory:641

    [1956] [0xc142011c] WIMGetMountedImageHandle:2897

    2020-05-08 01:24:07, Info DISM DISM WIM Provider: PID=1956 TID=1180 [d:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize

    2020-05-08 01:24:07, Info DISM DISM Imaging Provider: PID=1956 TID=1180 The provider WimManager does not support CreateDismImage on d:\ - CGenericImagingManager::CreateDismImage

    2020-05-08 01:24:07, Info DISM DISM Imaging Provider: PID=1956 TID=1180 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage

    2020-05-08 01:24:07, Info DISM DISM Manager: PID=1956 TID=1180 physical location path: d:\ - CDISMManager::CreateImageSession

    2020-05-08 01:24:07, Info DISM DISM Manager: PID=1956 TID=1180 Event name for current DISM session is Global\__?_Volume{c498c208-ef67-4ece-ac29-2cc4ec4f931d}__3131096205_1376256_535079 - CDISMManager::CheckSessionAndLock

    2020-05-08 01:24:07, Info DISM DISM Manager: PID=1956 TID=1180 Create session event 0x240 for current DISM session and event name is Global\__?_Volume{c498c208-ef67-4ece-ac29-2cc4ec4f931d}__3131096205_1376256_535079 - CDISMManager::CheckSessionAndLock

    2020-05-08 01:24:07, Info DISM DISM Manager: PID=1956 TID=1180 Copying DISM from "d:\windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation

    2020-05-08 01:24:08, Info DISM DISM Manager: PID=1956 TID=1180 Successfully loaded the ImageSession at "c:\2A7D15CA-D701-4712-9C1B-669389322254" - CDISMManager::LoadRemoteImageSession

    2020-05-08 01:24:08, Info DISM DISM Image Session: PID=1772 TID=488 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1772 TID=488 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect

    2020-05-08 01:24:08, Warning DISM DISM Provider Store: PID=1772 TID=488 There is a possible 32-bit versus 64-bit cross architecture issue with the provider or one of its dependencies. - CDISMProviderStore::Internal_LoadProviderhr:0x800700c1

    2020-05-08 01:24:08, Warning DISM DISM Provider Store: PID=1772 TID=488 Failed to load the provider: c:\2A7D15CA-D701-4712-9C1B-669389322254\OSProvider.dll. - CDISMProviderStore::Internal_GetProviderhr:0x800700c1

    2020-05-08 01:24:08, Error DISM DISM Provider Store: PID=1772 TID=488 Failed to get the OSServices provider - CDISMProviderStore::Final_OnConnecthr:0x800700c1

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1772 TID=488 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1772 TID=488 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1772 TID=488 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1772 TID=488 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1772 TID=488 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    2020-05-08 01:24:08, Error DISM DISM Proxy Image Session: PID=1956 TID=1180 Failed to get the provider store from the image session object. - CProxyImageSession::InitializePointershr:0x800700c1

    2020-05-08 01:24:08, Warning DISM DISM Manager: PID=1956 TID=1180 A problem ocurred loading the image session. Retrying... - CDISMManager::CreateImageSessionhr:0x800700c1

    2020-05-08 01:24:08, Info DISM DISM Manager: PID=1956 TID=1180 Copying DISM from "d:\windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation

    2020-05-08 01:24:08, Info DISM DISM Manager: PID=1956 TID=1180 Successfully loaded the ImageSession at "c:\D98AFBEC-E989-4058-B1C2-98580E86D258" - CDISMManager::LoadRemoteImageSession

    2020-05-08 01:24:08, Info DISM DISM Image Session: PID=1948 TID=188 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1948 TID=188 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect

    2020-05-08 01:24:08, Warning DISM DISM Provider Store: PID=1948 TID=188 There is a possible 32-bit versus 64-bit cross architecture issue with the provider or one of its dependencies. - CDISMProviderStore::Internal_LoadProviderhr:0x800700c1

    2020-05-08 01:24:08, Warning DISM DISM Provider Store: PID=1948 TID=188 Failed to load the provider: c:\D98AFBEC-E989-4058-B1C2-98580E86D258\OSProvider.dll. - CDISMProviderStore::Internal_GetProviderhr:0x800700c1

    2020-05-08 01:24:08, Error DISM DISM Provider Store: PID=1948 TID=188 Failed to get the OSServices provider - CDISMProviderStore::Final_OnConnecthr:0x800700c1

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1948 TID=188 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1948 TID=188 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1948 TID=188 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1948 TID=188 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1948 TID=188 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    2020-05-08 01:24:08, Error DISM DISM Proxy Image Session: PID=1956 TID=1180 Failed to get the provider store from the image session object. - CProxyImageSession::InitializePointershr:0x800700c1

    2020-05-08 01:24:08, Error DISM DISM Manager: PID=1956 TID=1180 Failed to load the image session from the temporary location: c:\D98AFBEC-E989-4058-B1C2-98580E86D258 - CDISMManager::CreateImageSessionhr:0x800700c1

    2020-05-08 01:24:08, Error DISM DISM.EXE: Could not load the image session. HRESULT=800700C1

    2020-05-08 01:24:08, Error DISM DISM.EXE: Unable to start the servicing process for the image at 'd:\'. HRESULT=800700C1

    2020-05-08 01:24:08, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

    2020-05-08 01:24:08, Info DISM DISM.EXE:

    2020-05-08 01:24:08, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->

    2020-05-08 01:24:08, Info DISM DISM.EXE:

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1956 TID=1180 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1956 TID=1180 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1956 TID=1180 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1956 TID=1180 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1956 TID=1180 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1956 TID=1180 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider

    2020-05-08 01:24:08, Info DISM DISM Provider Store: PID=1956 TID=1180 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    :)
     
    TazmanTony69, May 7, 2020
    #1
  2. LOUIS12349
    Louis12349 Win User

    Critical process died BSoD loop

    My alienware 17 R3 laptop apparently forced restart to update windows 10 earlier in the day and after the update finished it literally won't start up and is now stuck in Critical process died BSoD loop without me being able to enter safe mode.

    Any attempt to entering safe mode results in another Critical process died blue screen and I've tried EVERYTHING that the net lists as a solution.

    Tried going back to previous version of windows and it list an error, tried restoring from a previous point and it doesn't show up at all. Hell I tried a complete reset of the laptop and it gave me an error and said it cannot complete the process for god
    knows what reason.

    This happened once on my older alienware 17 r3 and I had to get a replacement entirely due to the vendors not being able to decipher the root cause of the problem but one thing is for damn sure, everytime a windows 10 update happens my laptop potentially
    gets killed off...

    Seriously, any suggestions? This is pretty frigging infuriating.

    Moved from: Windows / Windows 10 / Windows update, recovery, & backup
     
    Louis12349, May 7, 2020
    #2
  3. LOUIS12349
    Louis12349 Win User
    Critical process died BSoD loop

    My alienware 17 R3 laptop apparently forced restart to update windows 10 earlier in the day and after the update finished it literally won't start up and is now stuck in Critical process died BSoD loop without me being able to enter safe mode.

    Any attempt to entering safe mode results in another Critical process died blue screen and I've tried EVERYTHING that the net lists as a solution.

    Tried going back to previous version of windows and it list an error, tried restoring from a previous point and it doesn't show up at all. Hell I tried a complete reset of the laptop and it gave me an error and said it cannot complete the process for god
    knows what reason.

    This happened once on my older alienware 17 r3 and I had to get a replacement entirely due to the vendors not being able to decipher the root cause of the problem but one thing is for damn sure, everytime a windows 10 update happens my laptop potentially
    gets killed off...

    Seriously, any suggestions? This is pretty frigging infuriating.

    [Moved from: Windows / Windows 10 / Windows update, recovery, & backup]
     
    Louis12349, May 7, 2020
    #3
  4. RICHARDPOWICK
    RichardPowick Win User

    Win 10 1903 Stuck in Critical Process died loop - DISM fails with error 193

    Win 10 Critical process died

    Hi,

    Windows 10 won't boot showing critical process died. Auto repair doesn't work, sfc scannow and Chkdsk find no errors. Dism image cleanup won't run, and system restore also fails.

    Any ideas, I'm at the end of my tether?
     
    RichardPowick, May 7, 2020
    #4
Thema:

Win 10 1903 Stuck in Critical Process died loop - DISM fails with error 193

Loading...

  1. Win 10 1903 Stuck in Critical Process died loop - DISM fails with error 193 - Similar Threads - 1903 Stuck Critical

  2. Stuck in boot loop, critical process died error

    in Windows 10 Gaming
    Stuck in boot loop, critical process died error: For the past few weeks my computer has been stuck unable to boot. The only error message I've gotten is "CRITICAL PROCESS DIED" but I've tried almost every suggested method I can find to no avail. System restore doesn't appear to affect the correct drive, when I try to reset...

  3. Stuck in boot loop, critical process died error

    in Windows 10 BSOD Crashes and Debugging
    Stuck in boot loop, critical process died error: For the past few weeks my computer has been stuck unable to boot. The only error message I've gotten is "CRITICAL PROCESS DIED" but I've tried almost every suggested method I can find to no avail. System restore doesn't appear to affect the correct drive, when I try to reset...

  4. Stuck in boot loop, critical process died error

    in Windows 10 Software and Apps
    Stuck in boot loop, critical process died error: For the past few weeks my computer has been stuck unable to boot. The only error message I've gotten is "CRITICAL PROCESS DIED" but I've tried almost every suggested method I can find to no avail. System restore doesn't appear to affect the correct drive, when I try to reset...

  5. Stuck in BSOD critical process died loop

    in Windows 10 Gaming
    Stuck in BSOD critical process died loop: Hi,I recently built a new desktop computer and have run into a number of bsod issues I have been able to fix... until now!I was gaming and my computer suddenly shut down. As it was rebooting, it ran into a BSOD with the critical_process_died error. The automatic startup...

  6. Stuck in BSOD critical process died loop

    in Windows 10 Software and Apps
    Stuck in BSOD critical process died loop: Hi,I recently built a new desktop computer and have run into a number of bsod issues I have been able to fix... until now!I was gaming and my computer suddenly shut down. As it was rebooting, it ran into a BSOD with the critical_process_died error. The automatic startup...

  7. CRITICAL PROCESS DIED loop

    in Windows 10 Gaming
    CRITICAL PROCESS DIED loop: im posting this on my phone I have tried various solutions, such as reset, sfc, chkdsk, system restore, bootreg, and others but to no avail. Please help me https://answers.microsoft.com/en-us/windows/forum/all/critical-process-died-loop/c2832777-dbd7-4c55-8613-e83cc94de903

  8. CRITICAL PROCESS DIED loop

    in Windows 10 Software and Apps
    CRITICAL PROCESS DIED loop: im posting this on my phone I have tried various solutions, such as reset, sfc, chkdsk, system restore, bootreg, and others but to no avail. Please help me https://answers.microsoft.com/en-us/windows/forum/all/critical-process-died-loop/c2832777-dbd7-4c55-8613-e83cc94de903

  9. CRITICAL PROCESS DIED loop

    in Windows 10 BSOD Crashes and Debugging
    CRITICAL PROCESS DIED loop: im posting this on my phone I have tried various solutions, such as reset, sfc, chkdsk, system restore, bootreg, and others but to no avail. Please help me https://answers.microsoft.com/en-us/windows/forum/all/critical-process-died-loop/c2832777-dbd7-4c55-8613-e83cc94de903

  10. Critical Process died loop

    in Windows 10 Drivers and Hardware
    Critical Process died loop: Hi! I have been experiencing Critical Process Died BSOD loop. I tried going in recovery troubleshoot. I tried system restore but the status says that "You must enable system protection on this drive." I tried fixing this issue with cmd i tried net start vss and...