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

#1
Cerberus262

Cerberus262

    Member

  • Member
  • PipPip
  • 72 posts

On turning on the computer, I get a BSOD with the error listed above. It tries an automatic repair, does nothing but get me to an advanced options screen where I can then choose "Troubleshoot" and try various options. I have no System Restore points, so that one is out. I'm not ready to try reinstalling Win10, so can anyone assist me in trying to find out exactly what's causing the error and fix without a reinstall? I can get to a command prompt through the advanced options, so I assume I can try to find any error logs. I'm not up on reading those and fixing myself. 

 

I have tried removing all connections to the computer (USB, second HD, LAN, etc) and restarting with no effect.There has been no hardware or software installed recently that would lead me to believe that's the cause.

 

Any help would be very much appreciated!

 

TIA!

 

UPDATE: Following is a logfile I managed to copy over. Maybe this will be of some assistance...

 

Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎3/‎2/‎2016 12:51:39 PM (GMT)
Number of repair attempts: 21
 
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = D:\WINDOWS
AutoChk Run = 0
Number of root causes = 1
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 234 ms
 
Test Performed: 
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 1531 ms
 
Test Performed: 
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code =  0x0
Time taken = 469 ms
 
Test Performed: 
---------------------------
Name: Access control test
Result: Completed successfully. Error code =  0x0
Time taken = 7516 ms
 
Test Performed: 
---------------------------
Name: File system test (chkdsk)
Result: Completed successfully. Error code =  0x0
Time taken = 20625 ms
 
Test Performed: 
---------------------------
Name: Software installation log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Root cause found: 
---------------------------
A patch is preventing the system from starting.
 
Repair action: System files integrity check and repair
Result: Failed. Error code =  0xa
Time taken = 2171 ms
 
---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = D:\WINDOWS
AutoChk Run = 0
Number of root causes = 1
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 422 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 78 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Root cause found: 
---------------------------
Startup Repair has tried several times but still cannot determine the cause of the problem.
 
---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = D:\WINDOWS
AutoChk Run = 0
Number of root causes = 1
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 422 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 78 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Root cause found: 
---------------------------
Startup Repair has tried several times but still cannot determine the cause of the problem.
 
---------------------------
---------------------------

Edited by Cerberus262, 26 March 2016 - 08:11 AM.

  • 0

Advertisements


#2
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

Hello Cerberus262,

 

I can get to a command prompt through the advanced options,

 

 

From the command prompt, type sfc /scannow and then press Enter, it is sometimes necessary to re-start the computer and run SFC up to 3/4 times before all errors are repaired.


  • 0

#3
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

Thanks for the response!

 

I have tried the SFC command a number of times, rebooting between. I get the following error after it gets to 100% of the scan:

 

"Windows Resource Protection could not perform the requested operation."

 

I am assuming it's trying to do some repair action but cannot? What next?


  • 0

#4
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

This means that the files that are required to carry out the repairs to the OS are not available.

 

From the command prompt/Administrator type DISM /Online /Cleanup-Image /RestoreHealth then press Enter, this may take up to ten minutes or so**, once finished try restarting then running SFC again.

 

** DISM may appear to hang at around 20% but please allow it to finish.


  • 0

#5
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

Got message that "DISM does not support servicing Windows PE with the /Onlne option". Is this because I'm trying this prior to Win10 boot?


  • 0

#6
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 posts

It should run from command prompt and the fact that it is not suggests the best option is to use your Windows 10 media to reset the present OS, you can do this without losing any of your personal data but may need to reinstall certain apps, see the resetting your PC option here


  • 0

#7
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts

The DISM /Online /Cleanup-Image /RestoreHealth cannot repair damage files if its executed from Windows Recovery Environment (WinRE) as this command uses the Windows Update to repair damage components which does not work under Windows Recovery Environment.  Execute Sfc /Scannow /OFFBOOTDIR=C:\    /OFFWINDIR=C:\windows command to repair damage system files. Replace the C:\ drive letter with Windows partition assigned drive letter.  When computer boots into WinRE environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

