Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

PROCESS1_INITIALIZATION_ERROR on startup, cannot boot to Win 10

- - - - -

  • Please log in to reply

#16
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,833 posts

I admit that I am stumped and can only see a fresh install of the OS as the solution, FreeBooter may have some further suggestions for you and i will meanwhile ponder on it.

 

Edit to add;

 

Sorry was a bit rushed this morning and replied before heading off to work;

 

I previously asked what is shown to be on the D: drive, can you tell us please.

 

Noted the following in your last reply;

 

I dread having to reinstall software on this computer - my boy will not be happy.

 

The SSD that you installed Windows 10 to is just about large enough for the OS and therefore reinstalling Windows 10 would not be as much trouble as reinstalling an OS on a larger SSD or HDD that was partitioned, I would not recommend partitioning such a small drive so that it has both the OS and data on it and would definitely not save any data to it other than Windows updates etc.


Edited by phillpower2, 30 March 2016 - 08:11 AM.
As per the above.

  • 0

Advertisements


#17
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts

Apologies for my absence and wrongly assuming that you already had Windows 10 media Cerberus262, I misread what you meant by "I'm not ready to try reinstalling Win10,"
 
Couple of observations from the work that the two of you have been doing;
 

Volume 1     C   System Rese  NTFS   Partition    100 MB  Healthy

 
The drive/partition that Windows is installed on is automatically allocated the drive letter C: by Windows, 100MB is not enough space for any OS but it is enough for a System Reserved partition in Windows 7, not enough for it to be System Reserved for Windows 8 or 10 though as it would take up 350MB of space.
 

It seems I can access anything on either the D: or X: drives...

 
D: when not allocated to an optical drive is commonly a data partition on the same storage device as what the C: Windows partition is on, being that you can access the D: drive/partition can you tell us what exactly is on it.
 
Going by the above it looks like you upgraded from Windows 7 to 10, is that correct, if yes, how long ago.
 
Thank you for the additional assistance FreeBooter  :thumbsup: a word to the wise though, please avoid offering any assistance that is any way related to malware removal as in suggesting that Cerberus262 disinfect their computer in your reply #11, the GTG Terms of Use prohibits this;
 

Because of the potential for harm, only staff members approved for malware removal are allowed to offer malware removal advice or reply to malware topics.

 

 

@phillpower2 how would i go about instructing OP or any other members that i believe should have a malware infection checkup? 

 

If the 100 MB or 350 MB System Reserved partition missing or corrupted message like Boot Configuration Data was missing, should be displayed on the screen and that we’d have to repair our computer with Windows installation media the Startup Repair should have repaired this issue by now.  Looking at the logs the System files integrity check and repair has failed which we are also having issue running the scans to check and repair Windows system files. I would say the HDD/SSD could be failing which could cause SFC and Dism command not able to access Windows system files. OP as i suggested use HDD/SSD Diagnostic tool to view SMART report of the HDD or SSD drive.

 

Lets mark the System partition active from Command Prompt type below commands.

 

 

Diskpart

 

Select Disk 0

 

Select Volume 1

 

Active

 

Exit

 

Replace number 1 with System Reserved partition assign volume number which you can display this information by typing List Volume command.

Restart computer to see if issue resolved.

 

 

If issue is not resolved try below commands:

 

 

mkdir D:\Scratch
 

DISM /Image:D:\ /ScratchDir:D:\Scratch /Cleanup-Image /RevertPendingActions

 

Execute below command:

 

DISM image:D:\  /Cleanup-Image /RestoreHealth /source:X:\Sources\Install.wim:1 /LimitAccess

 

Replace X: drive letter with drive letter of Windows Setup DVD drive letter.

 

 

 

 

 

If you have upgraded from previous version of Windows O/S you can downgrade to previous version of Windows O/S form WinRe Advanced options.

Windows-10-Backup-and-Recovery-Advanced-

 

 

"Go Back to the previous build"

http://www.tenforums...us-windows.html


Edited by FreeBooter, 30 March 2016 - 08:07 AM.

  • 0

#18
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,833 posts

Point them towards the Malware and Spyware Cleaning Guide  information here please FreeBooter  :thumbsup:


  • 0

#19
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts

Point them towards the Malware and Spyware Cleaning Guide  information here please FreeBooter  :thumbsup:

