New
#1
Hard to say - only thing I can suggest is to create a virtual hard drive and clean install 1703 in it and see if that works, then try 1511 etc., trying older version of vmware etc. But hey - you are an expert so I am teling you to suck eggs. Maybe our resident vmware expert @jimbo could shed some light?
Ok, so very stupid happened. actually two of them. As it wouldn't work initially I turned on Hyper-V and Hypervisor and as it still wouldn't work I forgot about it. Than I thought that CPU virtualization wasn't enabled. Looked and looked thru BIOS (stupid UEFI) and couldn't find setting. At the end, just like any full blooded male person I resorted to humiliation and looked in the MB manual at last. That's where I found that they called it very (un)imaginative name "AVX" (without any explanation). It should have been enabled by default (as per manual) but it wasn't. I enabled it and than it wouldn't work until Hiper-V Hpervisor was turned. off but now VM works as advertised.
Last edited by CountMike; 03 Jun 2017 at 12:57.
This thread from our sister site may be useful so you can use hyper-v or vmware.
Solved Hyper V and VMWare on the same machine
Out of interest, why are you using VMware over Hyper-V. Hyper-V does have one annoying restriction in that you cannot get sound in basic mode.