New
#11
As guided I went through all relevant tutorials by Kari and first I must bow for his effort put for creating such detailed documentation.
So I tried using ViBoot to create VM from Macrium image. However I have one clarification to seek and request help.
Background:
I have two hard disks in my laptop. The second hard disk is replcament of CD/dvd bay.
Disk 1 is on UEFI having default created partitions and three data partitions. Disk two has just two data partitions.
The disk management layout is shown as per attachment.
When I created macrium image i only selected system partitions as sugggested by macrium which excluded data partitions.
However when I used viboot to create vm; while the vm gets created but before that i get follwing messages.
Why do i get such messages when i never imaged them.
Although I can bypass this but why it pops up.
Moreover I believe this is creating issue when i try to install some sofwtare on VM and then apply changes. The process takes huge time as it tries to apply changes to these data partitions as well.
Kindly clarify and how to avoid.
You are overcomplicating things really using viboot.
If you just create a blank virtual hard drive from disk management and initialise as GPT driv, then you can simply restore macrium backup image to that drive.
Once restored, detach vhd.
Then simply create new vm in hyper-v and connect to that drive.
![]()
OK I did execute what u said but i have one question since this was done outside Macrium viboot then once i update more software in virtual machine; how can i apply such changes back to macrium image?
I was trying to follow-
Macrium viBoot - Create Virtual Machine using Macrium Image Windows 10 Virtualization Tutorials
Forget viboot. Just install Macrium on your VM and create another image. Then you'll have an image with your changes included.
You can (if you want) restore that image back onto your real hardware by booting from Macrium recovery USB.
Assuming you have a license for the VM and the real hardware you'll have no issues swapping between the two like this at all.
TBH I do not even bother installing MR in VM. I simply attach VHD(X) file in host and image from there as I have MR Home single user licence. It is much faster as well doing it this way on my PC at least.
It does not really matter that much if vm is unactivated - a restored host image automatically activates anyway.