Backup and Restore with Macrium Reflect  

Matthew Wai said:

It is far beyond me.

It is actually really easy to use, viBoot is probably an easier interface to get to grips with than Reflect itself. For a Windows Home machine you'd need to install VirtualBox first, for Pro you need to turn on Hyper-V.

See Macrium's video here: Macrium Software | Macrium viBoot
and the Knowledge Base: Macrium viBoot - Knowledgebase 8.0 - Macrium Reflect Knowledgebase

Bree said:

It is actually really easy to use, viBoot is probably an easier interface to get to grips with than Reflect itself. For a Windows Home machine you'd need to install VirtualBox first, for Pro you need to turn on Hyper-V.

See Macrium's video here: Macrium Software | Macrium viBoot
and the Knowledge Base: Macrium viBoot - Knowledgebase 8.0 - Macrium Reflect Knowledgebase

Just a minor followup - some people try and run virtualbox on Pro with Hyper-V enabled. Unfortunately, they do not play well together and virtualbox is very slow.

If you really want to use virtualbox on Pro, you should disable the Hyper-V hypervisor (or uninstall Hyper-V).

You can create a dual boot entry where one entry boots into (same) windows with the hypervisor running (to use Hyper-V), or boot into (same) windows with hypervisor not running (to use virtual box).

cereberus said:

Just a minor followup - some people try and run virtualbox on Pro with Hyper-V enabled. Unfortunately, they do not play well together and virtualbox is very slow.

If you really want to use virtualbox on Pro, you should disable the Hyper-V hypervisor (or uninstall Hyper-V).

You can create a dual boot entry where one entry boots into (same) windows with the hypervisor running (to use Hyper-V), or boot into (same) windows with hypervisor not running (to use virtual box).

Virtualbox can use Hyper-V as it's virtualisation engine since V6 but it's described as experimental and I don't think it is an entirely satisfactory implementation.

I believe Matthew has Home, so Hyper-V is not going to be an issue for him.

kado897 said:

Virtualbox can use Hyper-V as it's virtualisation engine since V6 but it's described as experimental and I don't think it is an entirely satisfactory implementation.

Which is why I said they do not play well together, and is slow. Before the changes, I would have said they could not coexist.

kado897 said:

ViBoot gives the ability to boot an MR image in a VM using HyperV or VirtualBox for testing purposes.

I've never used virtualization, but it does interest me. If I turned on hyper-V & used MR's ViBoot, would that mean that I could install any type of software as a test or visit any "dangerous" website without any worry...i.e. I could just exit ViBoot & everything would be as if I never did anything?

I've been using Sandboxie or Acronis' Try & Decide for that purpose.

phrab said:

I've never used virtualization, but it does interest me. If I turned on hyper-V & used MR's ViBoot, would that mean that I could install any type of software as a test or visit any "dangerous" website without any worry...i.e. I could just exit ViBoot & everything would be as if I never did anything?

I've been using Sandboxie or Acronis' Try & Decide for that purpose.

I'm no expert on Hyper-V but yes I believe so. You don't need a MR image though, you can just install a new W10 or any other OS in a Hyper-V VM. I do that using VirtualBox as I'm using W10 Home which doesn't have Hyper-V.

kado897 said:

I'm no expert on Hyper-V but yes I believe so. You don't need a MR image though, you can just install a new W10 or any other OS in a Hyper-V VM. I do that using VirtualBox as I'm using W10 Home which doesn't have Hyper-V.

Thanks, Keith. I've never used it, but I was hoping it would be something simple, like starting "Try & Decide" or doing something within a Sandbox. I guess I should read up on it.