I will then boot it and test by browsing a Macrium Image file. My practice is to create a new Rescue USB with each new update of Macrium, thereby combining the latest versions of Windows RE and Macrium Reflect on the same bootable medium. If there is a problem with creating rescue media, you can always start over. In answer to your last question, pages 9 and 10 of the PDF mention Custom base WIM, as being beyond the scope of the casual user.
Regarding the choice of RE/PE version for your context, I would say go with the default of Windows RE as recommended, if available. If a boot menu is present when you run a Create Rescue Media step the remove choice will be offered. Question: PDF didn’t say if you can edit a Rescue Media USB in the future and if not work after testing it. Should I follow/pick the PE mentioned in the 1st Note box something about with Win7 & to enable USB 3.0 port in Rescue build pick this PE? So, In Advanced settings, whi how Win PE option is best for my case ? Soo, since I am forced to move back to Win 10 Pro (Adobe programs not supported anymore) and I should create a Bootable Rescue USB for my Win 7 Pro. I have a custom built PC that had Win7 enterprise (but repair shop couldn’t clone HD & HD not useable) so Win 10 Pro was installed but I took it back days later to downgrade to Win 7 Pro.
Question: On of Rescue Media PDF, about Win PE version options in Advanced Settings. A good thing to know…How I do remove it ? Question: I saw a post here saying didn’t like having boot menu as part of PC’s boot up/start up process and removed it. What I understood of pdf guide: selecting USB as my target device is the way the boot menu window will only appear when I plug in the USB I’ll need to go through process again to create a Bootable Rescue USB, right? What I understood of pdf guide: If want to add a boot menu window which includes WinPE every time I turn on PC I’ll need to pick Windows to continue the Windows start up/boot up like how use to. Have a few questions and confirmations if I understood correctly.
0 kommentar(er)
