Tjyylli

Does Linux have system calls to access all the features of the file systems it supports?

Why don't MCU characters ever seem to have language issues?

Deleting missing values from a dataset

My story is written in English, but is set in my home country. What language should I use for the dialogue?

What is the dot in “1.2.4."

Touchscreen-controlled dentist office snowman collector game

Plywood subfloor won't screw down in a trailer home

Can the druid cantrip Thorn Whip really defeat a water weird this easily?

Running a subshell from the middle of the current command

How to deal with a cynical class?

Can you reject a postdoc offer after the PI has paid a large sum for flights/accommodation for your visit?

This equation is outside the page, how to modify it

Giving Plot options defined outside of the Plot expression

Good allowance savings plan?

Does the Bracer of Flying Daggers benefit from the Dueling Fighting style?

Is having access to past exams cheating and, if yes, could it be proven just by a good grade?

Potentiometer like component

How do anti-virus programs start at Windows boot?

Heap & Stack Java

How does Dispel Magic work against Stoneskin?

Life insurance that covers only simultaneous/dual deaths

Does splitting a potentially monolithic application into several smaller ones help prevent bugs?

Sword in the Stone story where the sword was held in place by electromagnets

Format picture and text with TikZ and minipage

VT-x is not available, but is enabled in BIOS

“AMD-V is not available” even when Virtualization is enabled in the biosVirtualBox - How to solve “VT-x not available” when VT-x is turned on in BIOS?Error with Oracle VM VirtualBox: VT-x is not available (VERR_VMX_NO_VMX)Virtualization (VT-X) stopped working on w10 machine. How can I start it again?VT-x is not available (VERR_VMX_NO_VMX)VirtualBox states “VT-x is not available (VERR_VMX_NO_VMX).”Virtual box is not working on windows 10VirtualBox VERR_VMX_NO_VMXRunning 32 bit OS on 64 bit OS host without VT-xVirtualization does not work anymoreCore 2 Duo E8400 and Intel Virtualization TechnologyVT-x is Enabled, but is not operational ? Winows 8 unable to run 64-bit virtual machineIntel site says VT-x is supported on my CPU, but tests say otherwiseVT-x on 4790 on H97-D3H-CFVT-x is enabled, but it's not detected as such“AMD-V is not available” even when Virtualization is enabled in the biosVirtualBox - How to solve “VT-x not available” when VT-x is turned on in BIOS?X1 Yoga 2nd gen - VT-x not working anymore, BSOD when booting x64 VMsVirtualization (VT-X) stopped working on w10 machine. How can I start it again?VT-x not available in Windows 10 Pro even though i5-6400 CPU supports VT-X

88

33

Recently I started having an issue with VT-x on my Windows 10 running on HP EliteBook. I was using Oracle VirtualBox to run some VMs on it before and VT-x was enabled in BIOS and was working fine.

I started getting VT-x is not available error every time I was trying to start any of my VMs. That started happening after I installed Docker on my machine, so I tried uninstalling it and rebooting. Didn't help.

I checked BIOS settings and it says VT-x is enabled but checking with Intel(R) Processor Identification Utility shows that VT-x is not supported and Oracle VirtualBox also doesn't see it.

There were no hardware changes and the only software change was installing/uninstalling Docker.

How can this issue be fixed?

windows-10 bios virtualization vt-x

share|improve this question

asked Dec 6 '16 at 11:01

SergeyOvchinnikSergeyOvchinnik

6372610

add a comment | 

88

33

Recently I started having an issue with VT-x on my Windows 10 running on HP EliteBook. I was using Oracle VirtualBox to run some VMs on it before and VT-x was enabled in BIOS and was working fine.

I started getting VT-x is not available error every time I was trying to start any of my VMs. That started happening after I installed Docker on my machine, so I tried uninstalling it and rebooting. Didn't help.

I checked BIOS settings and it says VT-x is enabled but checking with Intel(R) Processor Identification Utility shows that VT-x is not supported and Oracle VirtualBox also doesn't see it.

There were no hardware changes and the only software change was installing/uninstalling Docker.

How can this issue be fixed?

windows-10 bios virtualization vt-x

share|improve this question

asked Dec 6 '16 at 11:01

SergeyOvchinnikSergeyOvchinnik

6372610

add a comment | 

