Windows 10 Recovery Tools - Bootable Rescue Disk

SIW2 said:

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"

Is it required that the install.wim image is mounted before attempting to use the /Restorehealth argument?

Not required in theory, but I have heard it is more likely to be successful. It only takes a minute to mount, why is it a big deal?

I use ModifyWinPESE.cmd and selected option 3 To Modify or Capture the WinPESE X64 Boot.wim
It Created folder Extracted-WimImage_x64

I then opened a new administrative command window and typed the following command
dism /image:Extracted-WimImage_x64 /add-driver /driver:c:\drivers /recurse

that command updated 44 drivers

I went back to the ModifyWinPESE.cmd window and selected again Option 3 To Modify or Capture the WinPESE X64 Boot.wim

Then I got the following Error:

[WARNING] "C:\Users\mtdew\Desktop\Tools\modify-winpese_17.01.25\Modify-WinPESE\Winpese_x64\Sources\Boot.wim" does not contain integrity information. Skipping integrity check.Scanning "C:\Users\mtdew\Desktop\Tools\modify-winpese_17.01.25\Modify-WinPESE\Extracted-WimImage_x64"5792 MiB scanned (17770 files, 2346 directories)Using image 1 from "C:\Users\mtdew\Desktop\Tools\modify-winpese_17.01.25\Modify-WinPESE\Winpese_x64\Sources\Boot.wim" as templateUsing LZX compression with 8 threads[ERROR] A file was concurrently modified!(3%) done Path: "\??\C:\Users\mtdew\Desktop\Tools\modify-winpese_17.01.25\Modify-WinPESE\Extracted-WimImage_x64\Users\Default\NTUSER.DAT" Expected SHA-1: 16f0786448c58e58a0015e01100e3439bcdfb9dc Actual SHA-1: 319b57c81adeb281317973a3ddfe4ef48fa3128dERROR: Exiting with error code 88: A file being added to a WIM image was concurrently modified. 1 file(s) copied.===============================================================================Press Any Key To Return To Menu

Several files in the extracted X86 boot disk are classified as virus by norton and removed

SIW2 said:

Not required in theory, but I have heard it is more likely to be successful. It only takes a minute to mount, why is it a big deal?

Who said it was a big deal? haha

I was just curious because I noticed Microsoft docs reference a syntax similar to yours -- Dism /Image:C:\offline /Cleanup-Image /RestoreHealth /Source:C:\test\mount\windows

Yet they omitted the part about mounting the image prior. But looking @ the syntax, it would seem that is the expectation.

Does the Recovery Tools ISO (winpese-x64-14393_17.01.16.iso) work with the Windows 10 Creators Edition (1709), or is there an updated ISO? I couldn't find one by searching.

thoatswold said:

Does the Recovery Tools ISO (winpese-x64-14393_17.01.16.iso) work with the Windows 10 Creators Edition (1709), or is there an updated ISO? I couldn't find one by searching.

It works with any version (or in fact no Windows installed at all).

I used it to fix 1709 issue a couple of weeks ago.

Great little rescue key, this one. Works a treat... except on my new Dell Optiplex 7050 MT desktops.

When I try to boot I get this blue screen:



There’s nothing wrong with the key – It works on every other device I’ve tried it on including my two XPS 13s. Just the 7050s that don’t like it.

Any ideas?

Tolqua.