I will do so in future thank you!


  • 0

#20
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,833 posts

You are most welcome and thank you for helping out on the forums  :)  :thumbsup:


  • 0

#21
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

Well, here is the result of the commands suggested:

 

The ACTIVE command did not resolve the problem on restart. Same loop.

 

The other commands resulted in the following errors (after each error, I have included the DISM log referenced.):

 

 
Error: 1392
 
An error occurred accessing the temporary folder d:\scratch\98959F0D-90DB-4309-819B-4B7FE325594F.
Ensure that the path to the temporary folder exists and that you have Read/Write permissions on the folder.
 
The DISM log file can be found at X:\windows\Logs\DISM\dism.log
 
-------------
2016-03-31 13:54:53, Info                  DISM   PID=476 TID=540 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
2016-03-31 13:54:53, Info                  DISM   PID=476 TID=540 DismCore.dll version: 10.0.10586.11 - CDISMManager::FinalConstruct
2016-03-31 13:54:53, Info                  DISM   PID=476 TID=540 Scratch directory set to 'd:\scratch'. - CDISMManager::put_ScratchDir
2016-03-31 13:54:53, Info                  DISM   PID=476 TID=540 Successfully loaded the ImageSession at "X:\Sources" - CDISMManager::LoadLocalImageSession
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Manager: PID=476 TID=540 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: 
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: 
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.10586, Running architecture=amd64, Number of processors=4
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.10586.0
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Executing command line: dism  /image:d:\ /scratchdir:d:\scratch /cleanup-image /revertpendingactions
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Loading Provider from location X:\Sources\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Connecting to the provider located at X:\Sources\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Loading Provider from location X:\Sources\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Connecting to the provider located at X:\Sources\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Loading Provider from location X:\Sources\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Connecting to the provider located at X:\Sources\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Loading Provider from location X:\Sources\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Connecting to the provider located at X:\Sources\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Loading Provider from location X:\Sources\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Connecting to the provider located at X:\Sources\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Loading Provider from location X:\Sources\FfuProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Warning               DISM   DISM Provider Store: PID=476 TID=540 Failed to Load the provider: X:\Sources\FfuProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
[476] [0x80070002] FIOReadFileIntoBuffer:(1250): The system cannot find the file specified.
[476] [0xc142011c] UnmarshallImageHandleFromDirectory:(793)
[476] [0xc142011c] WIMGetMountedImageHandle:(3046)
2016-03-31 13:54:53, Info                  DISM   DISM WIM Provider: PID=476 TID=540 [d:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2016-03-31 13:54:53, Info                  DISM   DISM VHD Provider: PID=476 TID=540 [d:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Getting Provider VHDManager - CDISMProviderStore::GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM VHD Provider: PID=476 TID=540 [d:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2016-03-31 13:54:53, Info                  DISM   DISM Imaging Provider: PID=476 TID=540 The provider VHDManager does not support CreateDismImage on d:\ - CGenericImagingManager::CreateDismImage
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Getting Provider WimManager - CDISMProviderStore::GetProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
[476] [0x80070002] FIOReadFileIntoBuffer:(1250): The system cannot find the file specified.
[476] [0xc142011c] UnmarshallImageHandleFromDirectory:(793)
[476] [0xc142011c] WIMGetMountedImageHandle:(3046)
2016-03-31 13:54:53, Info                  DISM   DISM WIM Provider: PID=476 TID=540 [d:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2016-03-31 13:54:53, Info                  DISM   DISM Imaging Provider: PID=476 TID=540 The provider WimManager does not support CreateDismImage on d:\ - CGenericImagingManager::CreateDismImage
2016-03-31 13:54:53, Info                  DISM   DISM Imaging Provider: PID=476 TID=540 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2016-03-31 13:54:53, Info                  DISM   DISM Manager: PID=476 TID=540 physical location path: d:\ - CDISMManager::CreateImageSession
2016-03-31 13:54:53, Info                  DISM   DISM Manager: PID=476 TID=540 Event name for current DISM session is Global\__?_Volume{6143ba6e-0000-0000-0000-500600000000}__3371616124_786432_93715 - CDISMManager::CheckSessionAndLock
2016-03-31 13:54:53, Info                  DISM   DISM Manager: PID=476 TID=540 Create session event 0x1e0 for current DISM session and event name is Global\__?_Volume{6143ba6e-0000-0000-0000-500600000000}__3371616124_786432_93715  - CDISMManager::CheckSessionAndLock
2016-03-31 13:54:53, Info                  DISM   DISM Manager: PID=476 TID=540 Copying DISM from "d:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2016-03-31 13:54:53, Error                 DISM   DISM Manager: PID=476 TID=540 Failed to copy the image provider store out of the image. - CDISMManager::CreateImageSessionFromLocation(hr:0x80070570)
2016-03-31 13:54:53, Error                 DISM   DISM.EXE: Could not load the image session. HRESULT=80070570
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: 
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2016-03-31 13:54:53, Info                  DISM   DISM.EXE: 
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 13:54:53, Info                  DISM   DISM Provider Store: PID=476 TID=540 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
 
------------
 
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
 
 
Error: 1392
 
An error occurred accessing the temporary folder X:\windows\TEMP\E45336C8-F01E-4AF3-B138-30ADAE346BB7.
Ensure that the path to the temporary folder exists and that you have Read/Write permissions on the folder.
 
The DISM log file can be found at X:\windows\Logs\DISM\dism.log
 
------------
 
2016-03-31 14:01:15, Info                  DISM   PID=676 TID=664 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
2016-03-31 14:01:15, Info                  DISM   PID=676 TID=664 DismCore.dll version: 10.0.10586.0 - CDISMManager::FinalConstruct
2016-03-31 14:01:15, Info                  DISM   PID=676 TID=664 Successfully loaded the ImageSession at "X:\windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Manager: PID=676 TID=664 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: 
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: 
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.10586, Running architecture=amd64, Number of processors=4
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.10586.0
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Executing command line: dism  /image:d:\ /cleanup-image /restorehealth /source:e:\sources\install.wim:1 /limitaccess
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Loading Provider from location X:\windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Connecting to the provider located at X:\windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Loading Provider from location X:\windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Connecting to the provider located at X:\windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Loading Provider from location X:\windows\System32\Dism\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Connecting to the provider located at X:\windows\System32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Loading Provider from location X:\windows\System32\Dism\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Connecting to the provider located at X:\windows\System32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Loading Provider from location X:\windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Connecting to the provider located at X:\windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Loading Provider from location X:\windows\System32\Dism\FfuProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Connecting to the provider located at X:\windows\System32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
[676] [0x8007007b] FIOReadFileIntoBuffer:(1250): The filename, directory name, or volume label syntax is incorrect.
[676] [0xc142011c] UnmarshallImageHandleFromDirectory:(793)
[676] [0xc142011c] WIMGetMountedImageHandle:(3046)
2016-03-31 14:01:15, Info                  DISM   DISM WIM Provider: PID=676 TID=664 [d:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2016-03-31 14:01:15, Info                  DISM   DISM VHD Provider: PID=676 TID=664 [d:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Getting Provider VHDManager - CDISMProviderStore::GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM VHD Provider: PID=676 TID=664 [d:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2016-03-31 14:01:15, Info                  DISM   DISM Imaging Provider: PID=676 TID=664 The provider VHDManager does not support CreateDismImage on d:\ - CGenericImagingManager::CreateDismImage
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Getting Provider WimManager - CDISMProviderStore::GetProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
[676] [0x8007007b] FIOReadFileIntoBuffer:(1250): The filename, directory name, or volume label syntax is incorrect.
[676] [0xc142011c] UnmarshallImageHandleFromDirectory:(793)
[676] [0xc142011c] WIMGetMountedImageHandle:(3046)
2016-03-31 14:01:15, Info                  DISM   DISM WIM Provider: PID=676 TID=664 [d:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2016-03-31 14:01:15, Info                  DISM   DISM Imaging Provider: PID=676 TID=664 The provider WimManager does not support CreateDismImage on d:\ - CGenericImagingManager::CreateDismImage
2016-03-31 14:01:15, Info                  DISM   DISM Imaging Provider: PID=676 TID=664 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2016-03-31 14:01:15, Info                  DISM   DISM Manager: PID=676 TID=664 physical location path: d:\ - CDISMManager::CreateImageSession
2016-03-31 14:01:15, Info                  DISM   DISM Manager: PID=676 TID=664 Event name for current DISM session is Global\__?_Volume{6143ba6e-0000-0000-0000-500600000000}__3371616124_786432_93715 - CDISMManager::CheckSessionAndLock
2016-03-31 14:01:15, Info                  DISM   DISM Manager: PID=676 TID=664 Create session event 0x1e8 for current DISM session and event name is Global\__?_Volume{6143ba6e-0000-0000-0000-500600000000}__3371616124_786432_93715  - CDISMManager::CheckSessionAndLock
2016-03-31 14:01:15, Info                  DISM   DISM Manager: PID=676 TID=664 Copying DISM from "d:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2016-03-31 14:01:15, Error                 DISM   DISM Manager: PID=676 TID=664 Failed to copy the image provider store out of the image. - CDISMManager::CreateImageSessionFromLocation(hr:0x80070570)
2016-03-31 14:01:15, Error                 DISM   DISM.EXE: Could not load the image session. HRESULT=80070570
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: 
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2016-03-31 14:01:15, Info                  DISM   DISM.EXE: 
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-31 14:01:15, Info                  DISM   DISM Provider Store: PID=676 TID=664 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
 
 
Any clues in this? I am trying to get one of the referenced disk tests run, but unless one runs from CD/DVD or USB, I will need to pull the drive and buy USB cable to attach to my laptop. Do you know if any run outside of Windows?
 
Thanks for all the help - hopefully we can find a solution.

  • 0

#22
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

Downloaded HDDScan and did the Short Test and Surface Read Test. No errors on either. Seems like the SSD is good. Now that I have the drive pulled, I am going to try a virus scan as well. Will let you know results.


  • 0

#23
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts

Create yourself a Knoppix or Puppy Linux live CD and see if you can access files on partition where Windows installed from linux live CD. If you connected the SSD to another computer then see if you can access the files on partition Windows installed.


Edited by FreeBooter, 31 March 2016 - 08:22 PM.

  • 0

#24
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

I can access the entire SSD - I have attached via USB cable to another Win10 computer.

 

I tried the virus scan (Windows Defender), found SoftwareBundler:Win32/Mizenota which I removed. It was located in the recycling bin on the main partition.

 

Tried rebooting, no change.


  • 0

#25
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts

Have you ask for malware checkup refer here to do so.


  • 0

Advertisements


#26
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts

If the computer you connect the SSD has a Windows operating system then run the commands from that computer run Sfc /Scannow /OFFBOOTDIR=X:\    /OFFWINDIR=X:\windows command from computer where SSD attached replace the X:\ drive letter with SSD assigned drive letter. You should one more time run Chkdsk  X: /R command before running SFC command.


  • 0

#27
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

Ran CHKDSK, found no errors. Ran the other command and got same error - "Windows Resource Protection could not perform the requested operation". I did both from command line run as administrator.

 

Time to try the other set of commands?


  • 0

#28
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts

There are few reasons why Sfc and Dism command wont work first is NTFS file system damage second is SSD is malfunctioning running short or long test with HDDScan far as i know only reports if there are bad sectors but does not report errors with file system or MBR or with boot sectors or errors for volume boot record also HDDScan does not repair any issues this program only reports. If you have not then have a look at SMART health report of the SSD. I need you to try one more thing that is to restore registry hives files from backup Windows created. Connect the SSD to working computer and from Windows Explorer navigate to C:\Windows\System32\Config folder rename all hive files with .bak extension like below.

 

 

System.bak

Software.bak

Sam.bak

Default.bak

Security.bak

 

Copy all registry hive files store at in RegBack folder to the C:\Windows\System32\Config folder.

Connect SSD to computer and see if you can boot Windows O/S.


Edited by FreeBooter, 01 April 2016 - 01:54 AM.

  • 0

#29
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

SMART report showed drive to be ok.

 

Tried copying backup registry files to config folder, attempted to boot, no success. Same error. I did note that there were differences in file sized between backup and original files you suggested replacing...

 

Next step?


  • 0

#30
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts

Don't worry about the registry hive size you need to backup your data and reinstall Windows OS this is the only option left and this is only way to make sure there is no faulty hardware.


Edited by FreeBooter, 02 April 2016 - 10:40 AM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP