Windows 10: Adding Windows Boot Menu Via Macrium Rescue Media Builder

I'm familiar with what selecting this option does in BIOS Firmware but I wondering what it does on a UEFI Firmware PC. Does it actually add another boot item that's accessible from the boot section of the firmware? I find this option handy in the BIOS Firmware world but I'm wondering if it works the same way in the UEFI world. I'd rather not make any changes that I can't easily undo since I have my UEFI training wheel on at this point.

:)

 

Use Macrium Reflect Rescue Media to Fix Windows Boot Issues  

A really good question deserving a bit more in-depth answer. A short answer is it makes restoring boot menu on a dual / multi boot system a piece of cake, one simple command to restore it as it was instead of manually adding / changing everything.

Let's use my actual boot menu as an example:




The easy way to restore my boot menu when I have been forced to reset boot records with Macrium Reflect is to restore a boot menu backup as told in tutorial (Part 1. to export / backup boot menu, Part 3. to restore it). One command to restore it fully:

In Command Prompt:

bcdedit /import X:\BootMenuBackup

Or in PowerShell:

cmd /c 'bcdedit /import X:\BootMenuBackup'

If I hadn't exported boot menu, I had to restore it manually:



(Click screenshot to enlarge.)

1. Add Windows 10 Education on physical drive W: to boot menu
2. Change its name (as shown in boot menu) to W10 EDU
   
3. Add Windows 10 PRO on a mounted virtual hard disk file (drive I: when mounted) to boot menu
4. Change its name to W10 PRO (VHD)
   
5. Change current OS boot menu entry name to W10 PRO (Hyper-V)
   
6. Copy the current OS boot menu entry to new entry W10 PRO (VMware)
   
7. Disable hypervisor in the copied new entry to allow running VMware on same machine and installation already running Hyper-V
8. Make current OS (my main OS, W10 PRO with hypervisor) default entry in boot menu, the one booted if user selects no OS within given time (by default 30 seconds)
9. Set boot menu display order. To do that I open another PowerShell / Command Prompt to list all boot menu entries with simple bcdedit command to get and copy identifiers of all added operating systems. Last OS added is by default always {default}, current OS you are using is {current}, all other entries are identified with their hexadecimal GUID

Not shown in screenshot: between steps 8. and 9. I launched Macrium Reflect to add Macrium Rescue environment as fifth entry to boot menu.

Notice that in steps 2. and 4. I used the same identifier {default} for two different operating systems when changing entry name. This is possible because by default the last OS added to boot menu gets identifier {default}; adding W:\Windows in step 1. made it default, then adding I:\Windows in step 3. made it default.

Exporting boot menu when it is as you prefer, then importing it with one command when need arises is much faster and easier.

I hope the above answers your question.

 

Use Macrium Reflect Rescue Media to Fix Windows Boot Issues  

Thanks, @Kari! Yes, it does, and very nicely laid out. For me, would save the hassle of the renaming of the OS names. Otherwise, you need a cheat sheet to know what "Windows 10 (on partition 6)" means.

Slightly OT....how did you get such a nice pic of your Boot Manager screen without a camera?

my ugly one:

 

Macrium Boot Question

Macrium Boot Question

I use Windows 10 and a Macrium recovery program. My BIOS is set where the optical disk for CDs and DVDs are not set to recognize a CD/DVD disc as the first priority to boot from.

What are the steps I should take to make my Macrium Rescue Disk as being first to boot from?

Thanks,

Jerry