Windows 10 Recovery Tools - Bootable Rescue Disk

I've been trying to perform sfc, dism, chkdsk... Though it's probably the OS that is damaged. I've been trying to get at the original windows 10 installation, to see if I can determine where the error (0x82f) is to be found. But that hasn't been possible. The SrtTrail.txt states that a recently maintained (? translating from Dutch, here) binary start-up element has been damaged (part of an update in progress, apparently).

I've entered the command you provided, but it also didn't work, gave me error 2.

I've used this PE to get into my PC stuck in boot loop in order to see if things are fixable. I've been able to get out all my files and media, so that's good. I haven't mounted any C:-drive image, though, just tried to access the installation that's on my hard drives to discover whether anything is fixable. But that's probably not the case...

mrswing said:

I've been trying to perform sfc, dism, chkdsk... Though it's probably the OS that is damaged. .

Can you make a new thread in the "General Support" forum called "Help with DISM" or "Can't fix bootloop" or something like that (whatever the error is now).

This thread is for the Rescue Disk and we'll sidetrack it if we aren't careful.

p.s. everything is fixable - just sometimes reinstalling is quicker and easier :)

Will do. Thanks for your help. The only thing that still isn't clear to me is how the PE apps and commands can be made to 'reach' the original windows installation.

Thanks for the PM - I responded but am not yet allowed to send PMs as I just joined today!

Hi
This line of code try to access the dir on c: but tell the tool to use the image on X drive (the drive were is the installation media).
the /online option doesn't work in PE environment, so you have to try to access the image in c:\windows...
verify if the install.wim is the same that you use with your installation.. Otherwise try to use your wim file in your installation...

lx07 said:

code]dism /image:c:\ /cleanup-image /restorehealth /source:wim:X:\sources\install.wim:1[/code]

I don't know how to do a validation of the wim file in a offline instalation...

this line is use to do the validation using SFC

Code:

  sfc /scannow /offbootdir=L:\ /offwindir=L:\Windows\

attention : change L by C if is the drive were your Windows instalation reside..

Windows has been assigned C. But what I don't understand is how to access the offline image...

mrswing said:

Windows has been assigned C. But what I don't understand is how to access the offline image...

What do you mean "access it"? You already have.

If you know it is been assigned C then not only can you access it but you already know you have or you wouldn't even know the mount point was C rather than D or E or whatever. What do you want to do with this image? Make it boot? Repair it? Copy data from it? Install something to it?

When you boot PE it will assign itself X letter for its volume. It will then look around and apply drive letters to what it can based on some criteria. You say your 'normal windows' "C" drive has been assigned letter "C". OK - this is common but certainly not inevitable. Assuming this is the case then that is your answer - you have succeeded.

You need to say (ideally in another thread) what you want to do. Speculative discussion of how PE works is pointless.

mrswing said:

The only thing that still isn't clear to me is how the PE apps and commands can be made to 'reach' the original windows installation.

If your image is D:\sources\install.wim then mount it using the following command from within PE:
"DISM.exe /mount-Image /ImageFile:d:\sources\install.wim /index:1 /mountdir:C:\mount"
Then:
"DISM.exe /Image:WindowsDriveletterhere:\ /Cleanup-image /Restorehealth /Source:c:\mount\windows /LimitAccess"

Can one use a newer Windows version/build image to repair an older one? Or does the image have to be a perfect match?

For example, if the PC needing repair has Win10 ver. 1607. Can I use a Win10 1709 image to repair it via dism?

Thnx...