New Macrium Reflect Updates [2]

IronZorg89 said:

Sorry to say that I always have a cursor on that screen. Maybe the issue doesn't have anything to do with Macrium Reflect and the best way to find out as @magilla suggested is to see what happens without MR boot option.

Yes, I also always have cursor and timer with and without Macrium-all machines, laptop and desktop, have cursor and timer but all are also dual or triple boot computers.

Bree said:

but the moment I move the cursor the timer will stop and disappear (though not the cursor).

yes, same here.

Fabler2 said:

The timer disappears once I move the mouse. Without the Macrium boot option I have the mouse pointer on Lock screen.

I'll try the keyboard next time as kado897 kindly suggested

As I mentioned earlier without the Macrium boot loader the mouse pointer works ok on the lock screen. With Macriums boot loader enabled I booted to Macrium's recovery and just for the heck of it repaired Windows boot. Guess what? It got rid of itself

Fabler2 said:

As I mentioned earlier without the Macrium boot loader the mouse pointer works ok on the lock screen. With Macriums boot loader enabled I booted to Macrium's recovery and just for the heck of it repaired Windows boot. Guess what? It got rid of itself

Yes, it will do that. Not a bug. The Boot Repair only looks for Windows OS partitions, then rebuilds the BCDBOOT data. Need to do the Macrium "add boot entry" again. It's perfectly normal.

f14tomcat said:

Yes, it will do that. Not a bug. The Boot Repair only looks for Windows OS partitions, then rebuilds the BCDBOOT data. Need to do the Macrium "add boot entry" again. It's perfectly normal.

Thanks for that. So I presume that if dual booting, both Windows, then Macrium would repair both boot loaders if one got corrupted?

Fabler2 said:

Thanks for that. So I presume that if dual booting, both Windows, then Macrium would repair both boot loaders if one got corrupted?

Been a while since I ran it, but as I recall it will re do the entire BCDBOOT data. On the Boot Manager screen, you would see something like:

Windows 10 on Partition 3

Windows 10 on Partition 5

and the Macrium boot entry, if you've done the "add boot entry".

The displayed names can be easily changed with EasyBCD app, or with a command line:

bcdedit /set {current} description "Windows 10 RTM Spring Update"

Be booted to the OS you want to change, and replace the words in bold with whatever you like.

It will be effective immediately and can be checked with the MSCONFIG command in the BOOT tab.

f14tomcat said:

Been a while since I ran it, but as I recall it will re do the entire BCDBOOT data. On the Boot Manager screen, you would see something like:

Windows 10 on Partition 3

Windows 10 on Partition 5

and the Macrium boot entry, if you've done the "add boot entry".

The displayed names can be easily changed with EasyBCD app, or with a command line:

bcdedit /set {current} description "Windows 10 RTM Spring Update"

Be booted to the OS you want to change, and replace the words in bold with whatever you like.

It will be effective immediately and can be checked with the MSCONFIG command in the BOOT tab.

Again thanks for that. The last time I dual booted was with Vista and XP so I've forgotten how-to never mind being rusty Surprised to find that EasyBCD is sill free to use for the home user.

Fabler2 said:

As I mentioned earlier without the Macrium boot loader the mouse pointer works ok on the lock screen. With Macriums boot loader enabled I booted to Macrium's recovery and just for the heck of it repaired Windows boot. Guess what? It got rid of itself

That's only logical. Macrium can't detect virtual or RAM disk based installations.

When you use Macrium Reflect to fix Windows boot issues, it looks for installed Windows operating systems on internal hard disks. It simply can't find any Windows installations on virtual hard disks or RAM disks.

In my case, I have seven boot menu entries: EN-GB English Windows 10 as my main OS with Hypervisor enabled to be able to run Hyper-V virtual machines installed on physical SSD, same OS copied to another boot menu entry with Hypervisor disabled to be able to run VMware and VirtualBox virtual machines, then the same OS in Finnish, Swedish and German installed on native boot virtual hard disks, my personal, custom recovery image which I update after every Insider build upgrade, and Macrium recovery environment:



(Boot menu only shows six entries, to boot to 7th, Macrium, I need first click See more operating systems.)

Only two of these are physical installations, the main OS with Hypervisor, and the same without Hypervisor. However, when Macrium checks installed operating systems to fix boot issues, it cannot detect the No Hypervisor boot menu entry because, in fact, it is the same than main OS, just with other settings. It can also not detect my Finnish, Swedish and German Windows 10, because they are installed on virtual hard disks. And, finally, it can't detect my custom recovery boot and Macrium boot menu entries.

If I need to fix Windows boot menu issues, only my main OS will be found, and after booting to it, I must recreate entries for all operating systems installed on virtual hard disks, recovery partition, and Macrium.



This is just how it works.

   Tip

To get screenshots or capture video of Windows Setup, boot menu, OOBE and so on, launch your Macrium Reflect image in Macrium viBoot. Screenshots in this post are from a Reflect image my system automatically creates every night, run as a virtual machine.

Ten Forums viBoot tutorial: Macrium viBoot - Create Virtual Machine using Macrium Image

Kari

Kari said:

That's only logical. Macrium can't detect virtual or RAM disk based installations.

When you use Macrium Reflect to fix Windows boot issues, it looks for installed Windows operating systems on internal hard disks. It simply can't find any Windows installations on virtual hard disks or RAM disks.

In my case, I have seven boot menu entries: EN-GB English Windows 10 as my main OS with Hypervisor enabled to be able to run Hyper-V virtual machines installed on physical SSD, same OS copied to another boot menu entry with Hypervisor disabled to be able to run VMware and VirtualBox virtual machines, then the same OS in Finnish, Swedish and German installed on native boot virtual hard disks, my personal, custom recovery image which I update after every Insider build upgrade, and Macrium recovery environment:



(Boot menu only shows six entries, to boot to 7th, Macrium, I need first click See more operating systems.)

Only two of these are physical installations, the main OS with Hypervisor, and the same without Hypervisor. However, when Macrium checks installed operating systems to fix boot issues, it cannot detect the No Hypervisor boot menu entry because, in fact, it is the same than main OS, just with other settings. It can also not detect my Finnish, Swedish and German Windows 10, because they are installed on virtual hard disks. And, finally, it can't detect my custom recovery boot and Macrium boot menu entries.

If I need to fix Windows boot menu issues, only my main OS will be found, and after booting to it, I must recreate entries for all operating systems installed on virtual hard disks, recovery partition, and Macrium.



This is just how it works.

   Tip

To get screenshots or capture video of Windows Setup, boot menu, OOBE and so on, launch your Macrium Reflect image in Macrium viBoot. Screenshots in this post are from a Reflect image my system automatically creates every night, run as a virtual machine.

Ten Forums viBoot tutorial: Macrium viBoot - Create Virtual Machine using Macrium Image

Kari

Thanks for the explanation. Very interesting.