Windows 10: Windows 10 Recovery Tools - Bootable Rescue Disk

Hi
are you refereeing to this line of command?
> DISM /online /cleanup-image /restorehealth

answer is Yes/No
the DISM command is a new MS Tool that was created to analyse and do a lot of things.. must of them related to kernel. but it can validate other parts of the system to verify if everything is working according in what MS defined.
That command validates if the installed operating system is working in accordance with the active image (the current active version). If one of the tools finds a problem it will creates a log to make a possible solution...
Must of them is changing kernel and system files that were in a wrong version (ie.)
It will look in the active image (or other that we can pass by the option [/Source), and online and it will copy the necessary files to the proper place (an do their registration). if it verifies if a service or a polycy that is ofending the Ms rules it can change.

to be honest I never see the command change group policies, but I never do a very drastic changes in the rules...

another thing that I discover, is that sometimes we have to run the command "sfc /scannow" first...
because the above DISM line gives an error when it runs... generally after a bad update...
of course all this commands must be run with admin privileges....

alr tech said:

Hi kbird

Like I promise I do some tests with other PCs with different locals.. and for now it gives to me the same.
Date=09-01-2018
of course if someone doesn't like "-" it can change the char by "." or "_". Or even without any char linking the vars.
let's see other opinions...


:) well I'm working with 3 machines that didn't boot properly and the common recipes did not work...
one had a bad drive.... i retest several times but the HD is in it´s final life. And it was changed... but before that I had to retrieve the Win Keys and others, like files. its done.
the other it was a windows update that failed.. and the machine refuses too boot in windows only PE... chkdsk didn't help, common script didn't finished... I had to use other utilities, but this new machines with uefi bios left my normal utility pens no longer useful... but rufus make other utilities uefi compatible and yours ISO, and they did recover the disk.
The Win 10 pro was reinstalled, software and is almost done.
The third is a HP machine it took me several hours to disable the protection in eufi bios. Someone power off the machine when it was upgrading, they try late recover it.. but they do mistakes and they try to install a 8.1 recovery. So the win 10 became a mess and I try everything to recover, it failed.
I had to retrieve the keys, files search for virus and make a new installation. the problem is that this model doesn't have a HP win 10 support... its recent.. but the win 10 installed normally.. and I'm looking in HP for 2 win 10 drivers to use with similar HP models.. and I have to create a recovery with Macrium..
It's taking time but I only work with them when I arrive home...

With Kyhi, is with my findings in the ISO...
of course the pertinent conclusions will be post later

That is good news :) ALR Tech....at least about the script.....not so good with 3 failing machines....

You don't need Rufus anymore to make most bootable disks , simply format the USB PenDrive Fat32 ( and make it active if not using UEFI bios) then in Explorer right click the .iso file and choose Open with Explorer , and Explorer will Mount the .iso like a CD/DVD , you can then just copy all files (select all) to the PenDrive. On some computers you will need to disable Secureboot in the Bios to allow booting from a USB drive .

KB.

Hi Kbird
yes, but I hope that others test the script to see if it works for them...

all the computers are not mine, they belongs to friends....
the first is already with their owners....
the last two are waiting for me to have time to create a macrium recovery volume....
the HP is already HP done... but the SO is still with 1607 14393.2007 w10 version.... I don't know if its waiting from authorisation from MS to get the last upgrade... ?
the drivers I look with a more recent models from HP... and that incredible that MS have one or two with a more recent version...
yes, HP is a huge company they can pay for the certification ...

alr tech said:

Hi Kbird
yes, but I hope that others test the script to see if it works for them...

Yes I hope so to .....I am hoping nothing else has been "broken" by my changes , but at least it will give others using non-english verion of windows an option ....if they find it

all the computers are not mine, they belongs to friends....
the first is already with their owners....
the last two are waiting for me to have time to create a macrium recovery volume....
the HP is already HP done... but the SO is still with 1607 14393.2007 w10 version.... I don't know if its waiting from authorisation from MS to get the last upgrade... ?
the drivers I look with a more recent models from HP... and that incredible that MS have one or two with a more recent version...
yes, HP is a huge company they can pay for the certification ...

I had one computer get stuck on 1607 too and it failed upgrade 1609 over and over , I ended up doing a Fresh install with a 1609 .iso made with the MediaCreation Tool. It is a very old machine , probably not really ready for Win10 , it is actually Dual booted with XP as I need XP to run some very old Software a few times a month.

KB.

Hi Kbird

Kbird said:

.... I am hoping nothing else has been "broken" by my changes...

I look to the script, and as I see you just modify the code to calculate date and send it to a variable... and later change the original var for the output... so it will create the iso... but lots of people change the conditions to the local... so a new error will appear....
If someone wants something like this Jan2018... well it can be done with more code, etc.....
but for me this is a simple tool to help building the iso... everyone can modify easily the name of the file after...

in the "old days" it was easy for me to create dual boots, then virtualization came along and I left the dual booting...
but this new uefi bios came, win 10 with all the changes... and again a way to make a easy rebuild of a trashed W10 installation became a priority...
thats why I land here ...
I have a few other questions that I will put in others places in the forum...

alr tech said:

Hi Kbird

I look to the script, and as I see you just modify the code to calculate date and send it to a variable... and later change the original var for the output... so it will create the iso... but lots of people change the conditions to the local... so a new error will appear....
If someone wants something like this Jan2018... well it can be done with more code, etc.....
but for me this is a simple tool to help building the iso... everyone can modify easily the name of the file after...

That's right , I just added the code at the top of the script and REM'd out the existing set %DTStamp% statements , giving my variables new names makes it easier to alter the script as you need eg a UK or US version , and so, it is pretty easy for anyone to change or fix. I added comments as well, so people can see what to do in the File... you seem to know what you are doing anyway though.

If you wanted 12-Jan-18 as the date , you could just use %date% in the Filename , instead of the variable %dtstamp% assuming your Windows Short Date is set to dd-MMM-yy. The number of letters = the number of letters output eg M=1 MM = 01 MMM = JAN and MMMM= January etc. dd-mm-yy would be 12-01-18 for today as another example.

It isn't obvious in the WIn10 that you don't have to accept the selections they give you in Settings , you can type in your own such as above in any combination and what you will get for %date% will be what you see by the Clock on the Taskbar. You can't write your own in Settings though....it just reflects what is in the Regional Settings in Control Panel....and you have to goto additional settings to write your own their too.

Whatever server is hosting these files has to be the slowest I've ever seen.Over an hour to download a 1.2GB file? And I'm on a gigabit connection.

422 KB/s - 127 MB of 1.2 GB, 45 mins left

Hi,

First time poster here, with a terribly noobish question - but I can't find the answer anywhere else.
I'm using the wonderful PE rescue disk to try and overcome a windows 10 boot loop problem (error code from Srt id >0x82f).

But when using the command prompt, I can't get to the C: drive to use scannow, DISM, SrtTrail etc. The prompt opens with X:\windows\system32, when I enter a cd command to reach C: it never works: whatever I typed in as command appears on the screen but then the X:\... prompt appears again.

Sorry if this is the wrong place to ask this, but I'm desperate (it's the third day I've been trying to solve the problem - a complete reinstall will probably be necessary but I want to exhaust all the options first).

Many thanks for any help you can offer.

What happens when you type:

Code:

C: <enter>

<enter> is the actual keystroke

Hi
sorry for the question, but did you test the partitions of the disk where the c: drive is?