It is difficult to post in this forum when I have updates to a prior post but can't just tag on to the prior post due to the moderation and the fact my prior posts haven't made it through the moderation queue yet...

Anyway, I just wanted to say that I've learned that you can't run VMware and Hyper-V at the same time.  This means in my case since I had VMware Workstation installed it would no longer run after I installed MS Hyper-V in order to try out viBoot.  So, unfortunately I can't try out this new product, and I was kind of excited about it.  Well, I guess I COULD still try it out by uninstalling Hyper-V and rebooting the computer each time I wanted to run Workstation but that's not worth it to me.

It'll be interesting to watch how others move forward with viBoot though.

Hi Gork,

Unfortunatley, you are correct that Hyper-V and VMWare cannot co-exist on the same hardware. As mentioned in one of my previous responses - we do intend to support VMWare in a future release. In the mean time, I did a quick Google search and found this: http://social.technet.microsoft.com/wiki/contents/articles/22283.how-to-install-hyper-v-on-vmware-workstation-10.aspx.

It details how to install Hyper-V on VMWare Workstation 10. We have not tested this ourselves, but it might provide a temporary solution for you to test Macrium viBoot.

Kind Regards,
Jamie - Macrium Support

Kind Regards

Jamie

Macrium Development

See our reviews on

I didn't think of trying to use Hyper-V inside a Workstation vm so thanks.  I did find some "solutions" on trying to run Hyper-V and Workstation side by side, but they included caveats I was not willing to live with.  The cleanest way is to install the Hyper-V components when you want to use them, then uninstall them when you want to use Workstation.  But I use Workstation often, so that'd be a pain - especially considering a reboot is required after un/installing Hyper-V.

Unfortunately if you try and run viBoot under Win8.1 Pro in a Workstation VM you get a 'cannot run viBoot in a virtual machine'

You have to make some changes to the Workstation vm setup file. Did you try following the instructions at the Web page linked above and it still didn't work?

Sorry, above anonymous poster was me.

Jeez, I hope anonymous posting isn't intended to remain as a permanent feature here. ... "Arvy"

I know this is a very old thread but worth posting this

You can make a new boot entry so you can then choose on reboot whether to boot with Hyper V turned on or not.

1. Install Hyper V
2. bcdedit /copy "{current}" /d "Hyper-V" 
3. bcdedit /set "{current}" hypervisorlaunchtype off
Then you can choose when you boot if you want Hyper V or not so if you want to use vmware for example you pick the boot option without Hyper V.

I just read a news article announcing VMware Workstation Pro 14 will be released in October and will have the ability to run Hyper-V inside a VM inside Workstation...  It'll be nice to be able to more easily try out viBoot!  That is, if I can swallow the upgrade price a year early - I normally only upgrade Workstation every other year and just did so last year.  But this addition is enticing!

That's because as of Win10 / Server 2016, Hyper-V has supported nested virtualization. It can be handy when you want to conduct labs (running on VMs) that involve setting up Hyper-V, for example. I personally wish it would go the other way since I would imagine performance would be better if you had the Tier 1 hypervisor (Hyper-V) running on hardware hosting the Tier 2 hypervisor rather than the other way around.

Also don't forget that exploring this will require a separate Windows license for the VM unless of course you're fine just using the trial period.