Recently I started having an issue with VT-x on my Windows 10 running on HP EliteBook. I was using Oracle VirtualBox to run some VMs on it before and VT-x was enabled in BIOS and was working fine.

I started getting VT-x is not available error every time I was trying to start any of my VMs. That started happening after I installed Docker on my machine, so I tried uninstalling it and rebooting. Didn't help.

I checked BIOS settings and it says VT-x is enabled but checking with Intel(R) Processor Identification Utility shows that VT-x is not supported and Oracle VirtualBox also doesn't see it.

There were no hardware changes and the only software change was installing/uninstalling Docker.

How can this issue be fixed?

windows-10 bios virtualization vt-x

share|improve this question

asked Dec 6 '16 at 11:01

SergeyOvchinnikSergeyOvchinnik

6372610

share|improve this question

asked Dec 6 '16 at 11:01

SergeyOvchinnikSergeyOvchinnik

6372610

share|improve this question

asked Dec 6 '16 at 11:01

SergeyOvchinnikSergeyOvchinnik

6372610

asked Dec 6 '16 at 11:01

SergeyOvchinnikSergeyOvchinnik

6372610

asked Dec 6 '16 at 11:01

SergeyOvchinnikSergeyOvchinnik

6372610

6 Answers
6

active

oldest

votes

119

There are three common culprits for the type of error the user is seeing:

• VT-x is not enabled in the BIOS


• The CPU doesn't support VT-x


• Hyper-V virtualization is enabled in Windows

Since the user already eliminated the first two possible culprits, the next step is to open a command prompt as administrator and run the following command:

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

Afterwards, reboot the PC and try VirtualBox again.

share|improve this answer

edited Dec 7 '16 at 0:31

Ben N

29.8k1398145

answered Dec 6 '16 at 12:28

n8ten8te

4,97272233

• 
  
  
  

  
  32
  

  
  
  
  
  
  

  
  
  To further clarify: Docker runs on top of Windows Hyper-V. The Docker install switched it on, but the de-install didn't switch Hyper-V off.
  
  – Tonny
  Dec 6 '16 at 15:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @cat: It's a shared resource, in order to properly disable it when the last component depending it is removed, you'd need some sort of reference counting.
  
  – Ben Voigt
  Dec 6 '16 at 19:49
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  For completeness: this can also happen with some viruses that use VT-x to hide from the operating system. These are seldom though.
  
  – Simon Richter
  Dec 6 '16 at 19:51
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @cat As Ben already mentioned: Docker has no way of knowing there isn't anything else running on the system that needs Hyper-V. So Docker can switch it on when it needs it, but should not switch it off, because that could kill/crash/disable another application. Not a bug. A "feature" made necessary by the fact that Windows doesn't provide any standard mechanism (reference counting) to keep track of what application is using which resource. Windows only does this for DLL's and some other similar resources and it is far from reliable. As a result it is safer to just leave them alone.
  
  – Tonny
  Dec 6 '16 at 20:07
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  It should be noted that Hyper-V does technically support nested virtualisation since the 1607 update. If you have a need for both Hyper-V and VBox at the same time, you can try enabling it.
  
  – Bob
  Dec 7 '16 at 6:45
  

  
  
  
  

 | 
show 3 more comments

13

After updating Windows 10 to "Fall Creators Update" I got the same issue. I resolved it by the following steps:

1. Enable all features under "Hyper-V" in "Turn Windows features on or
   off".


2. Restart.


3. Disable all features under "Hyper-V" in "Turn Windows features on or off".


4. Restart.


5. Now VirtualBox is working again and it shows (64-bit) in its list of operating systems.

share|improve this answer

edited Mar 15 '18 at 10:56

answered Nov 21 '17 at 10:03

Eng.FouadEng.Fouad

25027

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  For the impatient: disabling Hyper-V took Windows several minutes.
  
  – Jens Piegsa
  Feb 20 '18 at 11:49
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  unfortunately didn't worked for me...
  
  – Mahdi Rashidi
  Jul 28 '18 at 15:27
  

  
  
  
  

add a comment | 

3

If you're using the lasted Windows 10 build, disable Memory Integration in Device Security and reboot.

I was facing similar issue virtual box when I enabled this option. Disabling it worked for me.

share|improve this answer

answered Jan 8 at 12:20

slingzorslingzor

413

add a comment | 

2