You should also run check disk to repair damage file system and bad sectors type Chkdsk  C:  /r  command. Replace the C: drive letter with Windows partition assigned drive letter.


Edited by FreeBooter, 28 March 2016 - 05:34 AM.

  • 0

#8
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

Windows dir is D as you thought it might be.

 

First command string gets me the following: "There is a system repair pending which required reboot to complete. Restart Windows and run sfc again". Tried restarting and still gets me the same error loop, back to advanced options letting me get to command prompt. Ran command again, same error.

 

Ran the chkdsk - no bad sectors, said no problems, no further action is required. It did say at the end "failed to transfer logged messages to the event log with status 50." Assuming that's just due to the WinPE environment?

 

So... we have ruled out bad hard drive. How can we get the repair function to operate?


  • 0

#9
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts

Execute Del /f  /a  D:\Windows\WinSxS\Pending.xml  command and run the Sfc command if you still get the "There is a system repair pending which required reboot to complete" error then execute Del /f  /a  X:\Windows\WinSxS\Pending.xml  command and try to run SFC command.  If the error message still displayed then run Dism  /Image:D:\Windows  /Cleanup-Image  /RevertPendingActions command and try to run the Sfc /Scannow /OFFBOOTDIR=D:\    /OFFWINDIR=D\Windows command. Have you recently installed any new hardware or device driver or software before this boot issue started.


Edited by FreeBooter, 28 March 2016 - 09:55 AM.

  • 0

#10
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

Execute Del /f  /a  D:\Windows\WinSxS\Pending.xml  command and run the Sfc command if you still get the "There is a system repair pending which required reboot to complete" error then execute Del /f  /a  X:\Windows\WinSxS\Pending.xml  command and try to run SFC command.  If the error message still displayed then run Dism  /Image:D:\Windows  /Cleanup-Image  /RevertPendingActions command and try to run the Sfc /Scannow /OFFBOOTDIR=D:\    /OFFWINDIR=D\Windows command. Have you recently installed any new hardware or device driver or software before this boot issue started.

OK. Got the sfc /scannow/offbootdir=d:\ /offwindir=d:\windows to start, now I get the message "Windows Resource Protection could not start the repair service". This was after deleting the XML file on D: and attempting to run the Dism command. The Dism command gave me "Error: 2 Unable to access the image. Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder". I entered all commands exactly as referenced above with the exception of the last SFC command reference where it looks like you forgot a colon after the last D designation. Thoughts? Permissions issue on the D:Windows folder? Can I change that?


Edited by Cerberus262, 28 March 2016 - 12:58 PM.

  • 0

Advertisements


#11
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts

Can you paste or right here the output of the Bcdedit /enum | find "osdevice" command.

Are you running these commands from Windows Recovery Environment Command Prompt?

Yes i made a typo mistake and left out the colon for the D drive letter the correct command is Sfc /Scannow /OFFBOOTDIR=D:\    /OFFWINDIR=D:\Windows

Try to execute Dism  /Image:D:\  /Cleanup-Image  /RevertPendingActions command.

Execute Del /F /A D:\Windows\system32\codeintegrity\Bootcat.cache  command and then restart your computer.

Can you boot Windows 10 into Safe Mode.

You can boot Windows 10 into Safe Mode from the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.

Do you have Windows 10 Setup DVD if not then do you have access to Windows O/S running computer?

Have you change any setting within BIOS Setup Utility?

Have you recently install device driver or add new hardware to computer?

Execute Diskpart command and execute select disk 0 command and execute list volume command and if you can paste the output of list volume command to your next post.

Execute Exit command to exit Diskpart.

Execute Bootrec /FixMbr command, execute Bootrec /FixBoot command and execute Bootrec /RebuildBcd command.

