Win10 BSOD (critical process died) and DISM component store help


  1. banditz09
    Posts : 2
    Win10
       New #1

    Win10 BSOD (critical process died) and DISM component store help


    I'm not sure if this is the best place to ask, but I figured I'd give it a shot, as I have spent DAYS trying to get my drive to boot so I can properly take an image or do a "repair upgrade"



    I recently built a brand new PC because my old motherboard from 2012 took a dump. I thought getting the data from my old Intel 240gb SSD would be no problem, but it has proved to be the most challenging ever. I have SO many hours into this, googling issues, error codes, trying different software, boot disks, recovery USB's, repairs, etc. When I plug the drive into my new system, via SATA to USB or just directly SATA to motherboard, I can see the data on the drive, but I just can't get it to boot. I have tried everything... dism, (component store cannot be repaired), sfc, chkdsk (chkdsk says the drive is 100% healthy, no bad sectors), etc. I have tried taking an image of the drive / windows partition with Macrium and AOMEI backupper and it successfully takes the image, but when I try to restore to my new SSD (1TB NVME) I run into the same boot issues. It is not a UEFI vs Legacy BIOS issue, as my old mobo was UEFI and AHCI as well, not IDE. I've done all of the troubleshooting I could find on the web, googled every error message, messed with diskpart, with bootrec rebuildbcd, bootrec fixboot commands, etc. I suspect maybe some sort of corruption has happened with windows system files, or the registry, OR it has something to do with my new drive being GPT and this old source drive being MBR. I feel I have tried EVERYTHING on my own, and usually tech issues are no problem for me.



    I REALLY don't want to start over, as I have years worth of settings, customizations, programs, app data, user data, etc on the SSD, and I know you can't just simply copy and paste the \Windows or the \Users directory into a new installation of win10 without all hell breaking loose.



    My ultimate goal is to get this drive booting properly so that I can properly image it / clone it to my new NVME SSD in my new machine so that all of my user data, software, customizations, app data, etc are on the new system, as if nothing changed except for much better and faster hardware.



    So here is the closest I've gotten to figuring the issue out before I hit dead ends. I've googled every error code and every log file entry from DISM I find pertinent. I suspect my windows image component store is messed up and/or my registry, but there's GOT to be a way to fix it. I have uploaded the commands and the responses I got, as well as the log files they generated.

    Here is what I get when I do dism /checkhealth



    x:\windows\system32>dism /image:c:\ /cleanup-image /checkhealthDeployment Im - Pastebin.com



    Here is what I get when I attempt sfc with any parameters as well:



    "Windows Resource Protection could not perform the requested operation." (No log file)



    Here is what I get when I try to restore the image with the .esd file windows media creation tool provides:



    x:\windows\system32>dism /image:c:\ /cleanup-image /restorehealth /source:esd:G: - Pastebin.com



    I have triple-checked the commands to make sure my syntax is correct and that all of the paths, drive letters, etc are all correct and the files exist. From here, I'm not really sure what to do or if it's even possible to get dism to play nice and repair the "component store" (which I have no idea what it is)



    Also, I forgot to mention. Everything on my old system appeared to be working fine last week. This all started when I attempted to put my new graphics card (MSI RTX 2060) into the system. This is when all hell broke loose. I have no idea if that is what caused all of this, and if so, HOW....or if it's just a complete coincidence. Previously I had an old ass GTX 560 TI, so quite a bit newer graphics card but I still for the life of me can't figure out how in the world this could cause windows to be messed up to the point of not booting and have it's "component store" corrupted / unrepairable. Alternatively, I suppose it could have been a windows update to mess everything up.



    Am I completely screwed if DISM tells me "the component store cannot be repaired"? There's a LOT of stuff in those log files, stuff that's even way above my head. Maybe if I could fix them, I could get dism to play nice and fix the component store and then hopefully boot back up? I have tried doing all of the windows USB repair / startup repair with no luck. The furthest I've gotten to is getting it to the spinning dots of "attempting repairs" and it just stays stuck that way forever. I feel I'm SO CLOSE to fixing this issue, because all of my files are there, I just need to get it to boot and then moved over to my new system so all of my data and settings and software remain in place.



    Do I have any options? When I let it try to boot on it's own, I always get the BSOD "Critical Process Died."

    Thank you SO MUCH for any help / suggestions. My computer is my livelihood and how I put food on the table, and it's very hard to work and be productive without all of my data / software, etc.
      My Computer
    Quote Quote

  3. Macboatmaster
    Posts : 1,616
    11, 10, 8.1 and 7 all Professional versions, and Linux Mint
       New #2

    You cannot clone or image a OS disk that is MBR = Master Boot Record to a new drive and expect it to boot from the new drive when the firmware of the system is in UEFI mode
    UEFI requires a GPT partitioned drive to boot from, when it is the OS drive as the firmware hands control to the GPT FAT formatted partition for it to then commence loading Windows.

    If your original OS drive itself and its file system is still good, then it MAY boot and load windows on the new motherboard if
    with only the drive from the old motherboard connected - you enter setup - and in the UEFI interface you change the firmware to legacy.

    Then you should see the drive and set that as the boot option.

    You may need to run startup repair
    See this please
    Startup repair
    Run Startup Repair in Windows 10

    and in case you do not know how to get to advanced options
    Boot to Advanced Startup Options in Windows 10.

    Once you have that sorted you then need to image that disk to the new 1TB - but that cannot be done as I think you have tried - as you will encounter the same problem that you cannot clone or image an MBR disc to a GPT disc.
    The clone will wipe the new drive and simply clone it as the MBR disc and the image and restore needs to be done in a special way.
    Restoring an MBR System image to UEFI/GPT - KnowledgeBase v7.2 - Macrium Reflect Knowledgebase
      My Computer
    Quote Quote

  4. banditz09
    Posts : 2
    Win10
    Thread Starter
       New #3

    Hi, thank you for your response.

    I too thought the issue may have been UEFI, but my old motherboard is UEFI as well....and also my old drive won't boot properly on the old system as well, so I know it's not an issue with the new hardware.

    I actually followed the exact instructions in that Macrium article you mentioned....I imaged ONLY the C partition and not the whole drive. Still didn't fix the problem....it's either something happened with my registry, or Windows Update is the culprit, because again, it still won't boot on the old hardware. I wish Windows provided more information about the Windows Image other than.. "the component store cannot be repaired."

    Anyways, somehow, I believe my registry got messed up and if I could just correct those errors, DISM would then run properly and fix the "component store" - here is my srttrail.txt:

    Code:
    Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ?12/?3/?2020 3:42:17 AM (GMT)