Virtualbox was working ok. I updated Avast anti-virus today, 29th June 2017. Virtualbox then gave the VT-x error. In Avast Settings, go to Troubleshooting and enable "Use nested virtualiszation where available" and then reboot your PC. This worked for me with no other changes required.

share|improve this answer

answered Jun 29 '17 at 12:27

ejasftejasft

211

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Getting blue screens here since today (vmm.sys), I use avast free but I don't see that option.
  
  – Dan
  Jun 30 '17 at 5:49
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I had the same problem with Windows Defender. I enabled Device Security - Core Isolation. Disabling that resolved my problem.
  
  – Tsuharesu
  Aug 22 '18 at 0:29
  

  
  
  
  

add a comment | 

2

When I had this problem, VMWare Player gave a better diagnostic response than VirtualBox did when I tried to create a 64-bit virtual machine.

It said that my machine had the enterprise features Device Guard and Credential Guard enabled. I suppose they became enabled when I ran MalwareBytes; I can't think of any other change I made.

VMWare Player pointed me to a page called Manage Windows Defender Credential Guard. That page has a bunch of stuff about Group Policy Manager settings and the like, which of course are irrelevant to a W10 HOME installation.

In turn, that page pointed me to the Device Guard and Credential Guard hardware readiness tool, a PowerShell tool for enabling and disabling this feature set on servers.

Running that tool in a Run-As-Administrator power shell and giving this command

 .DG_Readiness_Tool_v3.5.ps1 -Disable -AutoReboot

took me through the process of disabling those features.

And I have virtualization capability back.

share|improve this answer

answered Jun 19 '18 at 11:52

O. JonesO. Jones

178110

add a comment | 

0

I came to this post thinking that VT-x wasn't enabled, because Hyper-V was telling me that "The virtual machine is using processor-specific features not supported on physical computer". This started after installing Windows updates and restarting the server. In reality, VT-x was actually enabled.

The fix was to delete saved state for all VMs, effectively a power-off.

It looks like the reason for this may have been a CPU microcode update but it's hard to be sure, it's just something that came up in a number of search results.

share

answered 5 mins ago

RomanStRomanSt

5,365134767

add a comment | 

protected by Community♦ Mar 8 '18 at 16:34

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?

119

There are three common culprits for the type of error the user is seeing:

• VT-x is not enabled in the BIOS


• The CPU doesn't support VT-x


• Hyper-V virtualization is enabled in Windows

Since the user already eliminated the first two possible culprits, the next step is to open a command prompt as administrator and run the following command:

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

Afterwards, reboot the PC and try VirtualBox again.

share|improve this answer

edited Dec 7 '16 at 0:31

Ben N

29.8k1398145

answered Dec 6 '16 at 12:28

n8ten8te

4,97272233

• 
  
  
  

  
  32
  

  
  
  
  
  
  

  
  
  To further clarify: Docker runs on top of Windows Hyper-V. The Docker install switched it on, but the de-install didn't switch Hyper-V off.
  
  – Tonny
  Dec 6 '16 at 15:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @cat: It's a shared resource, in order to properly disable it when the last component depending it is removed, you'd need some sort of reference counting.
  
  – Ben Voigt
  Dec 6 '16 at 19:49
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  For completeness: this can also happen with some viruses that use VT-x to hide from the operating system. These are seldom though.
  
  – Simon Richter
  Dec 6 '16 at 19:51
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @cat As Ben already mentioned: Docker has no way of knowing there isn't anything else running on the system that needs Hyper-V. So Docker can switch it on when it needs it, but should not switch it off, because that could kill/crash/disable another application. Not a bug. A "feature" made necessary by the fact that Windows doesn't provide any standard mechanism (reference counting) to keep track of what application is using which resource. Windows only does this for DLL's and some other similar resources and it is far from reliable. As a result it is safer to just leave them alone.
  
  – Tonny
  Dec 6 '16 at 20:07
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  It should be noted that Hyper-V does technically support nested virtualisation since the 1607 update. If you have a need for both Hyper-V and VBox at the same time, you can try enabling it.
  
  – Bob
  Dec 7 '16 at 6:45
  

  
  
  
  

 | 
show 3 more comments

119

There are three common culprits for the type of error the user is seeing:

• VT-x is not enabled in the BIOS


• The CPU doesn't support VT-x


• Hyper-V virtualization is enabled in Windows

Since the user already eliminated the first two possible culprits, the next step is to open a command prompt as administrator and run the following command:

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

