Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

can't update, can't boot, can't fix, can't sleep


  • Please log in to reply
7 replies to this topic

#1 WileyWon

WileyWon

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:10 PM

Posted 02 November 2017 - 09:58 PM

I'm not a complete moron but I'm beginning to feel like one.   Five days ago, I realized that one of my MS Updates was failing to install at every reboot.  I believe it was KB4041676.  So, I uninstalled it.  But, I didn't reboot the machine.  Then I downloaded the stand-alone version of the update and installed it.  Ever since, my PC has failed to boot and Startup Repair always fails.

Thinking that it was a boot file corruption, I took these steps:
> removed the drive from the machine and cloned it to a 250MB SSD
> attached the SSD drive to another PC
> used EASEUS PM to move the Windows partition a few hundred MB
> created a SYSTEM partition and an EFI partition 
> converted the drive to GPT
> installed the SSD in the original machine
> changed the boot method from Legacy to UEFI
> booted with a RECOVERY USB created on another machine with the same OS ver (without backup files)
> performed all the standard BOOTREC commands, which were all successful.  ScanOS shows 0 Windows installations, which I believe is normal in this configuration

Now when I try to boot from the SSD, it alternates between "your PC couldn't start properly code:0000001" and "Your PC ran into a problem...  Stop Code: inaccessible_boot_device:"
I could be wrong but I feel like this is not a boot file issue.  I believe I am facing the problem caused by the failed Windows update in the first place.


When I boot from the recovery USB and attempt repairs,I get these results:
SFC /verifyOnly fails with "there is a system repair pending..."
Dism /image:c:\ /cleanup-image fails with error 87 
Dism /image:c:\ /cleanup-image/revertPendingActions fails with error "800F082F
 

I can't boot because the image is broken.  I can't fix the image because it won't boot. 

 

Questions:
 

How can I clean up the image so it will boot?  
Is there an OFFLINE method to remove the last few Windows Updates?

Here are my logs:

-----------------------------------------------

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          232 GB  7168 KB        *
  Disk 1    No Media           0 B      0 B
  Disk 2    No Media           0 B      0 B
  Disk 3    No Media           0 B      0 B
  Disk 4    No Media           0 B      0 B
  Disk 5    Online         7633 MB      0 B

DISKPART> list volu

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     I                       DVD-ROM         0 B  No Media
  Volume 1     C   Windows      NTFS   Partition    232 GB  Healthy
  Volume 2         SYSTEM       FAT32  Partition    100 MB  Healthy    Hidden
  Volume 3     E                       Removable       0 B  No Media
  Volume 4     F                       Removable       0 B  No Media
  Volume 5     G                       Removable       0 B  No Media
  Volume 6     H                       Removable       0 B  No Media
  Volume 7     D   RECOVERY     FAT32  Removable   7632 MB  Healthy

DISKPART>exit

-----------------------------------------------
C:\Windows\System32>dism /image:c:\ /cleanup-image /scratchdir:c:\temp11

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0


Error: 87

An error occurred while processing the command.
Ensure that the command-line arguments are valid. For more information, review the log file.

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

------------------------------

