New
#11
There used to be a regedit you had to do to get export working properly. I think it was user @slicendice who told me.
@hanks, I've checked back on my posts from that time and it was indeed v7.1 I had, but I've also found that exporting the viBoot VM failed then too (albeit with a different error message). I did however find a way to make a new standard Hyper-V VM from a viBoot VM (and that one can then be exported, if you wish).
Export Hyper-V Virtual Machine in Windows 10 - Page 2 - | TutorialsBree said:
I've just tested that method today and successfully made a new VM from a viBoot VM.
Yes, it's a completely normal Hyper-V VM, solely managed by Hyper-V Manager.
The new VM is fully independent of the viBoot VM you created it from. Once you have edited the viBoot VM's disk to merge it into a new vhd and used that as the virtual disk for the new VM you can delete the original VM in viBoot. You could also delete the original .mrimg (if you wish). The new VM doesn't need any of them.
Thanks, it worked like a champ.
Most interesting thing I discovered: My native system occupies about 39 GB, the Hyper-V virtual image I created by merging is about 34 GB, but the virtual disk created by viBoot is 3.5 GB. I never realized that if I kill (or move) the original MR image the viboot machine dies (that's why my conventional data drive thrashes when I start the viboot machine -- all my other virtual machines are stored on a separate SSD). The viBoot vhd is not a 'stand alone' machine, it needs the original MR backup to function.
viBoot is great for 'temporary' machines, and thanks to @Bree and others I can make true Hyper-V machines from MR backups. Yea!
There is a problem with Bree's fix. If the Disk has a checkpoint, it will not allow you to edit it ????