Afterwards, reboot the PC and try VirtualBox again.

share|improve this answer

edited Dec 7 '16 at 0:31

Ben N

29.8k1398145

answered Dec 6 '16 at 12:28

n8ten8te

4,97272233

• 
  
  
  

  
  32
  

  
  
  
  
  
  

  
  
  To further clarify: Docker runs on top of Windows Hyper-V. The Docker install switched it on, but the de-install didn't switch Hyper-V off.
  
  – Tonny
  Dec 6 '16 at 15:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @cat: It's a shared resource, in order to properly disable it when the last component depending it is removed, you'd need some sort of reference counting.
  
  – Ben Voigt
  Dec 6 '16 at 19:49
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  For completeness: this can also happen with some viruses that use VT-x to hide from the operating system. These are seldom though.
  
  – Simon Richter
  Dec 6 '16 at 19:51
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @cat As Ben already mentioned: Docker has no way of knowing there isn't anything else running on the system that needs Hyper-V. So Docker can switch it on when it needs it, but should not switch it off, because that could kill/crash/disable another application. Not a bug. A "feature" made necessary by the fact that Windows doesn't provide any standard mechanism (reference counting) to keep track of what application is using which resource. Windows only does this for DLL's and some other similar resources and it is far from reliable. As a result it is safer to just leave them alone.
  
  – Tonny
  Dec 6 '16 at 20:07
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  It should be noted that Hyper-V does technically support nested virtualisation since the 1607 update. If you have a need for both Hyper-V and VBox at the same time, you can try enabling it.
  
  – Bob
  Dec 7 '16 at 6:45
  

  
  
  
  

 | 
show 3 more comments

There are three common culprits for the type of error the user is seeing:

• VT-x is not enabled in the BIOS


• The CPU doesn't support VT-x


• Hyper-V virtualization is enabled in Windows

Since the user already eliminated the first two possible culprits, the next step is to open a command prompt as administrator and run the following command:

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

Afterwards, reboot the PC and try VirtualBox again.

share|improve this answer

edited Dec 7 '16 at 0:31

Ben N

29.8k1398145

answered Dec 6 '16 at 12:28

n8ten8te

4,97272233

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

share|improve this answer

edited Dec 7 '16 at 0:31

Ben N

29.8k1398145

answered Dec 6 '16 at 12:28

n8ten8te

4,97272233

edited Dec 7 '16 at 0:31

Ben N

29.8k1398145

edited Dec 7 '16 at 0:31

Ben N

29.8k1398145

answered Dec 6 '16 at 12:28

n8ten8te

4,97272233

answered Dec 6 '16 at 12:28

n8ten8te

4,97272233

13

After updating Windows 10 to "Fall Creators Update" I got the same issue. I resolved it by the following steps:

1. Enable all features under "Hyper-V" in "Turn Windows features on or
   off".


2. Restart.


3. Disable all features under "Hyper-V" in "Turn Windows features on or off".


4. Restart.


5. Now VirtualBox is working again and it shows (64-bit) in its list of operating systems.

share|improve this answer

edited Mar 15 '18 at 10:56

answered Nov 21 '17 at 10:03

Eng.FouadEng.Fouad

25027

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  For the impatient: disabling Hyper-V took Windows several minutes.
  
  – Jens Piegsa
  Feb 20 '18 at 11:49
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  unfortunately didn't worked for me...
  
  – Mahdi Rashidi
  Jul 28 '18 at 15:27
  

  
  
  
  

add a comment | 

13

After updating Windows 10 to "Fall Creators Update" I got the same issue. I resolved it by the following steps:

1. Enable all features under "Hyper-V" in "Turn Windows features on or
   off".


2. Restart.


3. Disable all features under "Hyper-V" in "Turn Windows features on or off".


4. Restart.


5. Now VirtualBox is working again and it shows (64-bit) in its list of operating systems.

share|improve this answer

edited Mar 15 '18 at 10:56

answered Nov 21 '17 at 10:03

Eng.FouadEng.Fouad

25027

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  For the impatient: disabling Hyper-V took Windows several minutes.
  
  – Jens Piegsa
  Feb 20 '18 at 11:49
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  unfortunately didn't worked for me...
  
  – Mahdi Rashidi
  Jul 28 '18 at 15:27
  

  
  
  
  

add a comment | 