2017-10-31 10:02:16, Info                  DISM   PID=1040 TID=1028 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
2017-10-31 10:02:16, Info                  DISM   PID=1040 TID=1028 DismCore.dll version: 10.0.15063.0 - CDISMManager::FinalConstruct
2017-10-31 10:02:16, Info                  DISM   PID=1040 TID=1028 Scratch directory set to 'c:\temp11'. - CDISMManager::put_ScratchDir
2017-10-31 10:02:16, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2017-10-31 10:02:16, Info                  DISM   PID=1040 TID=1028 Successfully loaded the ImageSession at "X:\windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2017-10-31 10:02:16, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2017-10-31 10:02:16, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2017-10-31 10:02:16, Info                  DISM   DISM Manager: PID=1040 TID=1028 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: 
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: 
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.15063, Running architecture=amd64, Number of processors=8
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.15063.0
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Executing command line: dism.exe  /image:c:\ /cleanup-image /revertpendingactions /scratchdir:c:\temp11
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Connecting to the provider located at X:\windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Connecting to the provider located at X:\windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Connecting to the provider located at X:\windows\System32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Connecting to the provider located at X:\windows\System32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Connecting to the provider located at X:\windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Connecting to the provider located at X:\windows\System32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:16, Warning               DISM   DISM Provider Store: PID=1040 TID=1028 Failed to Load the provider: X:\windows\System32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-10-31 10:02:16, Warning               DISM   DISM Provider Store: PID=1040 TID=1028 Failed to Load the provider: X:\windows\System32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2017-10-31 10:02:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
[1040] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
[1040] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
[1040] [0xc142011c] WIMGetMountedImageHandle:(2893)
2017-10-31 10:02:16, Info                  DISM   DISM WIM Provider: PID=1040 TID=1028 [c:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2017-10-31 10:02:16, Info                  DISM   DISM VHD Provider: PID=1040 TID=1028 [c:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2017-10-31 10:02:16, Info                  DISM   DISM VHD Provider: PID=1040 TID=1028 [c:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2017-10-31 10:02:16, Info                  DISM   DISM Imaging Provider: PID=1040 TID=1028 The provider VHDManager does not support CreateDismImage on c:\ - CGenericImagingManager::CreateDismImage
[1040] [0x8007007b] FIOReadFileIntoBuffer:(1259): The filename, directory name, or volume label syntax is incorrect.
[1040] [0xc142011c] UnmarshallImageHandleFromDirectory:(639)
[1040] [0xc142011c] WIMGetMountedImageHandle:(2893)
2017-10-31 10:02:16, Info                  DISM   DISM WIM Provider: PID=1040 TID=1028 [c:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2017-10-31 10:02:16, Info                  DISM   DISM Imaging Provider: PID=1040 TID=1028 The provider WimManager does not support CreateDismImage on c:\ - CGenericImagingManager::CreateDismImage
2017-10-31 10:02:16, Info                  DISM   DISM Imaging Provider: PID=1040 TID=1028 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2017-10-31 10:02:16, Info                  DISM   DISM Manager: PID=1040 TID=1028 physical location path: c:\ - CDISMManager::CreateImageSession
2017-10-31 10:02:16, Info                  DISM   DISM Manager: PID=1040 TID=1028 Event name for current DISM session is Global\__?_Volume{225b370b-44a5-cfe0-2959-ff9e8147920c}__1883465882_262144_162405 - CDISMManager::CheckSessionAndLock
2017-10-31 10:02:16, Info                  DISM   DISM Manager: PID=1040 TID=1028 Create session event 0x1ec for current DISM session and event name is Global\__?_Volume{225b370b-44a5-cfe0-2959-ff9e8147920c}__1883465882_262144_162405  - CDISMManager::CheckSessionAndLock
2017-10-31 10:02:16, Info                  DISM   DISM Manager: PID=1040 TID=1028 Copying DISM from "c:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2017-10-31 10:02:16, Info                  DISM   DISM Manager: PID=1040 TID=1028 Successfully loaded the ImageSession at "c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC" - CDISMManager::LoadRemoteImageSession
2017-10-31 10:02:16, Info                  DISM   DISM Image Session: PID=1084 TID=572 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2017-10-31 10:02:16, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:16, Info                  DISM   DISM OS Provider: PID=1084 TID=572 Defaulting SystemPath to c:\ - CDISMOSServiceManager::Final_OnConnect
2017-10-31 10:02:16, Info                  DISM   DISM OS Provider: PID=1084 TID=572 Host OS verion is 10.0 - CDISMOSServiceManager::RunASICompatibilityShim
2017-10-31 10:02:16, Info                  DISM   DISM OS Provider: PID=1084 TID=572 Defaulting Windows folder to c:\Windows - CDISMOSServiceManager::Final_OnConnect
2017-10-31 10:02:16, Info                  DISM   DISM OS Provider: PID=1084 TID=572 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath
2017-10-31 10:02:16, Warning               DISM   DISM OS Provider: PID=1084 TID=572 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
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2017-10-31 10:02:17, Warning               DISM   DISM Provider Store: PID=1084 TID=572 Failed to Load the provider: c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2017-10-31 10:02:17, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2017-10-31 10:02:17, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2017-10-31 10:02:17, Info                  DISM   DISM Manager: PID=1040 TID=1028 Image session successfully loaded from the temporary location: c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC - CDISMManager::CreateImageSession
2017-10-31 10:02:17, Info                  DISM   DISM OS Provider: PID=1084 TID=572 Setting SystemPath to c:\ - CDISMOSServiceManager::SetSystemPath
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.15063.0, Image architecture=amd64
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Package Manager: PID=1084 TID=572 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2017-10-31 10:02:17, Info                  CBS    Universal Time is: 2017-10-31 18:02:17.465
2017-10-31 10:02:17, Info                  CBS    Failed to find a matching version for servicing stack: c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2017-10-31 10:02:17, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2017-10-31 10:02:17, Info                  CBS    Offline servicing, using stack version from: c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\cbscore.dll
2017-10-31 10:02:17, Info                  CBS    Loaded Servicing Stack v10.0.15063.0 with Core: c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\cbscore.dll
2017-10-31 10:02:17, Info                  CBS    Setting core mode: CbsCoreModeOffline
2017-10-31 10:02:17, Info                  CSI    00000001@2017/10/31:18:02:17.465 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffbd1164219 @0x7ffbd159ce96 @0x7ffbd159c1a4 @0x7ffbd18028f2 @0x7ffbd1802af5 @0x7ffbd17c02b9)
2017-10-31 10:02:17, Info                  CBS    Lock: New lock added: CCbsSessionManager, level: 11, total lock:14
2017-10-31 10:02:17, Info                  CBS    Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:15
2017-10-31 10:02:17, Info                  CBS    Lock: New lock added: FlightPackageCacheCriticalSection, level: 128, total lock:16
2017-10-31 10:02:17, Info                  CBS    Lock: New lock added: CCbsWorkerQueue, level: 60, total lock:17
2017-10-31 10:02:17, Info                  CBS    Lock: New lock added: CCbsWorkerQueue:m_WindowsUpdateExpressDownloadLock, level: 10, total lock:18
2017-10-31 10:02:17, Info                  DISM   DISM Package Manager: PID=1084 TID=572 Loaded servicing stack for offline use only. - CDISMPackageManager::CreateCbsSession
2017-10-31 10:02:17, Info                  CBS    Lazy store initialization mode
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  CSI    00000001 Shim considered [l:125]'\??\c:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2017-10-31 10:02:17, Info                  CSI    00000002 Shim considered [l:122]'\??\c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wcp.dll' : got STATUS_SUCCESS
2017-10-31 10:02:17, Info                  CSI    00000001 Shim considered [l:125]'\??\c:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2017-10-31 10:02:17, Info                  CSI    00000002 Shim considered [l:122]'\??\c:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wcp.dll' : got STATUS_SUCCESS
2017-10-31 10:02:17, Info                  DISM   DISM OS Provider: PID=1084 TID=572 Get the registry path to the SOFTWARE hive located at c:\Windows\system32\config\SOFTWARE and determine if it is loaded. - CDISMOSServiceManager::DetermineBootDrive
2017-10-31 10:02:17, Info                  DISM   DISM Driver Manager: PID=1084 TID=572 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Warning               DISM   DISM Provider Store: PID=1084 TID=572 Failed to Load the provider: c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Connecting to the provider located at c:\temp11\18EE59C8-00C1-43C6-8617-C6A54E782FFC\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2017-10-31 10:02:17, Info                  DISM   DISM Transmog Provider: PID=1084 TID=572 Current image session is [OFFLINE] - CTransmogManager::GetMode
2017-10-31 10:02:17, Info                  DISM   DISM Transmog Provider: PID=1084 TID=572 Determined WinDir path = [c:\Windows] - CTransmogManager::GetWinDirPath
2017-10-31 10:02:17, Info                  DISM   DISM Transmog Provider: PID=1084 TID=572 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
2017-10-31 10:02:17, Info                  DISM   DISM Transmog Provider: PID=1084 TID=572 Product Type: [WinNT] - CTransmogManager::Initialize
2017-10-31 10:02:17, Info                  DISM   DISM Transmog Provider: PID=1084 TID=572 Product Type ServerNT : [No] - CTransmogManager::Initialize
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IBSManager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: ProvManager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: ProvManager.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericManager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericManager.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2017-10-31 10:02:17, Info                  DISM   DISM Package Manager: PID=1084 TID=572 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2017-10-31 10:02:17, Info                  DISM   DISM Package Manager: PID=1084 TID=572 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2017-10-31 10:02:17, Info                  DISM   DISM Package Manager: PID=1084 TID=572 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2017-10-31 10:02:17, Info                  DISM   DISM Package Manager: PID=1084 TID=572 CBS session options=0x800! - CDISMPackageManager::Internal_Finalize
2017-10-31 10:02:17, Info                  CBS    Lazy store initialization mode, fully initialize.
2017-10-31 10:02:17, Info                  CBS    Offline image is writable
2017-10-31 10:02:17, 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'.
2017-10-31 10:02:17, 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'.
2017-10-31 10:02:17, 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'.
2017-10-31 10:02:17, 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'.
2017-10-31 10:02:17, 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'.
2017-10-31 10:02:17, 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'.
2017-10-31 10:02:17, 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'.
2017-10-31 10:02:17, Info                  CBS    Loading offline registry hive: BCD, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Boot/BCD' from path '\\?\c:\Boot\BCD'.
2017-10-31 10:02:17, Info                  CBS    Loading offline registry hive: ntuser.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Users/Default/ntuser.dat' from path '\\?\c:\Users\Default\ntuser.dat'.
2017-10-31 10:02:17, Info                  CBS    Loading offline registry hive: schema.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/system32/smi/store/Machine/schema.dat' from path '\\?\c:\Windows\system32\smi\store\Machine\schema.dat'.
2017-10-31 10:02:17, Info                  CSI    00000002 CSI Store 2676336497872 initialized
2017-10-31 10:02:17, Info                  CBS    Session: 1084_2772375 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2017-10-31 10:02:17, Info                  CBS    Client specified cancelling all pended transactions.
2017-10-31 10:02:17, Info                  CBS    Exec: Session processing started.  Client: DISM Package Manager Provider, Session(Cancelling): 1084_2772375
2017-10-31 10:02:17, Error                 CBS    Exec: Cannot finalize session because execution is frozen. [HRESULT = 0x800f082f - CBS_E_EXCLUSIVE_WOULD_MERGE]
2017-10-31 10:02:17, Info                  CBS    Exec: Processing complete, session(Cancelling): 1084_2772375 [HRESULT = 0x800f082f - CBS_E_EXCLUSIVE_WOULD_MERGE]
2017-10-31 10:02:17, Error                 CBS    Session: 1084_2772375 failed to perform cancelling all pending transactions. [HRESULT = 0x800f082f - CBS_E_EXCLUSIVE_WOULD_MERGE]
2017-10-31 10:02:17, Info                  CBS    Session: 1084_2772375 finalized. Reboot required: no [HRESULT = 0x800f082f - CBS_E_EXCLUSIVE_WOULD_MERGE]
2017-10-31 10:02:17, Error                 DISM   DISM Package Manager: PID=1084 TID=572 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f082f)
2017-10-31 10:02:17, Info                  CBS    Releasing offline store key
2017-10-31 10:02:17, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SOFTWARE
2017-10-31 10:02:17, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2017-10-31 10:02:17, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SYSTEM
2017-10-31 10:02:17, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SYSTEM, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2017-10-31 10:02:17, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SECURITY
2017-10-31 10:02:17, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SECURITY, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2017-10-31 10:02:17, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SAM
2017-10-31 10:02:17, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/SAM, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2017-10-31 10:02:17, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/COMPONENTS
2017-10-31 10:02:17, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/COMPONENTS, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2017-10-31 10:02:17, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DRIVERS
2017-10-31 10:02:17, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DRIVERS, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2017-10-31 10:02:17, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DEFAULT
2017-10-31 10:02:17, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/System32/config/DEFAULT, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2017-10-31 10:02:17, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Users/Default/ntuser.dat
2017-10-31 10:02:17, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Windows/system32/smi/store/Machine/schema.dat
2017-10-31 10:02:17, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}c:/Boot/BCD
2017-10-31 10:02:17, Error                 DISM   DISM Package Manager: PID=1084 TID=572 An error occured clearing the pending actions from the image. - CDISMPackageManager::RevertPendingActions(hr:0x800f082f)
2017-10-31 10:02:17, Error                 DISM   DISM Package Manager: PID=1084 TID=572 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f082f)
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Package Manager: PID=1084 TID=572 Finalizing CBS core. - CDISMPackageManager::Finalize
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: GetPublicObjectMonitor::Audit
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: WcpUnload
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: DrupUnload
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: DpxUnload
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: SrUnload
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2017-10-31 10:02:17, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM OS Provider: PID=1084 TID=572 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1084 TID=572 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Manager: PID=1040 TID=1028 Closing session event handle 0x1ec - CDISMManager::CloseImageSession
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: 
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2017-10-31 10:02:17, Info                  DISM   DISM.EXE: 
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2017-10-31 10:02:17, Info                  DISM   DISM Provider Store: PID=1040 TID=1028 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
----------------------------------------------



BC AdBot (Login to Remove)

 


m

#2 jenae

jenae

  • Members
  • 175 posts
  • OFFLINE
  •  
  • Local time:02:10 PM

Posted 02 November 2017 - 11:17 PM

Hi, you might be able to clear this with a restoration of the registry if time allows, win 10 makes a regbackup every 7-10 days. It appears you can access the RE (recovery environment) and use a command prompt.

 

Print out these cmd's to make it easier for you.

 

Open a cmd prompt and type :- (type cmd's exactly as you see here, syntax is important)

 

bcdedit | find "osdevice" 

 

(press enter, the | is called a pipe and is above the \ key), it will return ...OS device partition...X (where X is a drive letter) use this letter in the following cmd's. Often in 10 this will be D (do not worry if C: drive is the normal OS drive things work differently here, we will use D in this example)

 

Next type:-

 

D:  (press enter)

 

Next type:-

 

cd D:\Windows\System32\ Config (press enter)

 

Next type:-

 

Dir (press enter)

 

The contents of the system32 \config file will open, if the regback date, is before this happened, then continue (if not you have lucked out)

 

Next type:-

 

cd regback (press enter)

 

Next type:-

 

copy *.* D:\windows\system32\config (press enter)

 

Type:- ALL to the proceed prompt, that's it, the registry has been restored to the date of the regback, see how you go.



#3 WileyWon

WileyWon
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:10 PM

Posted 03 November 2017 - 07:21 AM

So, you're working under the theory that there are registry entries preventing me from booting?  I suppose that is likely.  A WindowsUpdate will definitely do that.  But, the problem could also be mis-matched files, right?   I would love to be able to run SFC if I can get past the "pending updates" thing. 

 

I will try your suggestion tonight.  Nothing else has worked.

 

I still have the original drive with the boot problem before it was cloned.  I may clone it again, just to eliminate the variables of GPT, UEFI, and partition changes.

 

Is there a way I can monitor (log) the boot process so we can see exactly where the failure occurs?

 

Others have suggested that I do a clean install but I have a few problems with that.  The biggest is Office 2016 because I don't have the install key.



#4 dmccoyks

dmccoyks

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:10 PM

Posted 09 November 2017 - 06:19 PM

If you are only concerned about not doing a clean install becaue you dont have your program keys. You can download something like the follwoing and it will provide you with a list of your keys.

https://www.belarc.com/en/products_belarc_advisor

#5 britechguy

britechguy

    Been there, done that, got the T-shirt


  • Moderator
  • 5,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Staunton, VA
  • Local time:10:10 PM

Posted 09 November 2017 - 06:30 PM

Also, as an aside, if you are using a Microsoft Account linked Windows 10 user account you should log in to the Microsoft Account and see if your Office Software is "on the record" there.

 

If it is you will be able to reinstall and you should also be able to get the product key.

 

The above being said, I love Belarc Advisor and use it any time I am either reinstalling Windows on a machine or setting up a new machine to replace an old one.  Users always forget exactly what software they've installed, particularly for rarely used stuff, and lose their license keys/product keys, too.  I use it to inventory what's installed so that I can review it with the client to decide what we need to reinstall.


Brian  AKA  Bri the Tech Guy (website address in my profile) Windows 10 Home, 64-bit, Version 1709, Build 16299

       

    Plus ça change, plus c'est la même chose
              

 


#6 WileyWon

WileyWon
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:10 PM

Posted 13 November 2017 - 08:37 AM

I think my topic has been hi-jacked.   This discussion was not supposed to be about licensing.  The machine I'm trying to fix was given to me by somebody who loses everything.  There is less than a 5% chance that he would be able to find his login information to MS.

 

My original question was "how to fix a Windows 10 installation that won't boot" after it was clobbered by a crappy MS Fall Creators update.  After wasting 8 days on this, I finally had to give up and re-build my system from scratch and buy MS Office 2016.

 

Since then, I have had two of my clients report almost the exact same issue.  Everything is fine, Fall Creators Update comes along, everything is still fine.   But, when it eventually comes time to reboot, the user is stuck between two different error messages.  One of them is "inaccessible_boot_device".   None of the solutions that I have found online have been successful.

 

If three people in my little world have suffered this problem, there must be thousands of others.  Why don't we know how to fix it?



#7 britechguy

britechguy

    Been there, done that, got the T-shirt


  • Moderator
  • 5,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Staunton, VA
  • Local time:10:10 PM

Posted 13 November 2017 - 09:23 AM

Because it could be that it is only those three people.  There is currently an ongoing thread on the Windows 7 forum about "inaccessible boot device," which is hardly unique and happens in other versions of Windows.

 

It often takes a while to figure out how to fix something, and some things never have an actual fix.  That is the way of cyber life.


Brian  AKA  Bri the Tech Guy (website address in my profile) Windows 10 Home, 64-bit, Version 1709, Build 16299

       

    Plus ça change, plus c'est la même chose
              

 


#8 WileyWon

WileyWon
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:10 PM

Posted 13 November 2017 - 05:13 PM

I was born in Staunton Va on a Tuesday, but it wasn't last Tuesday.

 

Hundreds of thousands of people have the Windows 10 Creators update.

Tens of thousands have received the Windows 10 Fall Creators update.

Some of them have no problems.  Others have major problems.

 

I'm not a mathematician, but the chances of me knowing the only three people with this problem is about the same as a meteor hitting my house in the next 15 minutes.

 

Here is an article that explains what my two clients and I have suffered.   http://www.drivethelife.com/windows-10/fix-windows-10-boot-loop-after-fall-creators-update.html

 

I'm sure there are many many many more.  But, the devil is in the details.  In my case, the /checkhealth thing turned up problems in my image.  For others, the image is fine but it still won't boot.

 

Here is a question, in case you are sincere about helping to get this solved:

 

When Client #1 goes into DiskPart and does List Vol, he sees something like this:

 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     E                       DVD-ROM         0 B  No Media
  Volume 1     C    Data         NTFS   Partition    600 GB  Healthy
  Volume 3           SYSTEM       FAT32  Partition    263 MB  Healthy    Hidden
  Volume 4     D                    NTFS   Partition    183 GB  Healthy    Boot
  Volume 5           Recovery     NTFS   Partition    499 MB  Healthy    Hidden
  Volume 6                             FAT32  Partition    100 MB  Healthy    System
 

Is it is a problem that his C & D are reversed?   I can change them with DISKPART but the changes won't survive a boot.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users