• Technologies

  • Instructors

  • Enabling Hypervisor to auto start in the Boot Configuration Database (BCD)

    If you are getting the following error when attempting to start a Virtual Machine (VM) in Hyper-V, Virtualization may either be not enabled in BIOS or Hypervisor was not started during your computer start up.


    Recently after configuring a computer to dual boot I was unable to start up a virtual machine in the second operating system.  I ran BCDEDIT and determined that there was no entry to start the Hypervisor.  See figure below.


    To resolve the issue you will need to add an entry to the BCD Windows Boot Loader to automatically start Hypervisor when the computer starts up.  Type the following command in an administrative command prompt:

    BCDEDIT /Set {current} hypervisorlaunchtype auto 


    Restart the computer after running the above BCDEDIT command.  Hypervisor will now auto start during computer start up.

    Launch an administrative command prompt and run BCDEDIT to verify there is now an entry to auto start hypervisor.


    You are all set to run or build virtual machines in Hyper-V.

    You may also like:  Using Server Manager to uninstall the MiniShell or Full Graphical Shell to convert Windows Server 2012 R2 Datacenter to a Core Edition

    Until next time, RIDE SAFE!

    Rick Trader
    Windows Server Instructor – Interface Technical Training
    Phoenix, AZ




    See what people are saying...

    1. dawid

      Wow, thanks so much, we’ve been struggling with this for months now. MS support had no clue. You are a life saver! 🙂

    2. Shawn C.

      Worked perfectly on 2008 R2 after reimaging the server to new disks. Thanks!

    3. Rod Funk

      This really helped me out last night after I added a RAID card and external array to a server and Hyper-V would no longer start. Most posts that I saw recommended removing and re-adding the Hypver-V role, but your solution identified the specific fix which is much less risky. Thanks!

    4. Xtina

      As a note for myself for later: there need to be quote marks around “{current}” when running in PowerShell.

    5. Pingback: Recovering from BCD error 0xC000000D with BitLocker and Hyper-V – Chad's Tech

    6. Pingback: Recovering from BCD error 0xC000000D with BitLocker and Hyper-V

    7. Naveed

      I have tried the above solution on Windows 10 Enterprise and got the following error while run the BCDEDIT /Set {current} hypervisorlaunchtype auto command i.e.
      Error: An error occurred while attempting to reference the specified entry. The program issued a command but the command length is incorrect.

    Share your thoughts...

    Please fill out the comment form below to post a reply.