Number of repair attempts: 20

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\windows
AutoChk Run = 0
Number of root causes = 0

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 78 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 78 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for installed LCU
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Check for installed driver updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x2
Time taken = 563 ms

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\windows
AutoChk Run = 0
Number of root causes = 0

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 719 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 94 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for installed LCU
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for installed driver updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x2
Time taken = 703 ms

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk1
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 0

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 734 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 78 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 62 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 110 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for installed LCU
Result: Completed successfully. Error code =  0x0
Time taken = 62 ms

Test Performed:
---------------------------
Name: Check for installed driver updates
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x2
Time taken = 1266 ms

---------------------------
---------------------------
    Here is what happens when I try /revertpendingactions

    Code:
    x:\windows\system32>dism /image:c:\ /cleanup-image /revertpendingactions /scratchdir:C:\kennytemp

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.19041.1

Reverting pending actions from the image...

Error: 2

An error occurred reverting the pending actions from the image.
For more information, review the log file.

The DISM log file can be found at X:\windows\Logs\DISM\dism.log



===================================================================

dism.log:


2020-12-12 16:13:59, Info                  DISM   PID=1400 TID=2228 Scratch directory set to 'X:\Users\Default\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2020-12-12 16:13:59, Info                  DISM   PID=1400 TID=2228 DismCore.dll version: 10.0.14393.0 - CDISMManager::FinalConstruct
2020-12-12 16:13:59, Info                  DISM   PID=1400 TID=2228 Scratch directory set to 'C:\kennytemp'. - CDISMManager::put_ScratchDir
2020-12-12 16:13:59, Info                  DISM   Try to initialize Panther logging 1 times, last error: 0x0
2020-12-12 16:13:59, Info                  DISM   PID=1400 TID=2228 Successfully loaded the ImageSession at "X:\windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2020-12-12 16:13:59, Info                  DISM   Try to initialize Panther logging 1 times, last error: 0x0
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   Try to initialize Panther logging 1 times, last error: 0x0
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Manager: PID=1400 TID=2228 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM.EXE:
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2020-12-12 16:13:59, Info                  DISM   DISM.EXE:
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.14393, Running architecture=amd64, Number of processors=24
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.14393.0
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Executing command line: dism  /image:c:\ /cleanup-image /revertpendingactions /scratchdir:C:\kennytemp
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Loading Provider from location X:\windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Connecting to the provider located at X:\windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Loading Provider from location X:\windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Connecting to the provider located at X:\windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Loading Provider from location X:\windows\System32\Dism\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Connecting to the provider located at X:\windows\System32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Loading Provider from location X:\windows\System32\Dism\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Connecting to the provider located at X:\windows\System32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Loading Provider from location X:\windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Connecting to the provider located at X:\windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Loading Provider from location X:\windows\System32\Dism\FfuProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Connecting to the provider located at X:\windows\System32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Loading Provider from location X:\windows\System32\Dism\SiloedPackageProvider.dll - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Warning               DISM   DISM Provider Store: PID=1400 TID=2228 Failed to Load the provider: X:\windows\System32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
[1400] [0x80070002] FIOReadFileIntoBuffer:(1250): The system cannot find the file specified.
[1400] [0xc142011c] UnmarshallImageHandleFromDirectory:(793)
[1400] [0xc142011c] WIMGetMountedImageHandle:(3047)
2020-12-12 16:13:59, Info                  DISM   DISM WIM Provider: PID=1400 TID=2228 [c:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2020-12-12 16:13:59, Info                  DISM   DISM VHD Provider: PID=1400 TID=2228 [c:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Getting Provider VHDManager - CDISMProviderStore::GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM VHD Provider: PID=1400 TID=2228 [c:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2020-12-12 16:13:59, Info                  DISM   DISM Imaging Provider: PID=1400 TID=2228 The provider VHDManager does not support CreateDismImage on c:\ - CGenericImagingManager::CreateDismImage
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Getting Provider WimManager - CDISMProviderStore::GetProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
[1400] [0x80070002] FIOReadFileIntoBuffer:(1250): The system cannot find the file specified.
[1400] [0xc142011c] UnmarshallImageHandleFromDirectory:(793)
[1400] [0xc142011c] WIMGetMountedImageHandle:(3047)
2020-12-12 16:13:59, Info                  DISM   DISM WIM Provider: PID=1400 TID=2228 [c:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2020-12-12 16:13:59, Info                  DISM   DISM Imaging Provider: PID=1400 TID=2228 The provider WimManager does not support CreateDismImage on c:\ - CGenericImagingManager::CreateDismImage
2020-12-12 16:13:59, Info                  DISM   DISM Imaging Provider: PID=1400 TID=2228 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2020-12-12 16:13:59, Info                  DISM   DISM Manager: PID=1400 TID=2228 physical location path: c:\ - CDISMManager::CreateImageSession
2020-12-12 16:13:59, Info                  DISM   DISM Manager: PID=1400 TID=2228 Event name for current DISM session is Global\__?_Volume{619d9c8d-3b4e-11eb-8dd1-88b6b553554a}__3769242318_5767168_621029 - CDISMManager::CheckSessionAndLock
2020-12-12 16:13:59, Info                  DISM   DISM Manager: PID=1400 TID=2228 Create session event 0x1f4 for current DISM session and event name is Global\__?_Volume{619d9c8d-3b4e-11eb-8dd1-88b6b553554a}__3769242318_5767168_621029  - CDISMManager::CheckSessionAndLock
2020-12-12 16:13:59, Info                  DISM   DISM Manager: PID=1400 TID=2228 Copying DISM from "c:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2020-12-12 16:13:59, Info                  DISM   DISM Manager: PID=1400 TID=2228 Successfully loaded the ImageSession at "C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F" - CDISMManager::LoadRemoteImageSession
2020-12-12 16:13:59, Info                  DISM   DISM Image Session: PID=264 TID=1688 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM OS Provider: PID=264 TID=1688 Defaulting SystemPath to c:\ - CDISMOSServiceManager::Final_OnConnect
2020-12-12 16:13:59, Info                  DISM   DISM OS Provider: PID=264 TID=1688 Defaulting Windows folder to c:\Windows - CDISMOSServiceManager::Final_OnConnect
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2020-12-12 16:13:59, Warning               DISM   DISM Provider Store: PID=264 TID=1688 Failed to load the provider: C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2020-12-12 16:13:59, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2020-12-12 16:13:59, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2020-12-12 16:13:59, Info                  DISM   DISM Manager: PID=1400 TID=2228 Image session successfully loaded from the temporary location: C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F - CDISMManager::CreateImageSession
2020-12-12 16:13:59, Info                  DISM   DISM OS Provider: PID=264 TID=1688 Setting SystemPath to c:\ - CDISMOSServiceManager::SetSystemPath
2020-12-12 16:13:59, Warning               DISM   DISM OS Provider: PID=264 TID=1688 Could not find CurrentMajorVersionNumber value; will fall back to binary version. - CDISMOSServiceManager::get_OSVersion
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.19041.610, Image architecture=amd64
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  CSI    00000001 Shim considered [l:125]'\??\c:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2020-12-12 16:13:59, Info                  CSI    00000002 Shim considered [l:122]'\??\c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\wcp.dll' : got STATUS_SUCCESS
2020-12-12 16:13:59, Info                  DISM   DISM OS Provider: PID=264 TID=1688 Determined System directory to be c:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory
2020-12-12 16:13:59, Info                  DISM   DISM Package Manager: PID=264 TID=1688 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2020-12-12 16:13:59, Info                  CSI    00000001 Shim considered [l:125]'\??\c:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2020-12-12 16:13:59, Info                  CSI    00000002 Shim considered [l:122]'\??\c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\wcp.dll' : got STATUS_SUCCESS
2020-12-12 16:13:59, Info                  CSI    00000001 Shim considered [l:125]'\??\c:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2020-12-12 16:13:59, Info                  CSI    00000002 Shim considered [l:122]'\??\c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\wcp.dll' : got STATUS_SUCCESS
2020-12-12 16:13:59, Info                  CBS    Universal Time is: 2020-12-12 21:13:59.599
2020-12-12 16:13:59, Info                  CBS    Failed to find a matching version for servicing stack: c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-12-12 16:13:59, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-12-12 16:13:59, Info                  CBS    Offline servicing, using stack version from: c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\cbscore.dll
2020-12-12 16:13:59, Info                  CBS    Loaded Servicing Stack v10.0.19041.621 with Core: c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\cbscore.dll
2020-12-12 16:13:59, Info                  CBS    Setting core mode: CbsCoreModeOffline
2020-12-12 16:13:59, Info                  CSI    00000001@2020/12/12:21:13:59.599 WcpInitialize: wcp.dll version 10.0.19041.621 (WinBuild.160101.0800)
2020-12-12 16:13:59, Info                  CBS    Lock: New lock added: CCbsSessionManager, level: 11, total lock:9
2020-12-12 16:13:59, Info                  CBS    Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:10
2020-12-12 16:13:59, Info                  DISM   DISM Package Manager: PID=264 TID=1688 Loaded servicing stack for offline use only. - CDISMPackageManager::CreateCbsSession
2020-12-12 16:13:59, Info                  CBS    Lazy store initialization mode
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  CSI    00000001 Shim considered [l:125]'\??\c:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2020-12-12 16:13:59, Info                  CSI    00000002 Shim considered [l:122]'\??\c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.621_none_e7694895260e0b6d\wcp.dll' : got STATUS_SUCCESS
2020-12-12 16:13:59, Warning               DISM   DISM OS Provider: PID=264 TID=1688 Could not find CurrentMajorVersionNumber value; will fall back to binary version. - CDISMOSServiceManager::get_OSVersion
2020-12-12 16:13:59, Error                 DISM   DISM OS Provider: PID=264 TID=1688 "Failed to query the value SystemRoot." - CDISMOSServiceManager::DetermineBootDrive(hr:0x80070002)
2020-12-12 16:13:59, Error                 DISM   DISM Driver Manager: PID=264 TID=1688 Failed to getting the boot drive from the os services provider. - CDriverManager::Initialize(hr:0x80070002)
2020-12-12 16:13:59, Warning               DISM   DISM Provider Store: PID=264 TID=1688 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80070002)
2020-12-12 16:13:59, Warning               DISM   DISM Provider Store: PID=264 TID=1688 Failed to load the provider: C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\DmiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80070002)
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Warning               DISM   DISM Provider Store: PID=264 TID=1688 Failed to load the provider: C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\SysprepProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Transmog Provider: PID=264 TID=1688 Current image session is [OFFLINE] - CTransmogManager::GetMode
2020-12-12 16:13:59, Info                  DISM   DISM Transmog Provider: PID=264 TID=1688 Determined WinDir path = [c:\Windows] - CTransmogManager::GetWinDirPath
2020-12-12 16:13:59, Info                  DISM   DISM Transmog Provider: PID=264 TID=1688 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
2020-12-12 16:13:59, Info                  DISM   DISM Transmog Provider: PID=264 TID=1688 Product Type: [WinNT] - CTransmogManager::Initialize
2020-12-12 16:13:59, Info                  DISM   DISM Transmog Provider: PID=264 TID=1688 Product Type ServerNT : [No] - CTransmogManager::Initialize
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Connecting to the provider located at C:\kennytemp\FDF75DFF-4F74-4CE2-AC5A-343D2600295F\SetupPlatformProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IBSManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: ProvManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: ProvManager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericManager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SysprepManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: SysprepManager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SetupPlatformManager
2020-12-12 16:13:59, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: SetupPlatformManager.
2020-12-12 16:13:59, Info                  DISM   DISM Package Manager: PID=264 TID=1688 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2020-12-12 16:13:59, Info                  DISM   DISM Package Manager: PID=264 TID=1688 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2020-12-12 16:13:59, Info                  DISM   DISM Package Manager: PID=264 TID=1688 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2020-12-12 16:13:59, Info                  DISM   DISM Package Manager: PID=264 TID=1688 CBS session options=0x800! - CDISMPackageManager::Internal_Finalize
2020-12-12 16:13:59, Info                  CBS    Lazy store initialization mode, fully initialize.
2020-12-12 16:13:59, Info                  CBS    Offline image is writable
2020-12-12 16:13:59, Info                  CBS    Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SOFTWARE' from path '\\?\c:\Windows\System32\config\SOFTWARE'.
2020-12-12 16:13:59, Info                  CBS    Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SYSTEM' from path '\\?\c:\Windows\System32\config\SYSTEM'.
2020-12-12 16:13:59, Info                  CBS    Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SECURITY' from path '\\?\c:\Windows\System32\config\SECURITY'.
2020-12-12 16:13:59, Info                  CBS    Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SAM' from path '\\?\c:\Windows\System32\config\SAM'.
2020-12-12 16:13:59, Info                  CBS    Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/COMPONENTS' from path '\\?\c:\Windows\System32\config\COMPONENTS'.
2020-12-12 16:14:00, Info                  CBS    Loading offline registry hive: DRIVERS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DRIVERS' from path '\\?\c:\Windows\System32\config\DRIVERS'.
2020-12-12 16:14:00, Info                  CBS    Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DEFAULT' from path '\\?\c:\Windows\System32\config\DEFAULT'.
2020-12-12 16:14:00, Info                  CBS    Loading offline registry hive: BCD, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/EFI/Microsoft/Boot/BCD' from path '\\?\c:\EFI\Microsoft\Boot\BCD'.
2020-12-12 16:14:00, Info                  CBS    Failed to open the registry root: n/a, key: Microsoft\Windows NT\CurrentVersion\ProfileList. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-12 16:14:00, Info                  CBS    Failed to query for path to user profiles directory. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-12 16:14:00, Info                  CBS    Failed to load the default user profile registry hive. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-12 16:14:00, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SOFTWARE
2020-12-12 16:14:00, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SYSTEM
2020-12-12 16:14:00, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SECURITY
2020-12-12 16:14:00, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SAM
2020-12-12 16:14:00, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/COMPONENTS
2020-12-12 16:14:00, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DRIVERS
2020-12-12 16:14:00, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DEFAULT
2020-12-12 16:14:00, Error                 CBS    Failed to load offline store from boot directory: '\\?\c:\' and windows directory: '\\?\c:\Windows\' [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-12 16:14:00, Error                 CBS    Failed to initialize store parameters with boot drive: c:\, windows directory c:\Windows, and external directory:  [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-12 16:14:00, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/EFI/Microsoft/Boot/BCD
2020-12-12 16:14:00, Error                 CBS    Cannot finalize a session that has not been initialized. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-12 16:14:00, Info                  CBS    Session: 264_35894984 finalized. Reboot required: no [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-12-12 16:14:00, Error                 DISM   DISM Package Manager: PID=264 TID=1688 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070002)
2020-12-12 16:14:00, Error                 DISM   DISM Package Manager: PID=264 TID=1688 An error occured clearing the pending actions from the image. - CDISMPackageManager::RevertPendingActions(hr:0x80070002)
2020-12-12 16:14:00, Error                 DISM   DISM Package Manager: PID=264 TID=1688 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070002)
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Package Manager: PID=264 TID=1688 Finalizing CBS core. - CDISMPackageManager::Finalize
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2020-12-12 16:14:00, Info                  CBS    Execution Engine Finalize
2020-12-12 16:14:00, Info                  CBS    Execution Engine Finalize
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2020-12-12 16:14:00, Info                  CBS    Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2020-12-12 16:14:00, Info                  CBS    Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: GetPublicObjectMonitor::Audit
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: WcpUnload
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: DrupUnload
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: DpxUnload
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: SrUnload
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2020-12-12 16:14:00, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(SysprepManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: SysprepManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Finalizing the servicing provider(SetupPlatformManager) - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: SetupPlatformManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   Offline Registry: PID=264 TID=1688 Hive is not mounted at HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/system32/config/SOFTWARE. - CRegistryMapping::Init
2020-12-12 16:14:00, Info                  DISM   Offline Registry: PID=264 TID=1688 Hive is not mounted at HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/system32/config/SYSTEM. - CRegistryMapping::Init
2020-12-12 16:14:00, Info                  DISM   Offline Registry: PID=264 TID=1688 Hive is not mounted at HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/system32/config/SECURITY. - CRegistryMapping::Init
2020-12-12 16:14:00, Info                  DISM   Offline Registry: PID=264 TID=1688 Hive is not mounted at HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/system32/config/SAM. - CRegistryMapping::Init
2020-12-12 16:14:00, Info                  DISM   Offline Registry: PID=264 TID=1688 Hive is not mounted at HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/system32/config/DEFAULT. - CRegistryMapping::Init
2020-12-12 16:14:00, Info                  DISM   Offline Registry: PID=264 TID=1688 Hive is not mounted at HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Users/Default/NTUSER.DAT. - CRegistryMapping::Init
2020-12-12 16:14:00, Info                  DISM   Offline Registry: PID=264 TID=1688 Hive is not mounted at HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/system32/config/COMPONENTS. - CRegistryMapping::Init
2020-12-12 16:14:00, Info                  DISM   Offline Registry: PID=264 TID=1688 Hive is not mounted at HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/system32/config/DRIVERS. - CRegistryMapping::Init
2020-12-12 16:14:00, Info                  DISM   DISM OS Provider: PID=264 TID=1688 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=264 TID=1688 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Manager: PID=1400 TID=2228 Closing session event handle 0x1f4 - CDISMManager::CloseImageSession
2020-12-12 16:14:00, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2020-12-12 16:14:00, Info                  DISM   DISM.EXE:
2020-12-12 16:14:00, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2020-12-12 16:14:00, Info                  DISM   DISM.EXE:
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2020-12-12 16:14:00, Info                  DISM   DISM Provider Store: PID=1400 TID=2228 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
      My Computer
    Quote Quote

  6. Macboatmaster
    Posts : 1,616
    11, 10, 8.1 and 7 all Professional versions, and Linux Mint
       New #4

    You said
    "OR it has something to do with my new drive being GPT and this old source drive being MBR."
    A motherboard can have UEFI firmware, but if the firmware is set legacy mode and windows installed then it is installed in MBR formatting and will not boot on a UEFI firmware that is NOT set legacy mode

    So the 1000$ question is - IS the original source drive GPT or MBR

    I know you said
    "I REALLY don't want to start over, as I have years worth of settings, customizations, programs, app data, user data, etc on the SSD, and I know you can't just simply copy and paste the \Windows or the \Users directory into a new installation of win10 without all hell breaking loose."

    but the easiest answer is most certainly - to install windows 10 on the new drive, with only that drive connected
    boot from that and update it
    then connect the original drive and move over your personal data etc, and reinstall your apps.


    Re this
    and also my old drive won't boot properly on the old system as well,
    I thought the board had a fault -

    Of course too late now, but the original problem of the crash on the old board could have been dealt with more easily if you had a full image and preferably a backup of data on a separate external drive.

    So in summary - with the drive from the old board and you say a complete new system - the clean install is the FAR BETTER bet - even if the original drive was OK.

    Good luck with it
    Thank you SO MUCH for any help / suggestions. My computer is my livelihood and how I put food on the table, and it's very hard to work and be productive without all of my data / software, etc.
    As I said no help now, but that in bold is very good reason to have not just one complete image and backups but if it was me, I would have two.

    I do not know if it influences you to make the decision - Regback
    https://support.microsoft.com/en-gb/...k-folder-start
      My Computer
    Quote Quote

 

  Related Discussions
Please Help! NOTE: I cannot download or run a log collector, the computer will crashes at startup, even in safe mode! The other day I accidentally clicked a bad link and picked up a nasty .pup chrome extension virus, the kind that redirects...
Ive tried to update drivers, checked the ssd, and even different ram. Don't know what else to do!
Hello. Few weeks ago I started getting bsod on my alienware laptop. Mainly unexpected store exception, sometimes critical process died and dpc watchdog violation. Windows doesnt manage to collect dump file as it stuck on 0 when collecting info so i...
Hello, I have some problems with my PC. After that Creators Update i get some BSODs with 'CRITICAL PROCESS DIED' and sometimes 'UNEXCEPTED STORE EXCEPTION'. The problem is Windows 10 don't create mini-dumps even I selected correctly settings to...
I have been getting frequent (every few hours) BSOD's with Critical Process Died and Unexpected Store Exception. The crashes do not align with any specific task which makes the computer crash. It's crashed during gaming, but then also when just on...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 22:01.
Find Us




Windows 10 Forums