New
#1241
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
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.
If you use cd /d that changes the drive as well as the directory, so if you are on X: and want to be on a directory on the C: drive you could use
cd /d c:\windows\system32
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.
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.
Not sure if message coming from your PC or PE
But the message refers to Ram Disk Drive
Which is drive X (Memory)
This version of PE is loaded in Memory.. aka > Ram Disk
So how mush Memory does the PC Have???