title: VT-x isn't available & No Hyper-V manager on Windows 10
body: <p>When I used <code>vagrant up</code> to boot a VM, I found the following <strong>error ox80004005</strong> (Note that I am using Oracle VM Virtualbox for the virtualization)</p>
  
  <pre><code>kayan@kayan-VirtualBox:~/vagrant/rpm$ vagrant up
  Bringing machine 'default' up with 'virtualbox' provider...
  ==&gt; default: Checking if box 'jhcook/fedora27' is up to date...
  ==&gt; default: Clearing any previously set forwarded ports...
  ==&gt; default: Clearing any previously set network interfaces...
  ==&gt; default: Preparing network interfaces based on configuration...
      default: Adapter 1: nat
  ==&gt; default: Forwarding ports...
      default: 22 (guest) =&gt; 2222 (host) (adapter 1)
  ==&gt; default: Running 'pre-boot' VM customizations...
  ==&gt; default: Booting VM...
  There was an error while executing `VBoxManage`, a CLI used by Vagrant
  for controlling VirtualBox. The command and stderr is shown below.
  
  Command: ["startvm", "769fc6c1-ea8d-46d8-8a7b-16989540d530", "--type", "gui"]
  
  Stderr: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
  VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
  </code></pre>
  
  <p><a href="https://i.stack.imgur.com/CKLuw.png" rel="nofollow noreferrer">Screenshot: VT-x isn't available ERROR</a></p>
  
  <p>I am using <strong>64-bit</strong> Windows 10. My processor is <strong>Intel(R) Core(TM) i7-7500U CPU @ 2.70 GHz</strong>.</p>
  
  <p>To solve this error, I was suggested by someone that I should disable <strong>Hyper -v</strong> on my host windows machine. When I opted to disable Hyper -v feature, I found that there is no Hyper-v in my machine (<strong>strange</strong>!!!)</p>
  
  <p><a href="https://i.stack.imgur.com/DjSOY.png" rel="nofollow noreferrer">Screenshot: No option to enable or disable Hyper-v</a></p>
  
  <p>I then used this command <code>dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All</code> to disable the hypervisor and I found this (Note: I run CMD as administrator).</p>
  
  <pre><code>Microsoft Windows [Version 10.0.16299.125]
  (c) 2017 Microsoft Corporation. All rights reserved.
  
  C:\WINDOWS\system32&gt;dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All
  
  Deployment Image Servicing and Management tool
  Version: 10.0.16299.15
  
  Image Version: 10.0.16299.125
  
  
  Error: 0x800f080c
  
  Feature name Microsoft-Hyper-V is unknown.
  A Windows feature name was not recognized.
  Use the /Get-Features option to find the name of the feature in the image and try the command again.
  
  The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
  
  C:\WINDOWS\system32
  </code></pre>
  
  <p><a href="https://i.stack.imgur.com/yBLZL.png" rel="nofollow noreferrer">Screenshot: 0x800f080c ERROR</a></p>
  
  <p>My virtual machine configuration:</p>
  
  <ul>
  <li>OS: Ubuntu 16.04.03</li>
  <li>RAM: 3072 MB</li>
  <li>Storage: 500 GB</li>
  <li>storage type: VDI</li>
  </ul>