I´ve been using VMware Player as my preferred private virtualization solution for years and years.
With the Windows 10 bad surprise I so far simply switched off (and on) Hyper-V with
bcdedit /set hypervisorlaunchtype off
to make it work.
With Windows 1709 forced upon me I find two months after release VMware Workstation is not compatible with Device/Credential Guard and according to
I´m supposed to fiddle with boot on the command line in a major way with no apparent way to undo things.
There doesn´t even seem to be an option to BUY sth compatible (at a reasonable price)!?
Now all of a sudden all the work I put into the Player VMs has become useless and I need to see how to proceed (with Hyper-V) quickly as I need sth.
Rrreally pi**d.
G.
Here´s my experience how to solve the VMware Workstation / Player Device / Credential Guard compatibility problem / Hyper-V entangled, convoluted BS. Good to know when one can rely on oneself these days.
With all that set straight I can now switch at MY will between Hyper-V VMs and Docker on one side and VMware on the other.
Hope this helps some poor souls who don´t get an answer here or are lost with all that misinformation and detours floating around.
Cheers
G.
Here´s my experience how to solve the VMware Workstation / Player Device / Credential Guard compatibility problem / Hyper-V entangled, convoluted BS. Good to know when one can rely on oneself these days.
With all that set straight I can now switch at MY will between Hyper-V VMs and Docker on one side and VMware on the other.
Hope this helps some poor souls who don´t get an answer here or are lost with all that misinformation and detours floating around.
Cheers
G.