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

T

TonyV

Member
Joined
May 7, 2020
Posts
5
Hi there,

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

Running automatic 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 completes with no errors.




2020-05-08 01:24:07, Info DISM PID=1956 TID=1180 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::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::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_GetProvider(hr: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_GetProvider(hr: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_LoadProvider(hr: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_GetProvider(hr:0x800700c1)
2020-05-08 01:24:08, Error DISM DISM Provider Store: PID=1772 TID=488 Failed to get the OSServices provider - CDISMProviderStore::Final_OnConnect(hr: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::InitializePointers(hr:0x800700c1)
2020-05-08 01:24:08, Warning DISM DISM Manager: PID=1956 TID=1180 A problem ocurred loading the image session. Retrying... - CDISMManager::CreateImageSession(hr: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_LoadProvider(hr: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_GetProvider(hr:0x800700c1)
2020-05-08 01:24:08, Error DISM DISM Provider Store: PID=1948 TID=188 Failed to get the OSServices provider - CDISMProviderStore::Final_OnConnect(hr: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::InitializePointers(hr: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::CreateImageSession(hr: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
 
Hi!

Since you are BSOD-ing, let's test the HDD first:

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:


  • Download the portable version of GSmartControl and save it on your Desktop;
  • Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
  • Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
  • You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
  • Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
  • Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
  • Please note: If the SMART Status reads: Unsupported, stop and let me know.
    info_failing.png
 
Hi,

System drive is an CX2-8B256-Q11 SSD which doesn't support smart.
I've run both a chkdsk and an extended hardware diagnostics from the Alienware bios on the drive with no errors.

Output from smartctl below. Doesn't seem to be a hard disk issue.
I've tried a couple of hard drive test utilities but neither worked in the WinRE boot environment.

Cheers

Tony.

smartctl 6.6 2017-11-05 r4594 [x86_64-w64-mingw32-w10-b18362] (sf-6.6-1)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number: CX2-8B256-Q11 NVMe LITEON 256GB
Serial Number: TW0XVRV7LOH0071400QO
Firmware Version: 48811QD
PCI Vendor ID: 0x14a4
PCI Vendor Subsystem ID: 0x1b4b
IEEE OUI Identifier: 0x002303
Total NVM Capacity: 256,060,514,304 [256 GB]
Unallocated NVM Capacity: 0
Controller ID: 1
Number of Namespaces: 1
Namespace 1 Size/Capacity: 256,060,514,304 [256 GB]
Namespace 1 Utilization: 0
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002303 5610041b30
Local Time is: Sat May 09 10:29:38 2020 PST
Firmware Updates (0x14): 2 Slots, no Reset required
Optional Admin Commands (0x001f): Security Format Frmw_DL NS_Mngmt Self_Test
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Maximum Data Transfer Size: 32 Pages
Warning Comp. Temp. Threshold: 85 Celsius
Critical Comp. Temp. Threshold: 95 Celsius

Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 8.00W - - 0 0 0 0 0 0
1 + 4.00W - - 1 1 1 1 5 5
2 + 2.10W - - 2 2 2 2 5 5
3 - 0.1000W - - 3 3 3 3 5000 5000
4 - 0.0100W - - 4 4 4 4 50000 100000

Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 - 512 0 0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning: 0x00
Temperature: 37 Celsius
Available Spare: 100%
Available Spare Threshold: 50%
Percentage Used: 13%
Data Units Read: 68,942,567 [35.2 TB]
Data Units Written: 45,330,905 [23.2 TB]
Host Read Commands: 855,532,495
Host Write Commands: 671,297,165
Controller Busy Time: 564,551
Power Cycles: 1,082
Power On Hours: 11,509
Unsafe Shutdowns: 104
Media and Data Integrity Errors: 12
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 37 Celsius

Error Information (NVMe Log 0x01, max 64 entries)
No Errors Logged
 
Hi!

SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
Hi,

To be clear , the OS won't boot , so can't get to the desktop.

When I run sfc from a winre disk on the offline boot drive with sfc /scannow /offbootdir=d:\ /offwindir=d:\windows

I get the "Windows Resource Protection could not perform the requested operation" error message.

trustedinstaller service is running

Rgds

Tony.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top