Macrium Reflect 8 Update Discussion

Every time there`s been a patch, there`s always an update to the Rescue Media.

Caledon Ken said:

Don't think he said he had to restart OS.

just he had to restart.

Ya Macrium just restarts, totally normal unless you uncheck the boxes.

I leave them checked to make sure Macrium opens and works properly after a patch.

OldMike65 said:

Yep and I only do Full backups

Same here, I do a full backup before installing the LCU.

kado897 said:

It goes by build number, not the changes in the build, so it always offers to create new rescue media.

If that is the case, I don't think it used to do that in 7.

It certainly has a new reflectbin.exe binary dated 5/30 for the recovery boot. The boot executable is also build 5145. Seems more legible to me.

Hopachi said:

Interesting test.
Slower but still good to have it as alternative.

A couple of notes:

I assume current OS stands for Win10.
Hyper-V 'knows' it best. That's boldly said the main reason it works better. Being type 1 hypervisor is indeed a thing AND it includes all guest tools/services already on that guest.

I've put my current Win10 in a VM a couple of times so far.
In Hyper-V it always feels snappy even on i3 CPU.

On QEMU/KVM it works better after installing the win-virtio drivers and on VirtualBox you need to install the guest additions for a fair test; Hyper-V includes all additions/tools/services for Win10 already giving it the edge for a Win8.1 / Win10 / Server 2016/2019+ VM.

I went on to Macrium Forum and they recommend turning off the HyperV Hypervisor as to run VM with Hypervisor works but is slow. Turning ot off made a big difference. Still a bit slow compared with HyperV but not too bad.

I will try installing guest additions.

cereberus said:

I went on to Macrium Forum and they recommend turning off the HyperV Hypervisor as to run VM with Hypervisor works but is slow. Turning ot off made a big difference. Still a bit slow compared with HyperV but not too bad.

I will try installing guest additions.

So it was a case of concurrently running VirtualBox with Hyper-V turned on...
At least it worked... This is also getting better so it seems.

But good thing you sorted that out.

Additions will improve it, the graphics alone should give it a boost in screen 'movement'.

Hopachi said:

Interesting test.
Slower but still good to have it as alternative.

A couple of notes:

I assume current OS stands for Win10.
Hyper-V 'knows' it best. That's boldly said the main reason it works better. Being type 1 hypervisor is indeed a thing AND it includes all guest tools/services already on that guest.

I've put my current Win10 in a VM a couple of times so far.
In Hyper-V it always feels snappy even on i3 CPU.

On QEMU/KVM it works better after installing the win-virtio drivers and on VirtualBox you need to install the guest additions for a fair test; Hyper-V includes all additions/tools/services for Win10 already giving it the edge for a Win8.1 / Win10 / Server 2016/2019+ VM.

cereberus said:

I went on to Macrium Forum and they recommend turning off the HyperV Hypervisor as to run VM with Hypervisor works but is slow. Turning ot off made a big difference. Still a bit slow compared with HyperV but not too bad.

I will try installing guest additions.

Hopachi said:

So it was a case of concurrently running VirtualBox with Hyper-V turned on...
At least it worked so it's getting better so it seems.

But good thing you sorted that out.

Additions will improve it, the graphics alone should give it a boost in screen 'movement'.

I feel like I'm barging in on a conversation, but although I've heard of Hyper-V, I've never used it & know nothing about it. Is there an advantage for a single user on Win10 Pro to use it? If so, is there a a discussion where I could learn what it does?

phrab said:

I feel like I'm barging in on a conversation, but although I've heard of Hyper-V, I've never used it & know nothing about it. Is there an advantage for a single user on Win10 Pro to use it? If so, is there a a discussion where I could learn what it does?

Simple answer: Hyper-V (and Virtualbox) lets you run a virtual machine, a completely independent PC, on your desktop with it's own (not necessarily Windows) OS. There are many uses, for instance you could install an Insider Build of W10 in a virtual machine for testing, while leaving your actual PC (known in VM terms as the Host machine) completely untouched.

In the discussion here, viBoot is Macrium's tool to allow you to boot a Reflect system image as a Virtual Machine, in Hyper-V or (new for v8) in Virtualbox.

Bree said:

Simple answer: Hyper-V (and Virtualbox) lets you run a virtual machine, a completely independent PC, on your desktop with it's own (not necessarily Windows) OS. There are many uses, for instance you could install an Insider Build of W10 in a virtual machine for testing, while leaving your actual PC (known in VM terms as the Host machine) completely untouched.

In the discussion here, viBoot is Macrium's tool to allow you to boot a Reflect system image as a Virtual Machine, in Hyper-V or (new for v8) in Virtualbox.

Thank you! I guess if I do decide to use it, I'll use Hyper-V, since it's faster, according to the posts above.

phrab said:

I feel like I'm barging in on a conversation, but although I've heard of Hyper-V, I've never used it & know nothing about it. Is there an advantage for a single user on Win10 Pro to use it? If so, is there a a discussion where I could learn what it does?

There are an excellent series of HyperV tutorials in this forum's tutorial section. Virtual machines are a great way of testing insider versiins for example.