Restart your computer to see Windows boots normally.

Make sure power and data cables of HDD is not loose also check other cables.

Scan RAM modules for errors with Memtest86+  software.


Edited by phillpower2, 29 March 2016 - 12:23 PM.
Deleted malware removal advice.

  • 0

#12
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

Data from first set of commands:

 

X:\windows\system32>bcdedit /enum |find "osdevice"
osdevice                partition=D:
 
X:\windows\system32>dism /image:d:\ /cleanup-image /revertpendingactions
 
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
 
 
Error: 1392
 
An error occurred accessing the temporary folder X:\windows\TEMP\C130E61B-4A48-4080-90F0-38E4685F1CD2.
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
 
-----------------------------------------------------
 
Here is a copy of the DISM log referenced above if that is helpful:
 
2016-03-28 20:22:35, Info                  DISM   PID=1272 TID=1276 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
2016-03-28 20:22:35, Info                  DISM   PID=1272 TID=1276 DismCore.dll version: 10.0.10586.0 - CDISMManager::FinalConstruct
2016-03-28 20:22:35, Info                  DISM   PID=1272 TID=1276 Successfully loaded the ImageSession at "X:\windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Manager: PID=1272 TID=1276 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: 
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: 
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.10586, Running architecture=amd64, Number of processors=4
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.10586.0
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Executing command line: dism  /image:d:\ /cleanup-image /revertpendingactions
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Loading Provider from location X:\windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Connecting to the provider located at X:\windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Loading Provider from location X:\windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Connecting to the provider located at X:\windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Loading Provider from location X:\windows\System32\Dism\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Connecting to the provider located at X:\windows\System32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Loading Provider from location X:\windows\System32\Dism\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Connecting to the provider located at X:\windows\System32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Loading Provider from location X:\windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Connecting to the provider located at X:\windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Loading Provider from location X:\windows\System32\Dism\FfuProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Connecting to the provider located at X:\windows\System32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
[1272] [0x80070002] FIOReadFileIntoBuffer:(1250): The system cannot find the file specified.
[1272] [0xc142011c] UnmarshallImageHandleFromDirectory:(793)
[1272] [0xc142011c] WIMGetMountedImageHandle:(3046)
2016-03-28 20:22:35, Info                  DISM   DISM WIM Provider: PID=1272 TID=1276 [d:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2016-03-28 20:22:35, Info                  DISM   DISM VHD Provider: PID=1272 TID=1276 [d:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Getting Provider VHDManager - CDISMProviderStore::GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM VHD Provider: PID=1272 TID=1276 [d:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2016-03-28 20:22:35, Info                  DISM   DISM Imaging Provider: PID=1272 TID=1276 The provider VHDManager does not support CreateDismImage on d:\ - CGenericImagingManager::CreateDismImage
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Getting Provider WimManager - CDISMProviderStore::GetProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
[1272] [0x80070002] FIOReadFileIntoBuffer:(1250): The system cannot find the file specified.
[1272] [0xc142011c] UnmarshallImageHandleFromDirectory:(793)
[1272] [0xc142011c] WIMGetMountedImageHandle:(3046)
2016-03-28 20:22:35, Info                  DISM   DISM WIM Provider: PID=1272 TID=1276 [d:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2016-03-28 20:22:35, Info                  DISM   DISM Imaging Provider: PID=1272 TID=1276 The provider WimManager does not support CreateDismImage on d:\ - CGenericImagingManager::CreateDismImage
2016-03-28 20:22:35, Info                  DISM   DISM Imaging Provider: PID=1272 TID=1276 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2016-03-28 20:22:35, Info                  DISM   DISM Manager: PID=1272 TID=1276 physical location path: d:\ - CDISMManager::CreateImageSession
2016-03-28 20:22:35, Info                  DISM   DISM Manager: PID=1272 TID=1276 Event name for current DISM session is Global\__?_Volume{6143ba6e-0000-0000-0000-500600000000}__3371616124_786432_93715 - CDISMManager::CheckSessionAndLock
2016-03-28 20:22:35, Info                  DISM   DISM Manager: PID=1272 TID=1276 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-28 20:22:35, Info                  DISM   DISM Manager: PID=1272 TID=1276 Copying DISM from "d:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2016-03-28 20:22:35, Error                 DISM   DISM Manager: PID=1272 TID=1276 Failed to copy the image provider store out of the image. - CDISMManager::CreateImageSessionFromLocation(hr:0x80070570)
2016-03-28 20:22:35, Error                 DISM   DISM.EXE: Could not load the image session. HRESULT=80070570
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: 
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2016-03-28 20:22:35, Info                  DISM   DISM.EXE: 
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2016-03-28 20:22:35, Info                  DISM   DISM Provider Store: PID=1272 TID=1276 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
 
-------------------------------------
 
Restarted, went through same loop to try to start, cannot boot into safe mode through the Advanced Options.
 
I do not have set up DVD (bought this copy of Win10 online) but I do have other Win10 computers.
 
No changes to BIOS or settings, no new hardware recently at all. Last addition was graphics card about 6 months ago.
 
Here is data from last set of commands:
 
D:\>diskpart
 
Microsoft DiskPart version 10.0.10586
 
Copyright © 1999-2013 Microsoft Corporation.
On computer: MININT-36H79H6
 
DISKPART> select disk 0
 
Disk 0 is now the selected disk.
 
DISKPART> list volume
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     E                       DVD-ROM         0 B  No Media
  Volume 1     C   System Rese  NTFS   Partition    100 MB  Healthy
  Volume 2     D                NTFS   Partition    111 GB  Healthy
  Volume 3     F   RESCUE DISC  FAT32  Removable   3826 MB  Healthy
 
DISKPART>
 
=======================================
 
D:\>bootrec /fixmbr
The operation completed successfully.
 
D:\>bootrec /fixboot
The operation completed successfully.
 
D:\>bootrec /rebuildbcd
Scanning all disks for Windows installations.
 
Please wait, since this may take a while...
 
Successfully scanned Windows installations.
Total identified Windows installations: 0
The operation completed successfully.
 
----------------------------------------------------------
 
Tried reboot, no success. Still goes through the same loop and I end up at the Advanced Options screen.
 
BTW - the F drive above is a USB drive I had plugged in to copy the logs onto.
 
Any other logs that might give a clue? It seems I can access anything on either the D: or X: drives...
 
Thanks for the help!

  • 0

#13
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,340 posts
Execute Sfc command from Windows 10 DVD you can create installation media with Windows 10 Media Creation Tool .
Can you explain to me how you cannot access anything on either the D: or X: partitions execute Dir D:\ command this should list content of the D:\ partition. There may be a chance that the hard disk drive is malfunctioning view health report and repair surface errors with your computer connected brand HDD Diagnostic Tool.

Edited by FreeBooter, 28 March 2016 - 09:33 PM.

  • 0

#14
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,784 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.

 


  • 0

#15
Cerberus262

Cerberus262

    Member

  • Topic Starter
  • Member
  • PipPip
  • 72 posts

This was a fresh installation of Win10 via online purchase on a new SSD drive. I'm assuming the C: and D: designations adjust while in the WinRE environment. D: is showing as the main drive with the Windows installation.

 

When it normally boots up, C: is the main drive. Of course none of the commands I am trying seem to be working. I tried running the commands from the Windows Media DVD choosing command prompt from the troubleshooting menu, but all commands give the same error messages I have been seeing...

 

I can see the D: drive and can access any files through command prompt. Any logs that might help in finding out the issue? I dread having to reinstall software on this computer - my boy will not be happy.


Edited by Cerberus262, 29 March 2016 - 08:12 PM.

  • 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