Booting to black screen + blinking caret -- can't repair

Page 1 of 3 123 LastLast

  1. Posts : 14
    Windows 10
       #1

    Booting to black screen + blinking caret -- can't repair


    "Running" Windows 10 (probably Pro, possibly N-edition) on a Macbook air 2012. Installed with Bootcamp Assistant which means a hybrid MBR, and legacy Bios mode for Windows (but not for macOS) on this particular model.

    When booting Windows I just get a black screen with a blinking caret ('_'). It probably happened after a hard powercycle during an update.

    Progression:

    1. Windows booted. No wireless networks listed. Turns out Windows' wireless service wasn't running and refused to start. I did a simple registry edit removing two out of three dependencies for that service. Didn't work, so I reversed my registry edit.
    2. I can't remember if I tried anything else. Anyway, I ended up in a never ending "Repairing Windows..." cycle, maybe because Windows got interrupted during boot by a hard power cycle.
    3. I could access the repair environment GUI but couldn't use any of the repair options. I tried them but they all complained that they were unable to do anything.
    4. After following previous guides here and trying some commands in the recovery console -- the last one being chkdsk /r, which I terminated prematurely since I didn't see the point of doing that on my SSD -- I ended up booting to just a black screen with caret. Sometimes with a little mojibake (unreadable symbols) on the line above. This is where I am now, if we only look at the visual results of booting. I have done more troubleshooting described below...


    I've made a Win 10 Pro 1903 install media on a 8 GB USB drive:

    • None of the automatic repair options work when booting from it (legacy Bios mode USB boot).
    • Sfc scans refuse to work and terminate immediately. No helpful error messages.
    • Can't restore registry backup -- all files in backup directory have size of 0.
    • Most commands can't identify the OS partition -- they say that there are 0 installed OSes.
    • Checkdisk finds no faults with the drive. The drive is a year old Samsung SSD and macOS boots fine from it. The Windows partition can be read fine both from recovery console and from macOS. MacOS NTFS drivers do not complain about the partition or the file system. I am fairly confident the hardware and file system are intact.
    • DISM command complains that the registry is damaged.
    • DISM command complains that the scratch directory size might be insufficient. I don't know what that means exactly. Is the X: RAM drive too small? I don't know...
    • DISM gives error 1009
    • Bootrec runs /fixmbr and /fixboot successfully, but /scanos returns 0 identified Windows installations.


    I feel like I have tried everything I could find in previous threads about the same issue.

    I tried to list everything here, but I'm sure I forgot something, in which case I will edit it in.

    No hardware peripherals except for the 8 GB bootable USB drive.
      My Computer


  2. Posts : 35,468
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #2

    Hi,
    I ended up booting to just a black screen with caret.
    - do you mean a hyphen or underscore? - a caret is ^

    Perhaps your best hope is that your boot priority has somehow changed and your PC is trying to boot from another device. That seems something you've not checked, noting you've been quite thorough.

    However, that's an outside possibility, I'd guess, given the other evidence.

    Indicative of the system not finding a valid bootable medium, of course.

    DISM command complains that the registry is damaged
    - clearly signicant and would argue against trying to recover your Windows partition alone.

    Can't restore registry backup -- all files in backup directory have size of 0.
    I discovered MS disabled this feature around the end of 1709 -> 1803.

    You can find articles about this now, cited on tenforums, where MS argues it saves space. Hmm.

    I assume you haven't yet discovered the value of using disk imaging routinely- so frequently recommended on tenforums- e.g. Macrium Reflect (free/paid). If you had a disk image you could have restored that and be up and running, hopefully.

    I think you're looking at doing a clean install.
    Last edited by dalchina; 21 Sep 2019 at 07:26.
      My Computers


  3. Posts : 14
    Windows 10
    Thread Starter
       #3

    Hello, thanks for the reply.

    dalchina said:

    - do you mean a hyphen? - a caret is ^
    I meant it in the words of Wikipedia "Caret or insertion point, a blinking vertical bar indicating where typed text will be inserted when using a cursor (user interface)", but it's true that is not a vertical bar, but rather an underscore _.

    Perhaps your best hope is that your boot priority has somehow changed and your PC is trying to boot from another device. That seems something you've not checked, noting you've been quite thorough.

    However, that's an outside possibility, I'd guess, given the other evidence.
    Yes, it's not possible since it's a Macbook and I manually choose the windows partition at boot every time by holding the alt-key.



    - clearly signicant and would argue against trying to recover your Windows partition alone.
    I'm assuming that by "Windows partition" you mean my Windows installation. Why shouldn't I try to recover it?


    I discovered MS disabled this feature around the end of 1709 -> 1803.

    You can find articles about this now, cited on tenforums, where MS argues it saves space. Hmm.
    Yeah I heard about that on youtube, but I thought that was about externally stored backups made with Windows backup tools. I guess I've just never thought of backups stored on the same drive as useful...


    I assume you haven't yet discovered the value of using disk imaging routinely- so frequently recommended on tenforums- e.g. Macrium Reflect (free/paid). If you had a disk image you could have restored that and be up and running, hopefully.

    I think you're looking at doing a clean install.
    Had it been my main OS where I store important stuff I would probably have something like that set up. I've always been generous with the idea that OSes are capable of repairing themselves and that I'm up to the task.

    That's too bad, I was hoping to learn something new. I take it there's no sanity checker for the registry that spits out what's wrong with it? Thinking back, the DISM command did probably generate a log file that it helpfully placed on the RAM drive. Perhaps I'll run it again and take a look.
      My Computer


  4. Posts : 35,468
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #4

    Sorry, yes, underscore (noted you showed it in initial post on rereading)

    FWIW:
    DISM command complains that the scratch directory size might be insufficient. I don't know what that means exactly.
    The scratch directory size might be insufficient to perform this operation

    You could try - and this works with a valid Windows partition:
    a. image the partition
    b. clean install Win 10
    c. restore the imaged partition in place of the new Windows partition
    d. reboot
      My Computers


  5. Posts : 14
    Windows 10
    Thread Starter
       #5

    The DISM log:

    Code:
    2019-09-21 13:37:01, Info                  DISM   PID=1456 TID=1460 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
    2019-09-21 13:37:01, Info                  DISM   PID=1456 TID=1460 DismCore.dll version: 10.0.18362.1 - CDISMManager::FinalConstruct
    2019-09-21 13:37:01, Info                  DISM   PID=1456 TID=1460 Scratch directory set to 'C:\scratch'. - CDISMManager::put_ScratchDir
    2019-09-21 13:37:01, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2019-09-21 13:37:01, Info                  DISM   PID=1456 TID=1460 Successfully loaded the ImageSession at "X:\Sources" - CDISMManager::LoadLocalImageSession
    2019-09-21 13:37:01, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2019-09-21 13:37:01, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2019-09-21 13:37:01, Info                  DISM   DISM Manager: PID=1456 TID=1460 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: 
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: 
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.18362, Running architecture=amd64, Number of processors=4
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.18362.1
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Executing command line: DISM  /ScratchDir:C:\scratch /Cleanup-Image /RestoreHealth
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Connecting to the provider located at X:\Sources\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:37:01, Warning               DISM   DISM Provider Store: PID=1456 TID=1460 Failed to load the provider: X:\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2019-09-21 13:37:01, Warning               DISM   DISM Provider Store: PID=1456 TID=1460 Failed to load the provider: X:\Sources\FfuProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Connecting to the provider located at X:\Sources\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Connecting to the provider located at X:\Sources\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Connecting to the provider located at X:\Sources\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:37:01, Warning               DISM   DISM Provider Store: PID=1456 TID=1460 Failed to load the provider: X:\Sources\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2019-09-21 13:37:01, Error                 DISM   DISM.EXE: No providers were found that support the command(cleanup-image). HRESULT=80070057
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: 
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2019-09-21 13:37:01, Info                  DISM   DISM.EXE: 
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:37:01, Info                  DISM   DISM Provider Store: PID=1456 TID=1460 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:16, Info                  DISM   PID=1576 TID=1580 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
    2019-09-21 13:38:16, Info                  DISM   PID=1576 TID=1580 DismCore.dll version: 10.0.18362.1 - CDISMManager::FinalConstruct
    2019-09-21 13:38:16, Info                  DISM   PID=1576 TID=1580 Scratch directory set to 'C:\scratch'. - CDISMManager::put_ScratchDir
    2019-09-21 13:38:16, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2019-09-21 13:38:16, Info                  DISM   PID=1576 TID=1580 Successfully loaded the ImageSession at "X:\Sources" - CDISMManager::LoadLocalImageSession
    2019-09-21 13:38:16, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2019-09-21 13:38:16, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2019-09-21 13:38:16, Info                  DISM   DISM Manager: PID=1576 TID=1580 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: 
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: 
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.18362, Running architecture=amd64, Number of processors=4
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.18362.1
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Executing command line: DISM  /ScratchDir:C:\scratch /Image:C:\ /Cleanup-Image /RestoreHealth
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Connecting to the provider located at X:\Sources\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:16, Warning               DISM   DISM Provider Store: PID=1576 TID=1580 Failed to load the provider: X:\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2019-09-21 13:38:16, Warning               DISM   DISM Provider Store: PID=1576 TID=1580 Failed to load the provider: X:\Sources\FfuProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Connecting to the provider located at X:\Sources\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Connecting to the provider located at X:\Sources\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Connecting to the provider located at X:\Sources\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:16, Warning               DISM   DISM Provider Store: PID=1576 TID=1580 Failed to load the provider: X:\Sources\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2019-09-21 13:38:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    [1576] [0x80070002] FIOReadFileIntoBuffer:(1381): Det går inte att hitta filen.
    [1576] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
    [1576] [0xc142011c] WIMGetMountedImageHandle:(2897)
    2019-09-21 13:38:16, Info                  DISM   DISM WIM Provider: PID=1576 TID=1580 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
    2019-09-21 13:38:16, Info                  DISM   DISM VHD Provider: PID=1576 TID=1580 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
    2019-09-21 13:38:16, Warning               DISM   DISM Provider Store: PID=1576 TID=1580 Failed to retrieve the Provider Instance. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)
    2019-09-21 13:38:16, Info                  DISM   DISM VHD Provider: PID=1576 TID=1580 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
    2019-09-21 13:38:16, Info                  DISM   DISM Imaging Provider: PID=1576 TID=1580 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
    [1576] [0x80070002] FIOReadFileIntoBuffer:(1381): Det går inte att hitta filen.
    [1576] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
    [1576] [0xc142011c] WIMGetMountedImageHandle:(2897)
    2019-09-21 13:38:16, Info                  DISM   DISM WIM Provider: PID=1576 TID=1580 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
    2019-09-21 13:38:16, Info                  DISM   DISM Imaging Provider: PID=1576 TID=1580 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
    2019-09-21 13:38:16, Info                  DISM   DISM Imaging Provider: PID=1576 TID=1580 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
    2019-09-21 13:38:16, Info                  DISM   DISM Manager: PID=1576 TID=1580 physical location path: C:\ - CDISMManager::CreateImageSession
    2019-09-21 13:38:16, Info                  DISM   DISM Manager: PID=1576 TID=1580 Event name for current DISM session is Global\__?_Volume{d8141751-0000-0000-0000-b02057000000}__473294888_65536_44296 - CDISMManager::CheckSessionAndLock
    2019-09-21 13:38:16, Info                  DISM   DISM Manager: PID=1576 TID=1580 Create session event 0x23c for current DISM session and event name is Global\__?_Volume{d8141751-0000-0000-0000-b02057000000}__473294888_65536_44296  - CDISMManager::CheckSessionAndLock
    2019-09-21 13:38:16, Info                  DISM   DISM Manager: PID=1576 TID=1580 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2019-09-21 13:38:16, Info                  DISM   DISM Manager: PID=1576 TID=1580 Successfully loaded the ImageSession at "C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE" - CDISMManager::LoadRemoteImageSession
    2019-09-21 13:38:16, Info                  DISM   DISM Image Session: PID=1608 TID=1632 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:16, Info                  DISM   DISM OS Provider: PID=1608 TID=1632 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
    2019-09-21 13:38:16, Info                  DISM   DISM OS Provider: PID=1608 TID=1632 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
    2019-09-21 13:38:16, Info                  DISM   DISM OS Provider: PID=1608 TID=1632 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath
    2019-09-21 13:38:16, Warning               DISM   DISM OS Provider: PID=1608 TID=1632 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:16, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2019-09-21 13:38:16, Warning               DISM   DISM Provider Store: PID=1608 TID=1632 Failed to load the provider: C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2019-09-21 13:38:16, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2019-09-21 13:38:16, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2019-09-21 13:38:16, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2019-09-21 13:38:16, Info                  DISM   DISM Manager: PID=1576 TID=1580 Image session successfully loaded from the temporary location: C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE - CDISMManager::CreateImageSession
    2019-09-21 13:38:16, Info                  DISM   DISM OS Provider: PID=1608 TID=1632 Setting SystemPath to C:\ - CDISMOSServiceManager::SetSystemPath
    2019-09-21 13:38:17, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.17134.829, Image architecture=amd64
    2019-09-21 13:38:17, Info                  DISM   DISM.EXE: Image session version: 10.0.17134.1
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:17, Info                  CSI    00000001 Shim considered [l:125]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
    2019-09-21 13:38:17, Info                  CSI    00000002 Shim considered [l:122]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\wcp.dll' : got STATUS_SUCCESS
    2019-09-21 13:38:17, Info                  DISM   DISM Package Manager: PID=1608 TID=1632 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
    2019-09-21 13:38:17, Info                  CSI    00000001 Shim considered [l:125]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
    2019-09-21 13:38:17, Info                  CSI    00000002 Shim considered [l:122]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\wcp.dll' : got STATUS_SUCCESS
    2019-09-21 13:38:17, Info                  CSI    00000001 Shim considered [l:125]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
    2019-09-21 13:38:17, Info                  CSI    00000002 Shim considered [l:122]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\wcp.dll' : got STATUS_SUCCESS
    2019-09-21 13:38:17, Info                  CBS    Universal Time is: 2019-09-21 12:38:17.546
    2019-09-21 13:38:17, Info                  CBS    Failed to find a matching version for servicing stack: C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2019-09-21 13:38:17, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2019-09-21 13:38:17, Info                  CBS    Offline servicing, using stack version from: C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\cbscore.dll
    2019-09-21 13:38:17, Info                  CBS    Loaded Servicing Stack v10.0.17134.580 with Core: C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\cbscore.dll
    2019-09-21 13:38:17, Info                  CBS    Setting core mode: CbsCoreModeOffline
    2019-09-21 13:38:17, Info                  CSI    [email protected]/9/21:12:38:17.577 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffc66d7c2b9 @0x7ffc67182a06 @0x7ffc6719deff @0x7ffc67555272 @0x7ffc675554c2 @0x7ffc67510cff)
    2019-09-21 13:38:17, Info                  CBS    Lock: New lock added: CCbsSessionManager, level: 11, total lock:8
    2019-09-21 13:38:17, Info                  CBS    Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:9
    2019-09-21 13:38:17, Info                  DISM   DISM Package Manager: PID=1608 TID=1632 Loaded servicing stack for offline use only. - CDISMPackageManager::CreateCbsSession
    2019-09-21 13:38:17, Info                  CBS    Lazy store initialization mode
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:17, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:17, Info                  CSI    00000001 Shim considered [l:125]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
    2019-09-21 13:38:17, Info                  CSI    00000002 Shim considered [l:122]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.881_none_eada7c8e1d8131a8\wcp.dll' : got STATUS_SUCCESS
    2019-09-21 13:38:18, Info                  DISM   DISM Driver Manager: PID=1608 TID=1632 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
    2019-09-21 13:38:18, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:18, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:18, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:18, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:18, Warning               DISM   DISM Provider Store: PID=1608 TID=1632 Failed to load the provider: C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2019-09-21 13:38:18, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:18, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Error                 DISM   Offline Registry: PID=1608 TID=1632 "Error creating registry mapping: SYSTEM" - COfflineRegistry::GetMountedPath(hr:0x800703f1)
    2019-09-21 13:38:19, Error                 DISM   DISM Appx Provider: PID=1608 TID=1632 Failed to get System key path. - CAppxManager::InitializeResources(hr:0x800703f1)
    2019-09-21 13:38:19, Error                 DISM   DISM Appx Provider: PID=1608 TID=1632 Failed to initialize members. - CAppxManager::Initialize(hr:0x800703f1)
    2019-09-21 13:38:19, Warning               DISM   DISM Provider Store: PID=1608 TID=1632 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x800703f1)
    2019-09-21 13:38:19, Warning               DISM   DISM Provider Store: PID=1608 TID=1632 Failed to load the provider: C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\AppxProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x800703f1)
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\SysprepProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Transmog Provider: PID=1608 TID=1632 Current image session is [OFFLINE] - CTransmogManager::GetMode
    2019-09-21 13:38:19, Info                  DISM   DISM Transmog Provider: PID=1608 TID=1632 Determined WinDir path = [C:\Windows] - CTransmogManager::GetWinDirPath
    2019-09-21 13:38:19, Error                 DISM   DISM Transmog Provider: PID=1608 TID=1632 GetProductType: Error [0x80004005] retrieving current ProductType value. - CTransmogManager::GetProductType
    2019-09-21 13:38:19, Warning               DISM   DISM Provider Store: PID=1608 TID=1632 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004005)
    2019-09-21 13:38:19, Warning               DISM   DISM Provider Store: PID=1608 TID=1632 Failed to load the provider: C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Connecting to the provider located at C:\scratch\F99DA4F2-B469-4809-A622-BCFFD2B3B5BE\SetupPlatformProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IBSManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: ProvManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: ProvManager.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericManager.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SysprepManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: SysprepManager.
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SetupPlatformManager
    2019-09-21 13:38:19, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: SetupPlatformManager.
    2019-09-21 13:38:19, Info                  DISM   DISM Package Manager: PID=1608 TID=1632 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
    2019-09-21 13:38:19, Info                  DISM   DISM Package Manager: PID=1608 TID=1632 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
    2019-09-21 13:38:19, Info                  DISM   DISM Package Manager: PID=1608 TID=1632 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    2019-09-21 13:38:19, Info                  DISM   DISM Package Manager: PID=1608 TID=1632 CBS session options=0x40000! - CDISMPackageManager::Internal_Finalize
    2019-09-21 13:38:19, Info                  CBS    Lazy store initialization mode, fully initialize.
    2019-09-21 13:38:19, Info                  CBS    Offline image is writable
    2019-09-21 13:38:19, 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'.
    2019-09-21 13:38:20, 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'.
    2019-09-21 13:38:20, Info                  CBS    Failed to load offline \\?\C:\Windows\System32\config\SYSTEM hive from '\\?\C:\Windows\System32\config\SYSTEM' into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SYSTEM'. [HRESULT = 0x800703f1 - ERROR_BADDB]
    2019-09-21 13:38:20, Info                  CBS    Failed to load offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SYSTEM [HRESULT = 0x800703f1 - ERROR_BADDB]
    2019-09-21 13:38:20, Info                  CBS    Failed to load offline SYSTEM hive. [HRESULT = 0x800703f1 - ERROR_BADDB]
    2019-09-21 13:38:20, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SOFTWARE
    2019-09-21 13:38:20, Error                 CBS    Failed to load offline store from boot directory: '\\?\C:\' and windows directory: '\\?\C:\Windows\' [HRESULT = 0x800703f1 - ERROR_BADDB]
    2019-09-21 13:38:20, Error                 CBS    Failed to initialize store parameters with boot drive: C:\, windows directory C:\Windows, and external directory:  [HRESULT = 0x800703f1 - ERROR_BADDB]
    2019-09-21 13:38:20, Error                 CBS    Cannot finalize a session that has not been initialized. [HRESULT = 0x800703f1 - ERROR_BADDB]
    2019-09-21 13:38:20, Info                  CBS    Session: 1608_364218 finalized. Reboot required: no [HRESULT = 0x800703f1 - ERROR_BADDB]
    2019-09-21 13:38:20, Error                 DISM   DISM Package Manager: PID=1608 TID=1632 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800703f1)
    2019-09-21 13:38:20, Error                 DISM   DISM Package Manager: PID=1608 TID=1632 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800703f1)
    2019-09-21 13:38:20, Error                 DISM   DISM Package Manager: PID=1608 TID=1632 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800703f1)
    2019-09-21 13:38:20, Error                 DISM   DISM Package Manager: PID=1608 TID=1632 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800703f1)
    2019-09-21 13:38:20, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800703F1
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Package Manager: PID=1608 TID=1632 Finalizing CBS core. - CDISMPackageManager::Finalize
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
    2019-09-21 13:38:20, Info                  CBS    Execution Engine Finalize
    2019-09-21 13:38:20, Info                  CBS    Execution Engine Finalize
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: GetPublicObjectMonitor::Audit
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: WcpUnload
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: DrupUnload
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: DpxUnload
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: SrUnload
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: AppContainerUnload
    2019-09-21 13:38:20, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(SysprepManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: SysprepManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Finalizing the servicing provider(SetupPlatformManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: SetupPlatformManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:20, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:21, Error                 DISM   Offline Registry: PID=1608 TID=1632 "Error creating registry mapping: SYSTEM" - COfflineRegistry::GetMountedPath(hr:0x800703f1)
    2019-09-21 13:38:21, Error                 DISM   DISM OS Provider: PID=1608 TID=1632 Failed to get the mounted hive path from the registry object. - CDISMOSServiceManager::UnloadHiveReportErrors(hr:0x800703f1)
    2019-09-21 13:38:21, Error                 DISM   DISM Provider Store: PID=1608 TID=1632 Failed to disconnect OSServices - CDISMProviderStore::Internal_DisconnectProvider(hr:0x800703f1)
    2019-09-21 13:38:21, Error                 DISM   DISM Provider Store: PID=1608 TID=1632 Failed while trying to disconnect the OSServices Provider! - CDISMProviderStore::Final_OnDisconnect(hr:0x800703f1)
    2019-09-21 13:38:21, Info                  DISM   DISM Provider Store: PID=1608 TID=1632 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:21, Error                 DISM   Offline Registry: PID=1608 TID=1632 "Error creating registry mapping: SYSTEM" - COfflineRegistry::GetMountedPath(hr:0x800703f1)
    2019-09-21 13:38:21, Error                 DISM   Failure occurred during the shutdown of the Provider Store.
    2019-09-21 13:38:21, Error                 DISM   DISM Manager: PID=1576 TID=1580 Failure occurred during shutdown of the Image Session. - CDISMManager::CloseImageSession(hr:0x800703f1)
    2019-09-21 13:38:21, Info                  DISM   DISM Manager: PID=1576 TID=1580 Closing session event handle 0x23c - CDISMManager::CleanupImageSessionEntry
    2019-09-21 13:38:21, Error                 DISM   DISM.EXE:  - CDismWrapper::CloseSession(hr:0x800703f1)
    2019-09-21 13:38:21, Info                  DISM   DISM.EXE: 
    2019-09-21 13:38:21, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2019-09-21 13:38:21, Info                  DISM   DISM.EXE: 
    2019-09-21 13:38:21, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2019-09-21 13:38:21, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:21, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:21, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:21, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-09-21 13:38:21, Info                  DISM   DISM Provider Store: PID=1576 TID=1580 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    - - - Updated - - -


    dalchina said:
    You could try - and this works with a valid Windows partition:
    a. image the partition
    b. clean install Win 10
    c. restore the imaged partition in place of the new Windows partition
    d. reboot
    I'm not sure what kind of image you're suggesting. A full partition image would of course just overwrite a clean install.

    If you're talking about a more restrictive image, like a system image, then I'm not sure from where I would perform the imaging. The recovery console? If that's what you meant then I'll research it.

    Would restoring from that image not restore the broken registry as well? As you can see I haven't had any experience with system images, so I'm not sure what's included or how fine-grained the restore process is.

    Thanks for the suggestions.
    Last edited by ntahoeusntahoeu; 21 Sep 2019 at 10:13.
      My Computer


  6. Posts : 35,468
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #6

    Hi, exactly, if the registry IS damaged, you're facing a clean install.

    Hence my caveat 'this works with a valid Windows partition'. It won't if the registry is damaged.

    If you were getting a DISM indication about the registry that was, for whatever reason, incorrect, you would be in luck. Depends whether you feel an experiment is worthwhile.

    More detail:
    a. Create Macrium reflect boot medium
    b. Boot PC using that.
    c. Create a 'disk image' of just the Windows partition (yes, the nomenclature is mixed) - saved to external disk.
    d. Clean install Windows on the original disk or anothe rdisk as you prefer.
    e. Make sure that boots normally.
    f. Ensure disk with image file is present and boot PC from MR medium
    g. Restore the image of your Windows partition in place of the newly created Windows partition.
    h. Remove MR bootable medium, reboot, automatic repair hopefully sorts things out, else Startup Repair from Win 10 install disk.

    (I was hoping to save myself some typing..!)
      My Computers


  7. Posts : 14
    Windows 10
    Thread Starter
       #7

    Sorry to wear out your fingers! As long as we're on the same page I'll do the necessary research.

    You seem to know your stuff, so I'll take your word for it that I should be prepared to do a clean reinstall. It's just the least interesting way to solve this kind of problem which meant I had to try for an alternative :)

    Now let' see, how long was it until Win 7 stops receiving security updates...
      My Computer


  8. Posts : 35,468
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #8

    Just a niggling thought- were you confident when you used DISM offline that you were accessing the correct drive letter? I would assume so.. just that if there was a chance of that the DISM results could be misleading.

    I'm sure you're pretty unhappy with Win 10- I've had Win 10 on 1 PC from build 1511, continuously upgraded. Loads of programs installed- far more than the average user. Very few problems.. I avoided the 1803/1809 debacle.
      My Computers


  9. Posts : 14
    Windows 10
    Thread Starter
       #9

    I hope so -- I used the /Image:C:\ flag.

    In the top of the log I did test run the /ScratchDir flag without /Image at first, which is a bit misleading, but here's the line with both:

    2019-09-21 13:38:16, Info DISM DISM.EXE: Executing command line: DISM /ScratchDir:C:\scratch /Image:C:\ /Cleanup-Image /RestoreHealth

    The rest of the flags are inherited from the other suggestions on this site.


    Yeah, you're right, but not because of this. When you're in the middle of immersing yourself in an old GOG game (the main reason I dual boot this machine) like Baldur's Gate, only to have a gigantic Windows Update popup (it runs in 800x600) place itself on top of the game and ruin the whole experience. At that point there's no longer any use running the game and, by extension, Windows 10, since after that I can't stop thinking about when I'll be interrupted next.

    If I were fine with waiting 10 minutes on updates at boot while forgetting what I was supposed to do in Windows "real quick", or waiting 10 minutes on shutdown just to make sure the machine is off before cramming it into a bag, then Windows 10 would probably be endurable. Right now Windows 10 doesn't let users preserve their train of thought, which makes it a UX nightmare. I think it's interesting to follow its evolution, though I wouldn't want to rely on it in its current shape. On a single boot desktop computer it would be a better experience.

    Win7 becomes a security hole in january and macOS is dropping support for 32-bit applications in 10.15. Not a good situation if you like old games sans popups. Maybe I'll just run Win 7 and lock it down. And not upgrade macOS from now on.
      My Computer


  10. Posts : 35,468
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #10

    Your Windows partition isn't necessarily C: as seen from an offline command line.
    (I'm no expert on DISM, I'm afraid).
    Example:
    How to Use DISM Offline Repair Windows 10?

    Windows updates- Home- by default in 1903 you can pause updates for up to 35 days.
    Active Hours - set that in settings to prevent restarts (but not downloads) for an 18 hr period.

    You can take control using 1 of the several (related in some cases) 3rd party utilities.

    See this thread:
    Is there any way to control updates?
    posts #3,4 e.g.

    I have Pro: the worst interruption I get is notification of an update.
      My Computers


 

  Related Discussions
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 19:47.
Find Us




Windows 10 Forums