#Download vmware workstation 12 pro update#
#Download vmware workstation 12 pro manual#
#Download vmware workstation 12 pro upgrade#
#Download vmware workstation 12 pro windows 10#

#Download vmware workstation 12 pro windows 10#

In addition, many of the functions available in bcdedit and Powershell are not available with Windows 10 Home. If you are using the basic Window 10 HOME updated to the latest 2018 build level, VMware will not function, because some elements of Hyper-V are included, although they cannot be controlled. Just to add a solution that worked for me:

VMWare still working with 'hypervisorlaunchtype' boot value deleted!.

Prompt and ran 'bcdedit /deletevalue hypervisorlaunchtype' to just remove the setting because I know someday I will forget and it will prevent me from getting Hyper-V going, reboot after doing this, but at the very least it must be set to 'off'

Note: At some point in this mess I ran 'bcdedit /set hypervisorlaunchtype off'.I attempted running VMWare with the 'hypervisorlaunchtype' set to 'auto' and got the Credential Guard/Device Guard error again.

After all this Hyper-V services no longer start automatically and VMWare starts without issue.

Went to 'Turn Windows features on or off' and un-checked Hyper-V to remove it again.

Verified Hyper-V was working (did not start a VM, just launched manager and saw it showed my computer name in the list).

Went to 'Turn Windows features on or off' and checked Hyper-V to add it back.

Run>gpedit.msc, set Group Policy 'Turn on Virtualization Based Security' backВ to 'Not Configured' (mentioned here:В ).

#Download vmware workstation 12 pro manual#

Run>services.msc, set all Hyper-V services backВ to Manual (will show as 'Manual(triggered)').It would give me either the Hyper-V compatibility error the OP shows, or the Credential Guard/Device Guard error no matter what I did. I actually tried all suggestions here and It appears Hyper-V possibly did not completely remove/disable itself in my case (after removing Hyper-V, some services were still starting automatically).

Hope this helps someone else! None of this fixed it for me. You may also need to disable it from starting by using a command line command mentioned before: I would also make sure to have hyper-v disabled in windows features.Дisable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V вЂ“All When you reboot you should get a preboot dialougue asking if you want to disable credential manager Then run the readiness tool with the disable flag:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned The tool is a powershell script so make sure to set your powershell exexution policy: Check local group policy for the following and disable:Д¬omputer configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security: disabled I was able to disable credential guard by using microsoft's Device Guard and Credential Guard hardware readiness tool: ДЇirst, make sure it isn't managed by group policy. Re-enabled the VT-x features in BIOS and am right back to where I started with the 'VMware and Hyper-V are not compatible' errors.Д¬redential guard is the root of the problem. Tried one of my Win 10 ењ†4 VM's andД¬ould not get it to run.but also did not get the 'VMware not compatible with Hyper-V' messages either. There were some complaints by VMware but it did run. This did allow me to launch a Win XP SP3 (32-bit) VM. I also tried turning off the Intetl VT-x features in BIOS. I also have uninstalled/reinstalled VMware - no luck. I also confirmed that no Hyper-V components were active in Windows Components Add/Remove.

#Download vmware workstation 12 pro upgrade#

So it appears to be related to the upgrade process. 1607 and VMware Workstation 12.1.1 is running fine. I have a second machine (Dell LatitudeД®7440) which was a clean-install of Windows 10 x 64 Enterprise ver. After the upgrade I am now getting this error.

Prior to the upgrade VMware Workstation v.

#Download vmware workstation 12 pro update#

I recently upgraded my desktop from Win Enterprise ењ†4 to the anniversary update ver 1607. Update: I tried with the build 14316 and got the same issue. I tried the bcdedit /set hypervisorlaunchtype off but did not work. I sent this issue using the Feedback Hub app, but I would like to find a workaround while another build is released. I cannot run VMware neither Hyper-V, because I am not able to enable the Hyper-V Platform again (everything is good in my BIOS). I then ran the upgrade to the 14295 again and just received the same error, even when I have not enabled Hyper-V at all. I reinstalled build 1511 (full updated), installed only VMware and it worked just fine. Hyper-V was disabled, of course, but I figured out that the Hyper-V Platform is greyed out (look at the Pic2). Remove the Hyper-V role from the system before running VMware Workstation' (Pic1). 'VMware Workstation and Hyper-V are not compatible. Everything seems to be fine, but I received this error message when I tried to run a VMware VM: I upgraded Windows 10 Enterprise to build 14295 I had Hyper-V enabled and, because of my job, had to disable it and installed VMware Workstation 12.1 Pro.