After updating Windows 10 to "Fall Creators Update" I got the same issue. I resolved it by the following steps:

1. Enable all features under "Hyper-V" in "Turn Windows features on or
   off".


2. Restart.


3. Disable all features under "Hyper-V" in "Turn Windows features on or off".


4. Restart.


5. Now VirtualBox is working again and it shows (64-bit) in its list of operating systems.

share|improve this answer

edited Mar 15 '18 at 10:56

answered Nov 21 '17 at 10:03

Eng.FouadEng.Fouad

25027

share|improve this answer

edited Mar 15 '18 at 10:56

answered Nov 21 '17 at 10:03

Eng.FouadEng.Fouad

25027

answered Nov 21 '17 at 10:03

Eng.FouadEng.Fouad

25027

answered Nov 21 '17 at 10:03

Eng.FouadEng.Fouad

25027

3

If you're using the lasted Windows 10 build, disable Memory Integration in Device Security and reboot.

I was facing similar issue virtual box when I enabled this option. Disabling it worked for me.

share|improve this answer

answered Jan 8 at 12:20

slingzorslingzor

413

add a comment | 

3

If you're using the lasted Windows 10 build, disable Memory Integration in Device Security and reboot.

I was facing similar issue virtual box when I enabled this option. Disabling it worked for me.

share|improve this answer

answered Jan 8 at 12:20

slingzorslingzor

413

add a comment | 

If you're using the lasted Windows 10 build, disable Memory Integration in Device Security and reboot.

I was facing similar issue virtual box when I enabled this option. Disabling it worked for me.

share|improve this answer

answered Jan 8 at 12:20

slingzorslingzor

413

share|improve this answer

answered Jan 8 at 12:20

slingzorslingzor

413

answered Jan 8 at 12:20

slingzorslingzor

413

answered Jan 8 at 12:20

slingzorslingzor

413

2

Virtualbox was working ok. I updated Avast anti-virus today, 29th June 2017. Virtualbox then gave the VT-x error. In Avast Settings, go to Troubleshooting and enable "Use nested virtualiszation where available" and then reboot your PC. This worked for me with no other changes required.

share|improve this answer

answered Jun 29 '17 at 12:27

ejasftejasft

211

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Getting blue screens here since today (vmm.sys), I use avast free but I don't see that option.
  
  – Dan
  Jun 30 '17 at 5:49
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I had the same problem with Windows Defender. I enabled Device Security - Core Isolation. Disabling that resolved my problem.
  
  – Tsuharesu
  Aug 22 '18 at 0:29
  

  
  
  
  

add a comment | 

2

Virtualbox was working ok. I updated Avast anti-virus today, 29th June 2017. Virtualbox then gave the VT-x error. In Avast Settings, go to Troubleshooting and enable "Use nested virtualiszation where available" and then reboot your PC. This worked for me with no other changes required.

share|improve this answer

answered Jun 29 '17 at 12:27

ejasftejasft

211

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Getting blue screens here since today (vmm.sys), I use avast free but I don't see that option.
  
  – Dan
  Jun 30 '17 at 5:49
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I had the same problem with Windows Defender. I enabled Device Security - Core Isolation. Disabling that resolved my problem.
  
  – Tsuharesu
  Aug 22 '18 at 0:29
  

  
  
  
  

add a comment | 

Virtualbox was working ok. I updated Avast anti-virus today, 29th June 2017. Virtualbox then gave the VT-x error. In Avast Settings, go to Troubleshooting and enable "Use nested virtualiszation where available" and then reboot your PC. This worked for me with no other changes required.

share|improve this answer

answered Jun 29 '17 at 12:27

ejasftejasft

211

share|improve this answer

answered Jun 29 '17 at 12:27

ejasftejasft

211

answered Jun 29 '17 at 12:27

ejasftejasft

211

answered Jun 29 '17 at 12:27

ejasftejasft

211

2

When I had this problem, VMWare Player gave a better diagnostic response than VirtualBox did when I tried to create a 64-bit virtual machine.

It said that my machine had the enterprise features Device Guard and Credential Guard enabled. I suppose they became enabled when I ran MalwareBytes; I can't think of any other change I made.

VMWare Player pointed me to a page called Manage Windows Defender Credential Guard. That page has a bunch of stuff about Group Policy Manager settings and the like, which of course are irrelevant to a W10 HOME installation.

