Hello, I am trying resolve that issue:
Got image created by macrium, booting it with viboot on windows 10 pro with hyper-v, its starts, works fine but vm list in viboot is "deleted VM" only with attached image/images. It works only to first reboot of my Win10 pc. After that cant start/backup etc. from viboot menu. What the heck? Cant start in HYPER-V as well. Please help.

Hi Jools

Thanks for posting. 

viBoot creates a temporary VM to test that images can be successfully booted using instant virtualisation. viBoot VM's do not persist after rebooting the host. 



Is this after a host reboot? Can you please attach a screen shot if not?

Kind Regards

Nick

Macrium Support

See our reviews on

Thanks for reply.
This state is just after create VM.

Hi Jools,

viBoot uses WMI to query Windows for VM's. It then maps VM's to mounted images. If there are mounted images that aren't mapped to VM's they are mapped to the "Delete VMs" entry to allow users to cleanly unmount images, etc... Could you please raise a support ticket so that your issue can be investigated further:

https://macrium.com/support

Thanks,

Mike.

Hello, we have exactly the same problem on two PCs. Both running Windows 10 and after creating VM in viBoot and then booting, it changed to Deleted VM. But it is still in Hyper-V administration.