[tanGee]

I'm trying to get my Dad's laptop back to a bootable state for him after it started booting to a black screen with a flickering white box that was almost impossible to see before it flashed away again. I was able to catch it at one point and it was "Interactive logon process initialization has failed.".

 

I booted into the recovery environment by power cycling at the windows logo a few times, and tried to run both 

 

sfc /scannow

 

and

 

dism /Image:C:\ /ScratchDir:C:\ /Cleanup-Image /RestoreHealth /Source:\install.wim

 

Note that C:\ is the directory containing the Windows installation that won't boot, and D:\ is a USB drive containing install.wim.

 

Both commands get so far, before erroring, CBS.log and DISM.log attached.

 

I've also tried:

 

- sfc /scannow /offbootdir=c:\ /offwindir=c:\Windows (this failed instantly, with the message "Windows Resource Protection could not perform the requested operation."

- SFCFix (from https://www.sysnative.com).(this instantly failed with "This version of D:\SFCFix.exe is not compatible with the version of Windows you're running."

 

Thanks in advance for any help or advice anyone may be able to offer!

Attached Files

•  CBS.log   601.22KB   408 downloads
•  dism.log   46.11KB   425 downloads

[Advertisements]

When you are using both Dism and Sfc tools offline from windows recovery environment they will not able to create logs.
 
Make sure C: partition where Windows is where installed.


Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

The following command scans integrity of all protected Windows system files and repairs files with problems when possible.

Sfc  /Scannow   /OFFBOOTDIR=D:\   /OFFWINDIR=D:\Windows

Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (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 have not included /LimitAccess parameter and have not included image number please visit below link for more information.


https://www.dost-tec....php?f=10&t=150

[FreeBooter]

When you are using both Dism and Sfc tools offline from windows recovery environment they will not able to create logs.
 
Make sure C: partition where Windows is where installed.


Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

The following command scans integrity of all protected Windows system files and repairs files with problems when possible.

Sfc  /Scannow   /OFFBOOTDIR=D:\   /OFFWINDIR=D:\Windows

Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (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 have not included /LimitAccess parameter and have not included image number please visit below link for more information.


https://www.dost-tec....php?f=10&t=150

[tanGee]

FreeBooter,

 

Thanks for the reply. I'll try the steps you've mentioned when I get home. I just wanted to check, will performing the SFC check from setup media's recovery environment be any different to running it from the recovery environment of the current OS installation? I've already done that, and when I did, the OS (Windows directory) was definitely on C:\.

 

However running sfc /scannow /offbootdir=c:\ /offwindir=c:\Windows failed instantly, with the message "Windows Resource Protection could not perform the requested operation."

[FreeBooter]

The SFC tool will repair files same way if it was run from online Windows OS.