Windows 10: Windows 10 Recovery Tools - Bootable Rescue Disk
I think the Bug from reading is in WinPE .240 from M$ that Macrium uses to build it's Rescue disk , so I am not sure if it is just Effecting MR .1366 or earlier version too as .240 is likely 6 months old but M$ may not have updated it yet.
My netbook was clean installed as it came with XP , which I had upgraded to win7, it was stuck on Win10.240 after the upgrade so I clean installed .420 a few weeks ago. It is only a Atom Chip so not high performance , and imagine any new laptop should be it's equal at least.
Thanks for information, interesting. The atom processor that rings a bell, did the netbook also have 'odd screen' resolution, something like 1024x600?
I will show my ignorance, what is the 240, is that build number for WinPE?
Well my confusion is increasing, to the unbelievable so I am struggling a lot to keep level head and logic. Here are some points.
1.. Downloaded windows 10 x86 ISO from a MS download site, have the record somewhere, fine
2.. Formatted a 32 GB USB stick FAT32 just to be on the safe side
3.. Window Explore shows empty drive/partition, I leave that window open.
4.. Using 7zip I extracted the ISO content directly to the newly formatted drive, takes some time
5.. As far as I can tell the directory structure looks right
6.. Removing the stick, place it in the USB2 (right hand side) port of the ASUS TP200SA when power off
7.. Holding down Esc key and turn power on, holding down Esc until first (dim) Asus logo shows.
8.. The UEFI boot manager shows 3 options, roughly as, a bit more specific, but selecting UEFI seems to be correct
a.. Windows 10
b.. UEFI: USB 2
9.. My problem is very quickly the Boot Manager shows again and if I select UEFI again eventually Win10 wil start.
If I repeat the same action using my Macrium Repair stick, the extremely slim, WinPE will open Macrium recovery window. This works.
What am I doing wrong? I think I am missing something in the boot process, the old BIOS/MBR I understand but UEFI is black art for me at the moment.
It gets even better, I also downloaded Win10x86PESE iso, the same thing happens, using the same stick!! I have repated this several times using two different sticks but I am starting to loose memory of which doing what.
Is there any log that be turned on or hidden somewhere I can use.
So very sorry for your loss Kyhi, deepest sympathies, to you and your family.
Scorched CPU Theory
You have my sympathies Jimmy.
It's nice you had a chance to tell him, that you loved him one last time, before his passing, I didn't have that chance.
Yes I think that is the resolution on the Netbook actually, uses the Intel Chip.
Both WinPE and Win10 have version numbers , in Win 10 .240 is about 6 months ago, win10 is now .494 as of Tuesday's Update cycle,
but reading at Macrium's Forums seems to indicate WinPe 10 is still at .240
a.) is the standard Boot to Win10
b.) and c.) are the same thing , b.) is UEFI boot , c.) MBR boot
B.) should work but if not cos Bios is not in UEFI mode then it should immediately reboot and you can choose c.) which should work , if not then the USB isn't being recognized as bootable . It may not be the WinPe you built , it maybe the Key , I have several Verbatim USB3 keys that work fine except if I try to boot them from a USB 2 port ..they aren't seen, so try another key too.
let's find out your current disk layout..
From command prompt (admin) type
select disk 0
post a pic of cmd window results..
PS with the setup media 0 if you are setting up a UEFI PC then you would select uefi:usb2 from the boot menu, to boot the USB Stick Media in uefi mode (USB has to be FAT32 Format)
Atom processors will only boot x86 UEFI , not x64 UEFI
If you have an x64 OS installed now, then it is legacy mode..
So, what I am saying is you have an x64 supportted PC, booting x86 UEFI software... Or that is how that usually works with ATOM cpu's, that is also how it handles just 2GB Ram
Some atom devices do boot 64bit UEFI but most are 32bit UEFI. On many devices, they can only boot in UEFI especially 32bit UEFI as they do not have legacy bios support.
Sorry I brought a bit of confusion into play here but thanks for the information on the Atom based pc's. I do have an Atom based pc but this is not the one I am working on at present.
The one I am having problem with is Asus TP200SA, and it has an Intel® Pentium® Processor, not sure what difference this makes. Some progress made as I discovered that I have had boot confusion and formating wrong, the last I still don't understand but will put it down to my mistakes. I got in my mind that all sticks I was using was formatted FAT32 but one of them had become NTFS, unfortunately it "half" boots.
When I got that cleared up I can now boot up a win10 x86 'properly' but have yet to intsall it properly (x64 also, this is installed, the boot stick made from an *.esd copy)
From memory both of these booted up using uefi:....., need to recheck this later because getting a bit desperate I jumped in with both feet and downloaded the WinPE Builder from "the oven" by the time I stumbled accross that forum I knew enough to understand a bit of the process. In reality I am not sure about my knowledge but by carefull reading when I had downloaded and started up, my impression was that if I just pointed to the source of an install ISO, closed my eyes and hit the Play button I might get a slimmed down version of Win10PESE.
Well because the x64 was a success I repeated with x86 and that was also a success as far as generating Win10PESE-ISO file. When it came to using them I was so set on that I needed to boot UEFI: option, several times I did that no go, while pondering my defeat I decided to try BIOS/MBR and that was when I got my big surprise. Win10PESE-x86 was workable, in a fashion there are errors coming up but it is working.
Past midgnight I made a quick dash, copied the Macrium install directory to a USB stick and inserted the stick in the Asus and just hit Reflect.exe and it started on Asus TP200SA but no keyboard and touchpad. I did not go any further as I think this was too far out, I should have installed Macrium in the PE system but it was another big download to get another PE-base, something does not sund right.
Anyway, this morning I have extracted the Win10PESE-x64, that I made, to a boot stick. Tested it out, again booting BIOS/MBR option, it has installed.
Since neither of my home made PE systems have Macrium installed, my next step is to check why I did not have success with Kyhi's files, Macrium already built in, in post number 1. It may have been I was stuck in the groove of just using UEFI: because this is what the Macrium Repair stick uses.
The good news
When I posted initial part of this, Win10PEKyhi-x86 has just about finished copying to the USB stick. Booting it on the Asus TP200SA was a bit of an anitclimax as when selecting BIOS/MBR boot option, it started straight away.
1.. Few minutes later had Macrium running but this does not have touchpad/keyboard working either.
2.. Networking is not running, when using trouble shooting: Not finding x:\windows\system32\msdt.exe
3.. Same message in Win10PEHandy-x86 but I could fill in WiFi setup and it worked despite saying network was not connected.
Just run the Win10PEKyhi-x64, the message is:
or similar, it is very small writing, it is back to the x86 for the time being.
not enough RAM to create system.
Last edited by handy2209; 15 Jul 2016 at 07:58.
First. My deepest sympathies are with you and your family Kyhi. I could literally feel your heartbreaking reading through the thread.
I am currently on the previous build: WinPESE_x64 20160125
I was reluctant to download the newer version if the Aug. 2016 Anniversary update is just going to bring signifacant changes again in 2 weeks? Bandwidth issues seem to be a recurring theme ITT.
I had to google FSCapture to find out about it: features / use / how-to
Solid reputation and fanbase, feature rich. (still asking myself whether personally would use those features?)
I was almost going to download and try the portable version until I read this:
I plan to testdrive FSCapture thoroughly next time I'm in WinPESE
RE: Macrium. As long as I can image and restore free version images, that's the only thing I'm worried about personally.
(which seems to be the case)
Has anyone got the current version of MBAM to update and run properly on WinPESE?
Are there any negatives to using F8 at boot.
Do you lose any advanced boot options?
Do you always have to choose the boot device?
EDIT: Found my answer here: Windows 10 instructional videos by Ten Forums members
As someone who has read through all 18 pages of this thread, learning, googling, re-reading, bookmarking, etc.
It seems like the recurring topic is dead links, bandwidth, and distribution methods.
Are torrent links totally prohibited on the forums? Seems to me a torrent would be perfect distribution method for users to be able to choose from. Users w/o a torrent client installed could still choose to use the bandwidth from the direct-download links.
PRO: One main directory, with sub-directories to pick and choose features from.
Is anyone else unable to view, or download Kyhi's image attachments?
His images and downloads work fine in the main applications posts. But attachments throughout the thread bring up the above.
Anyways. Just wanted to say Thank You to Kyhi, and all the others who have contributed to this project and posted in the thread.
Last edited by seedless; 16 Jul 2016 at 10:24.
You have my deepest sympathies Kyhi. I went through something very similar with my Dad a few years ago. What you did was a very good thing, but difficult. But, you will never be sorry you did it.
Have a new Double Power 8.1 Tablet that I've upgraded to Win 10. Now I've got it set up just right, I'm attempting to create a Rescue Disk. Purchased a 16gb micro-usb drive which is successfully recognized. Ran 'Create Rescue Disk' from Windows...
Does anyone know how this software can be configured to boot from usb on uefi/gpt.
I formatted usb using rufus on the relevant mode then dragged over the contents of another usb where it does work on bios/mbr set up.
But when booting...
I have a new laptop with win 7 pro installed. Once Win 10 is installed in July how will I be able to create a system restore disk?
Just sharing this.
I made another boo-boo today and deleted 500GB worth of media files (just movies and music). Don't ask me how because that's something nobody wants to do. :)
I don't keep a backup of these files. For me these are disposable...