In turn, that page pointed me to the Device Guard and Credential Guard hardware readiness tool, a PowerShell tool for enabling and disabling this feature set on servers.

Running that tool in a Run-As-Administrator power shell and giving this command

 .DG_Readiness_Tool_v3.5.ps1 -Disable -AutoReboot

took me through the process of disabling those features.

And I have virtualization capability back.

share|improve this answer

answered Jun 19 '18 at 11:52

O. JonesO. Jones

178110

add a comment | 

2

When I had this problem, VMWare Player gave a better diagnostic response than VirtualBox did when I tried to create a 64-bit virtual machine.

It said that my machine had the enterprise features Device Guard and Credential Guard enabled. I suppose they became enabled when I ran MalwareBytes; I can't think of any other change I made.

VMWare Player pointed me to a page called Manage Windows Defender Credential Guard. That page has a bunch of stuff about Group Policy Manager settings and the like, which of course are irrelevant to a W10 HOME installation.

In turn, that page pointed me to the Device Guard and Credential Guard hardware readiness tool, a PowerShell tool for enabling and disabling this feature set on servers.

Running that tool in a Run-As-Administrator power shell and giving this command

 .DG_Readiness_Tool_v3.5.ps1 -Disable -AutoReboot

took me through the process of disabling those features.

And I have virtualization capability back.

share|improve this answer

answered Jun 19 '18 at 11:52

O. JonesO. Jones

178110

add a comment | 

When I had this problem, VMWare Player gave a better diagnostic response than VirtualBox did when I tried to create a 64-bit virtual machine.

It said that my machine had the enterprise features Device Guard and Credential Guard enabled. I suppose they became enabled when I ran MalwareBytes; I can't think of any other change I made.

VMWare Player pointed me to a page called Manage Windows Defender Credential Guard. That page has a bunch of stuff about Group Policy Manager settings and the like, which of course are irrelevant to a W10 HOME installation.

In turn, that page pointed me to the Device Guard and Credential Guard hardware readiness tool, a PowerShell tool for enabling and disabling this feature set on servers.

Running that tool in a Run-As-Administrator power shell and giving this command

 .DG_Readiness_Tool_v3.5.ps1 -Disable -AutoReboot

took me through the process of disabling those features.

And I have virtualization capability back.

share|improve this answer

answered Jun 19 '18 at 11:52

O. JonesO. Jones

178110

 .DG_Readiness_Tool_v3.5.ps1 -Disable -AutoReboot

share|improve this answer

answered Jun 19 '18 at 11:52

O. JonesO. Jones

178110

answered Jun 19 '18 at 11:52

O. JonesO. Jones

178110

answered Jun 19 '18 at 11:52

O. JonesO. Jones

178110

0

I came to this post thinking that VT-x wasn't enabled, because Hyper-V was telling me that "The virtual machine is using processor-specific features not supported on physical computer". This started after installing Windows updates and restarting the server. In reality, VT-x was actually enabled.

The fix was to delete saved state for all VMs, effectively a power-off.

It looks like the reason for this may have been a CPU microcode update but it's hard to be sure, it's just something that came up in a number of search results.

share

answered 5 mins ago

RomanStRomanSt

5,365134767

add a comment | 

0

I came to this post thinking that VT-x wasn't enabled, because Hyper-V was telling me that "The virtual machine is using processor-specific features not supported on physical computer". This started after installing Windows updates and restarting the server. In reality, VT-x was actually enabled.

The fix was to delete saved state for all VMs, effectively a power-off.

It looks like the reason for this may have been a CPU microcode update but it's hard to be sure, it's just something that came up in a number of search results.

share

answered 5 mins ago

RomanStRomanSt

5,365134767

add a comment | 

I came to this post thinking that VT-x wasn't enabled, because Hyper-V was telling me that "The virtual machine is using processor-specific features not supported on physical computer". This started after installing Windows updates and restarting the server. In reality, VT-x was actually enabled.

The fix was to delete saved state for all VMs, effectively a power-off.

It looks like the reason for this may have been a CPU microcode update but it's hard to be sure, it's just something that came up in a number of search results.

share

answered 5 mins ago

RomanStRomanSt

5,365134767

share

answered 5 mins ago

RomanStRomanSt

5,365134767

answered 5 mins ago

RomanStRomanSt

5,365134767

answered 5 mins ago

RomanStRomanSt

5,365134767