VMware workstation and Hyper-V are not compatible. How to Remove the Hyper-V role?
up vote
2
down vote
favorite
I’m running VMware Workstation for virtualization, and as you all know,
VMware and Hyper-V are sworn enemies.
After the last Windows update, Hyper-V was enabled again, but it was easy to just disable, so it worked that one time. Now I have Hyper-V disabled and I still get a warning when trying to open VMware:
Other threads have suggested that that there are other applications/services that use Hyper-V.
I do not have anything called Device Guard on my Windows 10-computer.
(Although I have BitDefender.)
To keep it short: How can I run VMware again?
windows windows-10 hyper-v vmware-workstation
edited Oct 4 at 0:06
Scott
15.5k113789
asked Jan 31 at 12:28
Cowborg
1112
add a comment |
up vote
2
down vote
favorite
I’m running VMware Workstation for virtualization, and as you all know,
VMware and Hyper-V are sworn enemies.
After the last Windows update, Hyper-V was enabled again, but it was easy to just disable, so it worked that one time. Now I have Hyper-V disabled and I still get a warning when trying to open VMware:
Other threads have suggested that that there are other applications/services that use Hyper-V.
I do not have anything called Device Guard on my Windows 10-computer.
(Although I have BitDefender.)
To keep it short: How can I run VMware again?
windows windows-10 hyper-v vmware-workstation
edited Oct 4 at 0:06
Scott
15.5k113789
asked Jan 31 at 12:28
Cowborg
1112
github.com/Microsoft/WSL/issues/2850
– grawity
Jan 31 at 12:30
@Cowborg - Please supply us which build you are using. You can determine that by runningwinver
– Ramhound
Jan 31 at 14:52
OS Build 16299.192
– Cowborg
Feb 1 at 16:11
I have the same issue. I installed updates and I can't use VMware Workstation anymore.
– drinovc
Jun 19 at 13:37
Possible duplicate of Cannot run VM in VMWare on Windows 10 due to Hyper-V
– DaveInCaz
Nov 15 at 13:01
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I’m running VMware Workstation for virtualization, and as you all know,
VMware and Hyper-V are sworn enemies.
After the last Windows update, Hyper-V was enabled again, but it was easy to just disable, so it worked that one time. Now I have Hyper-V disabled and I still get a warning when trying to open VMware:
Other threads have suggested that that there are other applications/services that use Hyper-V.
I do not have anything called Device Guard on my Windows 10-computer.
(Although I have BitDefender.)
To keep it short: How can I run VMware again?
windows windows-10 hyper-v vmware-workstation
edited Oct 4 at 0:06
Scott
15.5k113789
asked Jan 31 at 12:28
Cowborg
1112
I’m running VMware Workstation for virtualization, and as you all know,
VMware and Hyper-V are sworn enemies.
After the last Windows update, Hyper-V was enabled again, but it was easy to just disable, so it worked that one time. Now I have Hyper-V disabled and I still get a warning when trying to open VMware:
Other threads have suggested that that there are other applications/services that use Hyper-V.
I do not have anything called Device Guard on my Windows 10-computer.
(Although I have BitDefender.)
To keep it short: How can I run VMware again?
windows windows-10 hyper-v vmware-workstation
windows windows-10 hyper-v vmware-workstation
edited Oct 4 at 0:06
Scott
15.5k113789
asked Jan 31 at 12:28
Cowborg
1112
edited Oct 4 at 0:06
Scott
15.5k113789
asked Jan 31 at 12:28
Cowborg
1112
edited Oct 4 at 0:06
Scott
15.5k113789
edited Oct 4 at 0:06
Scott
15.5k113789
edited Oct 4 at 0:06
Scott
15.5k113789
15.5k113789
asked Jan 31 at 12:28
Cowborg
1112
asked Jan 31 at 12:28
Cowborg
1112
asked Jan 31 at 12:28
Cowborg
1112
1112
github.com/Microsoft/WSL/issues/2850
– grawity
Jan 31 at 12:30
@Cowborg - Please supply us which build you are using. You can determine that by runningwinver
– Ramhound
Jan 31 at 14:52
OS Build 16299.192
– Cowborg
Feb 1 at 16:11
I have the same issue. I installed updates and I can't use VMware Workstation anymore.
– drinovc
Jun 19 at 13:37
Possible duplicate of Cannot run VM in VMWare on Windows 10 due to Hyper-V
– DaveInCaz
Nov 15 at 13:01
add a comment |
github.com/Microsoft/WSL/issues/2850
– grawity
Jan 31 at 12:30
@Cowborg - Please supply us which build you are using. You can determine that by runningwinver
– Ramhound
Jan 31 at 14:52
OS Build 16299.192
– Cowborg
Feb 1 at 16:11
I have the same issue. I installed updates and I can't use VMware Workstation anymore.
– drinovc
Jun 19 at 13:37
Possible duplicate of Cannot run VM in VMWare on Windows 10 due to Hyper-V
– DaveInCaz
Nov 15 at 13:01
github.com/Microsoft/WSL/issues/2850
– grawity
Jan 31 at 12:30
github.com/Microsoft/WSL/issues/2850
– grawity
Jan 31 at 12:30
@Cowborg - Please supply us which build you are using. You can determine that by running
winver– Ramhound
Jan 31 at 14:52
@Cowborg - Please supply us which build you are using. You can determine that by running
winver– Ramhound
Jan 31 at 14:52
OS Build 16299.192
– Cowborg
Feb 1 at 16:11
OS Build 16299.192
– Cowborg
Feb 1 at 16:11
I have the same issue. I installed updates and I can't use VMware Workstation anymore.
– drinovc
Jun 19 at 13:37
I have the same issue. I installed updates and I can't use VMware Workstation anymore.
– drinovc
Jun 19 at 13:37
Possible duplicate of Cannot run VM in VMWare on Windows 10 due to Hyper-V
– DaveInCaz
Nov 15 at 13:01
Possible duplicate of Cannot run VM in VMWare on Windows 10 due to Hyper-V
– DaveInCaz
Nov 15 at 13:01
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
Just to add a solution that worked for me:
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.
In addition, many of the functions available in bcdedit and Powershell are not available with Windows 10 Home. For example, in Powershell, none of the vm cmdlts are available. Credential Guard/Device Guard are also not available. The Microsoft site solutions will not work. Even the so-called "Hypervisor readiness" do not run.
In "Programs" "Windows Functions" there are no selections for Hyper-V. There is only a generic tickbox for "Windows Hypervisor Platform".
However this sequence works:
untick "Windows Hypervisor Platform"
run bcdedit /set hypervisorlaunchtype off
reboot
steps 1-3 are not enough ! You must also deactivate the "Core Isolation" function in the Windows Defender Security Center.
Reboot again.
VMware will then function.
It is strange but interesting that "Core Isolation" also has an effect on some system drivers. With Core Isolation activated, my laptop CD/DVD drive was dead, Windows would not recognise its own native driver cdrom.sys. But everything returns to normal when Core Isolation is deactivated.
answered Nov 23 at 23:17
peterbrendon
91
New contributor
peterbrendon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
-1
down vote
CMD with administrative rights
bcdedit /set hypervisorlaunchtype off
and a reboot.
answered Oct 3 at 22:51
drd9973
11
add a comment |
protected by Ramhound Nov 24 at 0:49
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Just to add a solution that worked for me:
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.
In addition, many of the functions available in bcdedit and Powershell are not available with Windows 10 Home. For example, in Powershell, none of the vm cmdlts are available. Credential Guard/Device Guard are also not available. The Microsoft site solutions will not work. Even the so-called "Hypervisor readiness" do not run.
In "Programs" "Windows Functions" there are no selections for Hyper-V. There is only a generic tickbox for "Windows Hypervisor Platform".
However this sequence works:
untick "Windows Hypervisor Platform"
run bcdedit /set hypervisorlaunchtype off
reboot
steps 1-3 are not enough ! You must also deactivate the "Core Isolation" function in the Windows Defender Security Center.
Reboot again.
VMware will then function.
It is strange but interesting that "Core Isolation" also has an effect on some system drivers. With Core Isolation activated, my laptop CD/DVD drive was dead, Windows would not recognise its own native driver cdrom.sys. But everything returns to normal when Core Isolation is deactivated.
answered Nov 23 at 23:17
peterbrendon
91
New contributor
peterbrendon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
Just to add a solution that worked for me:
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.
In addition, many of the functions available in bcdedit and Powershell are not available with Windows 10 Home. For example, in Powershell, none of the vm cmdlts are available. Credential Guard/Device Guard are also not available. The Microsoft site solutions will not work. Even the so-called "Hypervisor readiness" do not run.
In "Programs" "Windows Functions" there are no selections for Hyper-V. There is only a generic tickbox for "Windows Hypervisor Platform".
However this sequence works:
untick "Windows Hypervisor Platform"
run bcdedit /set hypervisorlaunchtype off
reboot
steps 1-3 are not enough ! You must also deactivate the "Core Isolation" function in the Windows Defender Security Center.
Reboot again.
VMware will then function.
It is strange but interesting that "Core Isolation" also has an effect on some system drivers. With Core Isolation activated, my laptop CD/DVD drive was dead, Windows would not recognise its own native driver cdrom.sys. But everything returns to normal when Core Isolation is deactivated.
answered Nov 23 at 23:17
peterbrendon
91
New contributor
peterbrendon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
Just to add a solution that worked for me:
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.
In addition, many of the functions available in bcdedit and Powershell are not available with Windows 10 Home. For example, in Powershell, none of the vm cmdlts are available. Credential Guard/Device Guard are also not available. The Microsoft site solutions will not work. Even the so-called "Hypervisor readiness" do not run.
In "Programs" "Windows Functions" there are no selections for Hyper-V. There is only a generic tickbox for "Windows Hypervisor Platform".
However this sequence works:
untick "Windows Hypervisor Platform"
run bcdedit /set hypervisorlaunchtype off
reboot
steps 1-3 are not enough ! You must also deactivate the "Core Isolation" function in the Windows Defender Security Center.
Reboot again.
VMware will then function.
It is strange but interesting that "Core Isolation" also has an effect on some system drivers. With Core Isolation activated, my laptop CD/DVD drive was dead, Windows would not recognise its own native driver cdrom.sys. But everything returns to normal when Core Isolation is deactivated.
answered Nov 23 at 23:17
peterbrendon
91
New contributor
peterbrendon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Just to add a solution that worked for me:
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.
In addition, many of the functions available in bcdedit and Powershell are not available with Windows 10 Home. For example, in Powershell, none of the vm cmdlts are available. Credential Guard/Device Guard are also not available. The Microsoft site solutions will not work. Even the so-called "Hypervisor readiness" do not run.
In "Programs" "Windows Functions" there are no selections for Hyper-V. There is only a generic tickbox for "Windows Hypervisor Platform".
However this sequence works:
untick "Windows Hypervisor Platform"
run bcdedit /set hypervisorlaunchtype off
reboot
steps 1-3 are not enough ! You must also deactivate the "Core Isolation" function in the Windows Defender Security Center.
Reboot again.
VMware will then function.
It is strange but interesting that "Core Isolation" also has an effect on some system drivers. With Core Isolation activated, my laptop CD/DVD drive was dead, Windows would not recognise its own native driver cdrom.sys. But everything returns to normal when Core Isolation is deactivated.
answered Nov 23 at 23:17
peterbrendon
91
New contributor
peterbrendon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 23 at 23:17
peterbrendon
91
New contributor
peterbrendon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 23 at 23:17
peterbrendon
91
answered Nov 23 at 23:17
peterbrendon
91
91
New contributor
peterbrendon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
peterbrendon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
peterbrendon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
up vote
-1
down vote
CMD with administrative rights
bcdedit /set hypervisorlaunchtype off
and a reboot.
answered Oct 3 at 22:51
drd9973
11
add a comment |
up vote
-1
down vote
CMD with administrative rights
bcdedit /set hypervisorlaunchtype off
and a reboot.
answered Oct 3 at 22:51
drd9973
11
add a comment |
up vote
-1
down vote
up vote
-1
down vote
CMD with administrative rights
bcdedit /set hypervisorlaunchtype off
and a reboot.
answered Oct 3 at 22:51
drd9973
11
CMD with administrative rights
bcdedit /set hypervisorlaunchtype off
and a reboot.
answered Oct 3 at 22:51
drd9973
11
answered Oct 3 at 22:51
drd9973
11
answered Oct 3 at 22:51
drd9973
11
answered Oct 3 at 22:51
drd9973
11
11
add a comment |
add a comment |
protected by Ramhound Nov 24 at 0:49
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
github.com/Microsoft/WSL/issues/2850
– grawity
Jan 31 at 12:30
@Cowborg - Please supply us which build you are using. You can determine that by running
winver– Ramhound
Jan 31 at 14:52
OS Build 16299.192
– Cowborg
Feb 1 at 16:11
I have the same issue. I installed updates and I can't use VMware Workstation anymore.
– drinovc
Jun 19 at 13:37
Possible duplicate of Cannot run VM in VMWare on Windows 10 due to Hyper-V
– DaveInCaz
Nov 15 at 13:01