Terms of Use For FixedByVonnie

By proceeding to access fixedByVonnie.com, you expressly acknowledge, and agree to, all of the following:

fixedByVonnie.com is a personal website and blog owned by Security Plus Pro LLC, which is being presented for informational purposes only. The views on this website are solely those of the website owner (and not those of any employer or of any professional associations affiliated with the website owner).  Any views expressed in this website and any information presented on this website, or in any of its blog entries, should not be relied on for any purpose whatsoever other than as the personal opinions of the website owner.  The website owner expressly disclaims any and all liability for any information presented on this site.  The owner of this website and its blog posts shall not be held liable, and shall be held harmless, for any errors or omissions in any information or representations contained in this website, or in any of its blog entries.  The website owner also expressly disclaims any liability for the current or future availability of any such information. The website owner makes no representations as to the accuracy or completeness of any information on this website or which may be found by following any link on this website. The website owner shall not be held liable for any losses, injuries, damages, claims, or causes of action, from the display or use of any information on this website or in any of its blog entries. If you use the information on this website, or on any of its blog entries, you do so solely at your own risk.

Why is VirtualBox only showing 32 bit guest versions on my 64 bit host OS? - fixedByVonnie

Why is VirtualBox only showing 32 bit guest versions on my 64 bit host OS?

I experienced an extremely nettlesome problem after swapping out my traditional hard drive for a faster Solid State Drive (SSD).  I installed Windows 8.1 from scratch using the Product Key, copied over all my software (I probably should have used Ninite but I was too lazy) and then mindlessly enabled a bunch of options that I never enabled before.

But Alas! Stupidity has a cost and in my case it cost hours of discomfiting nights scouring Google for a solution.

Today I want to save you the pain I encountered by showing you how to fix a problem I experienced in VirtualBox.  This post is going to be succinct and to the point.

Even though my Host OS is a 64-bit version of Windows 8.1, VirtualBox categorically refused to display any 64-bit guest OSes in the Create Virtual Machine dialog box.

64-bit OS running 64-bit VirtualBox only showing 32-bit Guest OS

This was super annoying because all my ISOs were 64-bit therefore I couldn’t use them until I fixed this problem.

Uninstalling and reinstalling VirtualBox made no observable difference so I booted into the BIOS to see what I could find there.

I have a Lenovo ThinkPad W520.  As a side note, a few months ago I made another idiotic mistake: I enabled a bunch of BIOS passwords to make myself feel secure but then forgot how to disable them!

Thank God I didn’t enable a Supervisor Password or else I would have to replace the system board.  That’s seriously the only way to get around that one; resetting the CMOS won’t fix a forgotten Supervisor password.  Thankfully, I remembered, the Hard Drive password and the Power-On Password, so after surmounting those obstacles, I removed those passwords and tried to see if there was anything I could enable to make VirtualBox display 64-bit Guest OS versions.

In the Security Section, I noticed an option called Virtualization.

Filled with a bracing hope, I tabbed over and hit enter but then noticed all relevant settings were already enabled!

Intel (R) Virtualization Technology was enabled and Intel (R) VT-d Feature was also enabled.  These were two key options that VirtualBox was expecting.  But since both were already enabled I was utterly flumoxed.

Do I need to toggle the values?  In other words, do I need to disable both options, save changes, reboot, and then enable them again?

Enable Intel VT-d for VirtualBox

I couldn’t figure it out so I decided to poke around the administrator options in Windows to see what I could find.

I wanted to see what administrative Windows features were enabled – perhaps something was conflicting with the visualization settings in the BIOS?

I quickly pressed Windows Key + q to open the Search box and typed in:

turn windows features on or off

Turn windows features on or off

I scanned a few options but one in particular was salient:

Hyper-V was enabled.

In Windows 8.1 Hyper-V is the successor to Microsoft Virtual PC.  It’s the native virtualization component that is available to all Windows 8.1 users.

It was enabled though…

Interesting.  Could this be conflicting with the Intel settings in my BIOS?  I decided to uncheck the option to see.

How to disable Hyper-V in Windows 8.1

Windows quickly displayed a progress bar denoting the removal of the Hyper-V platform and after about a minute prompted me to reboot.

When my system came back up, I swiftly logged back into the Windows, kicked open VirtualBox and checked the versions list:

Yes yes yes!!!!

I couldn’t have been more elated – something like this might seem trivial to some people but it was really worrying me.  Because it used to work before I upgraded my hard drive.  It turns out, upgrading my hard drive wasn’t even remotely causally related to my problem.

I think I literally pumped my fists in the air when I saw this screen.

VirtualBox showing 64-bit versions

The Bottom Line

If VirtualBox is only showing 32 bit versions in the Version list make sure:

  • Your Host OS is 64-bits
  • Intel Virtualization Technology and VT-d are both enabled in the BIOS
  • The Hyper-V platform is disabled in your Windows Feature list.

I hope this helps you – I don’t know if my situation will apply to your system configuration but I wanted to share.  Hopefully this little article will spare you the hours of mind numbing frustration that besieged me for the last few weeks.


Connect with Vonnie on Twitter

Posted in Windows, Windows 8, Windows 8.1 Tagged with: , ,
  • Лоджия

    Thanks so much for this fantastic solution! I have no idea how you figured out that it was Hyper V, but I’m happy you shared it because it worked for me perfectly

    • Do I need to toggle the values? In other words, do I need to disable both options, save changes, reboot, and then enable them again?

    • Do I need to toggle the values? In other words, do I need to disable both options, save changes, reboot, and then enable them again?

  • Nice stuff overall, After some days ago, I was need to install latest Operating system windows 8.1 pro at my notebook, So I install with it from my DVD suit, But with getting its activation, I saw product key was lost.
    I search at yours as well as many other sites to buy it but all were free & blocked from Microsoft. Then One of my friend tell me about ODosta Store
    Where I bought, Which is working well now.

    • Yasir Majaz

      Ap ne apna Ishtihar lazmi ghusaana tha yahan? Topic to dekh lety kam az kam :/

  • Vy0m

    I was struck with this same problem with 1.21 Giga Watts!

    But I had added problem that I couldn’t disable it from “Turn windows features on or off” since it wouldn’t open for some reason. Hence I found a command line to disable it:

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

    and to enable it back again (in case)

    dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All

    Thanks for writing this blog. 🙂

  • Pingback: Ubuntu: Beginning to Walk on Unchartered Territory | Vineet Kumar()

  • Govindaraju Palanisamy

    It worked for me too.. Thanks a lot!

  • Ben

    I suspected the same thing about maybe Windows masking the 64 bit option. Sure enough you’re research made it so much quicker to figure out.
    Thanks for the research … saved a bunch of time.

  • Jim

    You are my HERO FOR THE DAY! (Week!?) Seriously, saved me hours of work. Thanks!

  • Sarthak Vox

    thanks 🙂

  • RK

    thanks Buddy!

    • ZaInT
    • ben

      I use the “uppest” comment so everybody knows this: I had the same issue in Win10 today. Windows Defender has an option “core isolation”. I somehow had this enabled recently. Disabling it solved the issue and I now can use VirtualBox with 64bit guests again. Thanks to the threader and all the commenters that pointed in the right direction!

      • Chetan laxkar

        Also enabled core isolation and tray to all way to slowed problem with VritualBox. Disable after run again properly.
        Thanks !

      • Tony Marcus Cassani

        where is that bro?

  • Wow.. Thanks a lot.

  • Eyog Yvon


  • Bob

    I had this same problem but when I check the things you mentioned they were all set correctly. I enabled and disabled VT-d in the BIOS, saved changes, and restarted and then it worked. Or maybe it was the restart… it works now.

    • Henri

      It was most probably the restart that solved your issue, if you installed a fresh copy of VirtualBox. For some reason, VirtualBox requires this on some PC’s, whereas with VMware Workstation it works without restarting the computer.

  • Thanks bro! You saved a lot of my time!

  • Leandro G Machado

    Thanks, help me a lot! Thank you sir

  • Linda Vanderbaan

    Thanks! I’m just on Windows 7, but this helped with the bios image.

  • Horses Mouth

    Most HP pavillion lap top computers ONLY require to enable in BIOS virtualization in the BIOS setup by entering in to the BIOS setup by post boot pressing Esc + F10.

    • Chintu

      As mentioned, I just needed to enable BIOS virtualization in my HP Pavilion

  • Myyyyyy hero! This saved me a bunch of time, thanks!!

  • Sajid MSH

    Bigggggg thanks Budyy………..thumbs UP 4 u… (Y) 🙂

  • Jorge


  • Chris B

    You sir are the shiz.

  • sirop

    Solved the problem although it was an amd processor in my case.

  • Londeren

    Thank you. It’s very helpful

  • Akul Singhal

    I am not getting any feature as Hyper-V in that box. Please Help!!

    • Henri

      Hyper-V is only included on:
      1) Windows Server 2008 and newer
      2) Windows 8 (Pro/Enterprise editions only) and newer.

      Windows 7 or older did not come with Hyper-V unfortunately, so if you still have this issue it must be something other than Hyper-V.

    • Henri

      By the way, I’m running Windows 7 64-bit on my laptop (I also have Windows 8.1/10 on my desktop) and I had the same issue: only 32-bit options showed up in VirtualBox.

      Since I was running Windows 7, that pretty much instantly ruled out Hyper-V as a problem and I was also 100% sure that all virtualization settings were enabled in BIOS.

      Interestingly enough, I just had to restart my laptop and after that VirtualBox showed all the versions correctly (now even the 64-bit). I forgot to restart my computer after installing VirtualBox. =) Pretty typical of Windows.


  • Nagato

    Thank you so much! That’s exactly the problem and this article is so helpful!!!

  • cybernove

    Im assuming this trouble shooting will work with windows 7 or 8.

  • Paulo Hora

    Hi there! Bringing additional information, I have a scenario where I
    need Hyper-V Management Tools installed for use with Remote Server
    Administration Tools. I just unchecked Hyper-V Platform, rebooted and it

  • Alejandro

    Good evening.

    Under Windows 10 host, running in a Dell inspiron A8 (AMD) laptop, these commands won-t fix the “no 64-bit guest” issue. The equivalent of VT-x under AMD’s processors is AMD-V, and yes, it’s enabled and doubled-checked that no-brainer setting. This exact same laptop ran VirtualBox 64 bit guests when the host OS was Windows 8.1

    Any other tip would be mostly welcome. Thank you.

    • Leonardo Carneiro

      Same problem here =(
      Any news?

    • john

      I have Windows 10 and I found the solution. It sounds like its stupid and pointless but it works. First you open the installer you used to initially get virtualbox (redownload it if you need to), then you click next and then repair, once it finishes the repair you then restart the computer like it asks, finally you must delete the shortcut on your desktop. Lastly you go grab a new shortcut, do this by going to C:Program FilesOracleVirtualBox and at the bottom you will see virtualbox.exe and right click it and click send to: Desktop(shortcut). Your welcomz 🙂

      • Adel

        WTF I was like “Is he trolling?” but still I tried, worked without even needing to restart! thanks a lot bro, worked on w8.1 x64. 😉

      • :O this totally works. All it took for me was to choose the repair options and then that was it. Thanks John!

      • Ibrahim Jalloh

        How do you open the installer you used to initially get virtualbox?

      • Tom

        Wow thanks. Such a stupid thing to need to do but totally fixed the issue. Though you don’t need to restart or get a new shortcut only run repair.

      • Damian Salcedo

        Thank you John and Alejandro, that worked just fine!!

      • Damn son!

        Dat works!

      • Nick

        Cant believe it was that simple, thank you!

      • Mickael Vest

        Same here, seems too simple to be true but it worked like a charm, without even restarting, thanks !

      • Unknown

        IT WOKRS!
        Thank you very much.
        (Anyway its so stupid bug…)

      • Baz

        I didn’t need to reboot, or do the shortcut stuff, just:
        install >> repair >> done.

        • I needed to reboot, but it worked on win 8.1

        • Aadi

          Thanks a lot, it was so easy and works for me

        • Jadwin Manuel

          I’ve been trying for the past week to see my 64 bit versions of kali. You’re my based god.

        • Or Ben Ari

          how do i get to that install >> repair option?

          • Kaitlu

            Right click on the Virtualbox install file >> “Run as Administrator” >> “Yes” >> Repair, then follow prompts.

          • ZaInT
        • ラミらみ Rami Hamouda

          Thank you man . It really worked for me !!

        • Hotair10

          My hero!

        • Noa

          ROCK ON!

        • Mau. cavazos

          EXCELLENT That was perfect thank you

        • ZaInT
        • Riivo Must

          This is absurd! I did repair and 64bits appeared! Thank you so much 🙂

          Even now, Win10 Home 1809 64bit + VirtualBox Version 6.0.6 r130049 (Qt5.6.2).

      • Randy Katz

        Unfortunately, this works! I hate solutions that have no reason but thanks so so much!

      • Quake591

        Thanks 🙂

      • sammath

        Hey dude, i did exactly the same way you did, but it did not work///: I have windwos 10. i could not fixed the problem unfortunatelly. please help?

        • Sumanth Lingappa

          Same problem, it didnt work for me.. repair>restart>run the virtualbox from c:programs..

          Any luck for you?

      • chris freer

        Great been days trying to figure this out. Done the repair and there it was on my virtualbox finally 64-bit options. thx

      • anon

        worked as well on a windows 7 ultimate host.

      • Spearing the Bearded Clam

        Works like a champ win10 ent x64.

      • Aloxy

        I have tried all of these methods, once I restart my computer, it goes back to being 32 bit list. Even when the list is 64bit before I restart, it gives me a kernal error: https://gyazo.com/068bfec66719ea1420a8faa43dba2088
        please help me Im using this for my college class and it is very important.

      • jarlave

        I thought, why should it help to delete the shortcut and make a new one? Tried it, wtf it worked…

      • abac00s

        Thanks! You saved me a lot of time.

      • jconch

        Thank you so much. Been trying to install a Yomsemite VM for a little while but this worked beautifully.

      • palsu dop

        Its kind of pointless, but it worked! I didn’t need to restart also

      • Mayank Katiyar

        It worked after reboot only, though i dint delete shortcut. It was really helpful. Tnx John

      • Moh Zah

        Wow thanks worked for me without reboot and shortcut 🙂

      • Kaitlu

        You are fantastic. I uninstalled, reinstalled, check BIOS, verified HyperV was already disabled (it was), then hit my head against the wall 3 times. Found this, repaired my install, even though it was freshly installed, and fixed the issue. Now I can get my SBS2011/Win Server 2008 R2 lab going!

        • Noa

          SAME, AND the repair doesn’t work unless I reboot.

          • Kaitlu

            It’s been a while, but I managed to fix this. Now that I’ve been using Hyper-V, I actually prefer it (and it’s necessary to learn if you plan on taking the MCSA Server 2012/2016). Verify that your processor virtualization flag is on in the BIOS, save and exit for good measure (usually F10), and boot into Windows. Install or use Hyper-V and your life will get better. Let me know if you have problems and I’ll help troubleshoot.

          • Noa

            It was acting whacky for me….went to use Hyper-V, no option to install it…so I rechecked the BIOS, my settings didn’t save. lol (crappy HP BIOS)

            So I turn VT on again and it works fine now. Thanks!

          • Kaitlu

            Glad to hear it. Same thing happened to me on my last system. I’ve since built a server and moved on to a real lab.

      • Tapa Dipti Sitaula

        Awesome! Thank-you!!

      • RandomGuy

        Dude, U just saved the day

      • _neo

        This doesn’t work for me with 1.5.14 on Win10 1511 x64:

        NtCreateFile(DeviceVBoxDrvSub) failed: 0cx000000e
        STATUS_NO_SUCH_DEVICE (161 retries) (rc=-101)

        Running ‘sc query vboxdrv’ yields:

        SERVICE_NAME: vboxdrv
        WIN32_EXIT_CODE : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT : 0x0
        WAIT_HINT : 0x0

      • Rulezthenet

        Really it was bullshit … Thanks to you Buddy 🙂
        I didn’t need to reboot my system .. it works just after repair work done.

        To repair VM – Go to VM install exe fie —> right click run as Administrator —> repair ( You may uninstall previous one if you want )

        Thanks again !!

        • Andrew Zapata

          wow Thanks Dude

      • ZaInT
      • JMXHD

        My HERO!! If you have a Paypal, I would love to donate you!!!

      • Edinan William

        wtf, it works, tnx

    • OMG just worked without reboot (Windows 10 1511 x64)!!!! Thanks a lot

    • ZaInT
  • Anurag Vasanwala

    Dear Vonnie,
    What a coincidence. I have the same machine ThinkPad W520 and was facing the same problem. Your article worked for me.

    Thanks a lot 🙂

  • Sandeep

    Thanks mate. In my case I have a Lenovo ThinkPad (E550) but it has Windows 7 on it.

    I’ve enabled both the settings in Virtualization in BIOS and it works.

  • Pingback: Enable VT-x for VirtualBox | revect.de/()

  • Snookiemon

    your fix worked like a charm. Thanks a million.

  • Carlon

    Thank you!! I spent days trying to figure out this problem.

  • Eric Paulson

    You’re the man! Wanted to tell you all how to do this on a Lenovo ThinkCentre with Intel processor, Windows 7, and disk encryption software. The disk encryption software hijacks the standard boot sequence, so the F1 key doesn’t get you to the BIOS from a cold boot. Instead, boot normally, then run the Repair option from the installer (not sure it’s necessary, but I did it following one of the suggestions below), then do a Restart as suggested by the program). Press F1 to get to the BIOS, ENABLE the Intel Virtualization feature in the Advanced menu, F10 to save the BIOS setting change, and then continue with the normal Boot sequence.

  • Yasir Majaz

    @vonnie Thank you so much.

    I faced the same problem last night on my MSI GE70 Apache Pro Notebook with Windows 10 (x64). Now I am in office and cant try out your tip right away but I know this is definitely the problem because I activated and used Hyper-V for XP just a day ago.

    I am noob to Virtual Machines and just trying to dive into the pool. I decided to give “Hyper-V” a shot because I thought it is “by Microsoft” so it must be more “fitting” with Windows 10, rather than any third party VM. But when I tried to transfer data between the host and the guest, I literally started to sweat, and finally gave up.

    After Googling I came to know “VirtualBox” seems to be what I am looking for. So, last night I successfully installed XP 32bit and at first I didn’t noticed the 64-bit options missing. But after the XP, when I tried to created a Virtual Machine for Ubuntu, I was astonished to see there was no 64-bit option for any Operating System. Thanks God, and thank you Vonnie, now I know how to kill this worm 😉

  • Pingback: Sunday school session on VirtualBox | Just a blog()

  • name

    god bless you broha!

  • Akshay Cm

    Thanks dUde Thanks a lot i am so happy!!! 🙂

  • Nikolay Morozov

    Hey man, thanks! Didn’t think about Hyper-V)

  • Fabrício Severo

    Thank you very much for this post. It helped me solve a problem i had for two weeks.
    Only one thing more to consider. In my case, i checked all this ocnfiguration, but the problem was that my system was with “secure boot” enabled. Maybe one more item to test and add to your checklist.
    Thank you again.

  • Michael Whitis

    Thank you so much for this! Saved me wasting my Christmas holiday trying to troubleshoot!

  • Pingback: VirtualBox is missing x64 version of guest OSs | Marko's Tech Blog()

  • Amogh Patel

    You Rock!! Totally fixed my problem. Thank you so much, I was so annoyed 🙂

  • markogts

    Thank you! Had a similar problem (64 bit linux version not booting from CD). Windows 10 home edition does not have the hyper-V, but the bios had to be changed. Thank you again.


  • Kryšpín Frýsa

    Deleting Hyper-V helps me!

  • Pingback: [Ubuntu #0] Cómo preparar una máquina virtual (en Windows) – +140()

  • Saliha Arif


  • tmooredba

    Brilliant. I had exactly the same issue. When I saw your mention of upgrading to an SSD, I thought yes! That’s exactly the thing I did before this happened. Then I read down and realised it wasn’t related to my issue either. After upgrading the HD I reinstalled Windows, and mindlessly installed Hyper-V thinking ‘yeah I’ll give this a go’. Big mistake! Thanks for posting this, it has saved me a serious amount of time! 🙂

  • RileyRampant

    you saved me a lot of head-scratching. danke shoen!!!

  • Thanks. This helped a lot.

  • Danny

    This is like the most useful post I’ve seen in my life, I’ve lost hours trying to solve this issue! Thanks!

  • ny3ranger

    Great post. Solved problem in 5 minutes due to your struggle.

  • Gedielson Araujo Silva

    Thanks man.
    Hyper-V is not compatible with Virtual Box and VM Ware, afer uninstall Hyper-V my Virtual Box works.

  • Tixel

    Eternal gratitude!! Same problem here after installing a bunch visual studio stuff. And it was totally confusing, because this tool told me VT-X was enabled



  • Polyterative

    It’s working now, thank you.
    Although I wonder why do I need to disable Hype-v support in Windows 10.
    Any withdrawals?

  • prabhkaran malik

    hello sir
    i went through this guide of yours and did everything you said but i was not able to find the hyper v option in the enable or disable windows features pls help and reply asap
    thank you

  • Santosh

    Thanks !!! it is now working.

  • Ashley Crookes

    Thanks for the tip, I’m going to go and try this now on my Asus laptop as I also can only see 32bit versions. I want to test out Win10, but not ready to upgrade just yet!

  • mountassir

    i have win 10 X64 but virtual box show just X32 what is the solution to fix that probleme

  • Abdul Aleem Shaikh

    This works like a charm.
    Using Win 7 (64-bit) on a HP Pavilion m6 laptop, had to make sure of the following:-
    1) Windows Feature named “Windows Virtual PC” was Disabled.
    2) In the BIOS settings, under System Configuration, “Virtualization Technology” was Enabled.

  • Colin D

    Thx, worked like a charm on Lenovo T440p.

  • Milind Joshi

    Thanks a lot Vonnie. That resolved my issue. I am running Windows 10 trying to install CentOS using Virtualbox. I too couldn’t see 64-bit option. My problem was with the BIOS settings. I had to Google to figure out how to get to those settings because it’s been a while I did that. After turning ON virtualization option in my BIOS, I am now able to see 64-bit options as well. Although, I didn’t see Hyper-V platform options in my Windows features dialog box.

  • Renan Rufino

    Thank You so much.. I’m using Hyper – V but Virtual Box too. Solved for me, thanks!

  • docesam

    THANK YOU ,it worked for me !

  • Ed Martin

    Just wondering why you would want to use virtualbox if you have hyper-v enabled? I have used both in the past, and have recently started experimenting with server OS in hyper-v and they work really well. I have also installed Linux inside hyper-v without a problem.

  • Voltaic Shock

    Thanks for this but my issue is I want to have Hyper-V installed and also use VirtualBox with 64-bit OS. Sadly this doesn’t seem possible

  • Pingback: Choosing and Using a Virtual Machine Program, Part 1: Running Linux Mint 17.3 as Guest | Ray Woodcock's Latest()

  • Ahmad Moemen

    I don’t have Intel (R) VT-d Feature in my BIOS…

  • Costa

    Thank you!

  • roystreet

    Hey Vonnie — Thank you ever so much!! I couldn’t figure it out either & I didn’t even think to change that. I only needed to change it in Windows, I didn’t need to go into the BIOS.

    Reference: I’m running a Surface Pro 3, i5, 128GB SSD, 4GB RAM…with Windows 10

  • Dwayne Warwick

    omg thank you so much

  • MilesTFox

    The missing ‘Why this works’ is as follows:

    When you enable the ‘virtualization’ setting in the bios, that enables a virtual machine ‘hypervisor’ to see that this computer supports hardware cpu virtualization. ‘VT-d’ extends this to allowing direct use of some kinds of hardware, like the graphics card.

    Only one hypervisor can use these capabilities at a time. A hypervisor manages how virtual machines use the computer’s cpu and ram. A hypervisor enables hardware-level cpu emulation, which is usually much faster than software emulation.

    Hyper-V is a hypervisor, used for Microsoft’s own virtual machine software.
    Virtualbox installs it’s own hypervisor to support 64-bit OS’s.
    Virtualbox can run 32-bit OS’s in software emulation mode, which is why they showed up.

    Turning ON the bios settings and OFF hyper-v, makes those capabilities availiable for Virtualbox to see/use them.


    To those who didn’t see any change till you reinstalled/repaired Virtualbox:

    When installing, Hyper-V had the virtualization capabilities in use by itself, so Virtualbox could not use them. Virtualbox thus did not/could not install it’s hypervisor.

    Reininstall/Repairing Virtualbox with the settings right and hyper-v off, allowed it to see the virtualization support and install it’s hypervisor.

    • I have virtualization on and Hyper-V completely off yet no 64bit option in VirtualBox. Thoughts on what could be the issue or troubleshooting steps?

      • _neo

        Same here, on Win 10 Home. Ever get it to work?

        • Yeah, basically switching between Hyper-V & VirtualBox manually and requiring a reboot each time I want to use one or the other:
          bcdedit /set hypervisorlaunchtype off –> to enable VirtualBox fully
          bcdedit /set hypervisorlaunchtype auto –> will restore Hyper-V

        • ZaInT
      • Daedalus

        I had to run virtualbox as administrator to get it to show up as no Hyper-V option was available to me. Not sure if that was the issue, but rebooting the machine to clear the currently active programs and immediately setting it to run as administrator by default solved my issue.

      • Joshua K

        I found that the BIOS setting for “Intel HT” has to be OFF as well. This is for my Gen-2 i5 CPU. Apparently VBox needed to use true cores, not Hyper-
        Threaded cores.

      • ZaInT
      • YT

        The intel virtualization technology in the BIOS of your computer must be turned on, not off.

    • ZaInT
  • Pianogamer

    Wasted so much time making a 32bit linux, installed a bunch of stuff, cloning git repos, then when I came to Bazel it was “not supported”, turns out it requires 64bit… which I of course would have if it wasn’t for this BS.

  • Danger Man

    I am not the admin of this PC, I dont even know the key to my BIOS, and for a few days, im going to have to leave the bios alone because this: it was broke

  • Gavin Edwards

    THANK YOU!!! This totally fixed my issue. Freakin’ HyperV of all things! I use it a work all the time, but I don’t remember it ever conflicting with VirtualBox. the only thing I can attribute it to is that we only run Intel at work. I run AMD at home. This is the first instance of Vbox that I have run on Windows 10 with this motherboard. Every time I started my 64-bit vm of Linux, it would error out. Disabling HyperV did the trick. Thanks again.

  • bot bot

    Thank you so much. This worked for me!!

  • Francisco QV

    thank you so much man. Worked like a charm.

  • Sixfootjames

    Thank you, thank you, thank you!

  • This worked for me on a Thinkpad Yoga 14 bought in 2016 (Windows 10).
    On this laptop,
    The Hyper-V platform did not appear in the Windows Feature list, so presumably it was disabled.
    But Intel Virtualization Technology and VT-d were both disabled in the BIOS (Security tab). After enabling them the 64 bit options appeared in VirtualBox.

  • Chunk TV!

    What about for users of AMD?

  • Hector
  • McLovin

    Lots of reading to get to the fun part.

    Thanks MilesTFox for the explanation of why things are the way they are.

  • Anish

    Thanks a lot !!. It worked for me too.

  • For some reason the latest Surface Pro 4 firmware blocked this entirely. I removed Hyper-V and still get BSOD on my old 64bit guests.. no capability to run VMs in VirtualBox at this point. can’t seem to find anyone posting repro issues..

  • Erek Lazar (Pockmeryn)

    Tried to follow the instructions, but my list under ‘turn windows features on or off’ is completely missing Hyper-V (and some of the others) altogether – How do I fix this? I want to run 64Bit VM’s just like everyone else coming to this topic. My host OS is 8.1 64Bit in this case.

  • keepsontickin

    Succinct and to the point?

  • Shawn Paul Neckelmann


  • Hans Schmid


  • disqus_6rbIUXsxpY

    This is great, and deservedly at the top of my Google search for this issue. Great article and extremely useful!

  • 3N1GM4

    Disabling Hyper-V worked perfectly for me on my Surface Pro 3, thanks!

  • Adam S

    Nice. For me, it allowed the 64 options simply by enabling Virtualization in Bios. No Windows 7 settings changes were needed.

  • Cfem

    Thank you very much you saved me a lot of hours!

  • abdulaziz

    i have same problem can anyone give me the link to install virtual box 64 bit

  • Ashtez

    Thank you !

  • Kevin

    Thanks! it work well and now i can install 64bits

  • Techngro

    The article itself didn’t do much for me (I had already tried those things), but the comments section got it working finally. So glad you wrote this and glad I came here. 🙂

  • Kenyandiasporalinkdotcom


  • Imani

    Hola! I don’t know what I did (as for some reason my BIOS looks very different from your screenshots), I’m thinking it might’ve been repairing my VirtualBox download, but I got it to work!!! *cue happy dance* Thank you!!!

  • Guy Rich

    Thank you vonnie! It would be nice if VirtualBox.org posted this fix on their website.

  • RobertKarlsson1

    Thanks you!

  • Ayesha Williams

    I had this same issue and just now I followed what was said and it resolved my issue. If you are having this same issue I would highly recommend that you do check your BIOS and make sure everything that is needed to be enabled for your virtual box is enabled.

  • Henry

    I love e you you beautiful person

  • 손기석


  • mp arthur

    I am having the same issue ie. my laptop’s operating windows is 64 bit but the VirtualBox only displays those 32 bits.

    I am unaware to see Hyper – V in the turn on or off Window features.


    Your advice is welcomed.

  • Darn Tootin

    On a Windows 7 host, I fixed the issue just by re-running the installer and selecting the repair option.

  • Excellent.
    I was just having this problem
    And no documentation was leading me; not even close to this conclusion
    Thank you so much.

  • Matus

    I have older BIOS (2011) and there is only one setting for Virtualization technology, which was enabled and Virtual Box showed only 32 bit option. When I disabled virtualization setting in BIOS, Virtual Box now offers 64bit!

  • Kaushal

    Hello sir ,
    I have Lenovo g50 and os window 10,
    I want to install kali lunix on Oracle vm virtual box ,but it show “this kernel required an x86-64 ,but only detected an i686 cpu.unable to boot please use kenel appropriate for your country.”
    Please help me to fix it.

  • Rafał Gąsiorowski

    Thank you for this article! Helped me a lot! 🙂

  • Bryan See

    Mine too, VirtualBox has been showing only 32-bit ones, rather than 64 bit. And attempting to start them results in the “SYSTEM_SERVICE_EXCEPTION” BSOD.

  • Gokulnath

    Issue solved 🙂

  • Sanjay Marwal

    Thanks buddy… You saved my time… appreciate your effort

  • Alexander

    Great! The reason has been found. Thank you!

  • Dodison

    my host os is 64-bits
    Intel Virtualization Technology and VT-d are both enabled in the BIOS
    The Hyper-V platform is disabled in your Windows Feature list
    but it’s still not working :/

    • SlowSteadii

      Did you ever figure this out?

  • Sahil Mahale

    Thanks man’s , I was having the same exact problem

  • Johan Steyn

    Thank you Sooooo much!!!

  • Roger Tranchez

    Thanks a lot, worked ok !

  • How about AMD?

  • Ismael Santana

    Many thanks Vonnie, it works for me. In my case, Windows 8.1 and Asus UEFI Bios, the configuration was:

    Advanced Mode (F7) > Advanced menu:
    – CPU Configuration > Intel Virtualization Technology: changed to Enabled
    – AdvancedSystem Agent (SA) Configuration > VT-d: changed to Enabled

    I also checked the Hyper-V. It was disabled.


  • Yannis M.

    Thanks for this! 😉

  • Ahmad Raza

    in windows 7 i have no Hyper_v, what should i see else?

  • Andrew Kvochick

    Thank you!

  • Lucas Coelho Figueiredo

    It`s so counter intuitive! Thanks for posting about this! Really helped me.

  • Marián Miklušák

    Great. Help me too. And I have also finally found out how to enter BIOS on my Lenovo Ideapad. Nothing like F2 or something, there is a button on the side of the laptop, that you have to press with a pin or something 😀 😀

  • Dickie

    Thank you – helped me out 🙂 +1 internets….

  • Sam McKenney

    Hell yeah! I was stuck with the same issue. Checked my BIOS and, sure enough, virtualization settings were not set as they should be. I changed those and VOILA! 64-bit OS enabled in VirtualBox. Thank you!

  • Fattea

    Thanks alot man, worked just fine for me (Intel Virtualization was disabled in the BIOS).

  • Sumit Negi

    Yes yes yess
    It works i am facing this problem from long time. Now i can install ubuntu on my laptop

  • Saúl Nogueras

    I love you

  • Awesome, thanks so much!

  • Niv Froehlich

    Brilliant! Can’t thank you enough!!! (Solution worked on Thinkpad T420 once the virtualization features were enabled in Thinkpad Setup).

  • Paul

    Thank you for this, saved me quite a lot of time! It was Hyper-V which I used before and was still enabled. As I have imported a 64-Bit VM guest and when I tried to start it, my host system ended up in a bluescreen. When I tried to create a new VM, I recognized that there was no option to create a 64-Bit VM. Now, with Hyper-V beeing disabled, everything works as expected.

  • Karol Zmyslowski

    It really works! Thank You! 🙂

  • Remty

    That worked wonderfully for me, thanks!

  • thank you. this was really helpful

  • Andrei Blagaila-Lazar

    Dude you saves my ass. I lost one week trying to figure out why it had this problem

  • mohammad karam

    Thank you so freaking much !

  • Thiago Ztt

    Thank you!!

  • Michal Spyrex Korchaník

    Thanks a lot!

  • nadjim debabi

    BOUSLLAM 19000

  • angngima sherpa

    can anyone plz help me i cannot find virtualization in my laptop.acer aspire


  • I am still getting same error

    • Κωνσταντίνος Κ.

      maybe you try from x86 system, you need x64 host 😀

  • Johaness

    didnt’ work here

  • Najam Pratapgarhi

    Very Good Man..

  • ZaInT

    Thank you for giving us a fix that works, there is no logic to this error and I would never have fixed this on my own

  • Asim Ali

    It worked for me.. saved me a lot of digging around.

  • Barry McDermid

    I went through all the options with no success on Win 10 (Bios options on, hypervisor definitely off, virtual box installed & repaired with Admin).

    Finally it was DeviceGuard. I went into the registry and turned EnableVirtualizationBasedSecurity from 1 to 0 and restarted.

    under ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlDeviceGuard

    Then my virtualBox started showing 64 bit items and my 64 bit VM’s worked! Hope it helps somebody!

    My original post detailing all I tried is here https://forums.virtualbox.org/viewtopic.php?f=6&t=87237&start=15#p417501

  • Eoin Gibbs

    I’m having a similar issue on Dell Optiplex 3040 PC (Win10 x64 OS).
    Have deleted VirtualBox, reinstalled, repaired etc – no luck.
    Have changed virtualisation settings in BIOS (everything enabled) – no luck.
    Windows features -> Hyper V (disabled) – no luck.

    Any help would be greatly appreciated.

    • Fatin Fatima Abdullah

      Hi guys, Im facing the same situation. 🙁 any help would be appreciated..

  • Holmack

    Thank you for the help, I was having the same issue here, and now it’s working fine.

  • Mohammed Umair

    I neither have hyper-v nor virtualization in my dell laptop.
    what to do

  • vignesh ghantasala

    nice work finally worked thanks bro

  • Joseph Leung

    can you say this in english
    cause i dont understand

  • Murillo


  • Note I had to also disable the Windows Hypervisor Platform feature before 64 bit guests were available again. I had VirtualBox installed, decided to try Hyper-V for my use case, then switched back on Windows 10 Professional.

  • Balaji N

    Thank you very much sir. I owe you a lot. But, My bad deleted two machines as i felt useless 🙁

  • GogozzRicky Wilfred

    what about windows 7 x64, no Hyper V in features ,so how can i solve the issue with vbox x32 version only to x64?

  • bad94

    perfect thanks

  • Yassine ALOUANE

    Thank’s, you saved me a lot of trouble

  • Mmola Milford Chithime

    Great advise. Thank you

  • Sergii

    +1 like

  • Alexander Huba

    Intel Virtualization Technology was disabled in BIOS. When I enabled – it started to show 64-bit section, thanks for the article.

  • YT

    This helped me a lot. Thanks a bunch – now I can practice my *cough* “ethical” *cough* hacking, again 😛

  • Coo coo

    Tnx for story.

  • Bidyadhar Barik

    My Laptap have dell latitude 5580 model with OS 10 and i installed oracle vm virtual box and enable all Intel (R) Virtualization Technology was enabled and Intel (R) VT-d Feature was also enabled. it’s showing 32 bit only not showing 64 bit. please help.

  • Amanda Feddon

    FINALLY!! Thank you!!! Worked perfectly.

  • Daniel Roe

    Thank you so much! Whew! Big help

  • King Chuba

    Thank you so much, i disabled my Hyper-V and it work!!

  • leviarrion felix (Teh Neon 10

    I actually have a 64-bit Windows 10 and I still have 32-bit virtualbox. *sigh*
    And I can’t find HyperX. What is this? A 32-bit Windows 10 or something?

  • Ian Mckee

    It all started when MYOB wouldn’t work with Win 10. I turned to Virtual Box for Win 7 but only had 64 bit disk and Virtual box was only 32bit. Spent the day trying to get hold of a Win 7 32 bit disk but when I did I had no valid code. When I read your fix I was dubious, changed the AMD to enable in the bios, Hyper-V was already disabled, and your fix is awesome! Wish I had read it at 10am instead of 6:30pm. Thank you, thank you, thank you.

  • Пётр Двухреченский

    Thanks for sharing this! I literally pumped my fists in the air when I found this post!

  • Dominika

    Thank you! 🙂

  • Thiago Nascimento

    Thank you!!!

  • ftey2000

    saved me a lot of hours. Many many thanks

  • Avatania

    Guys don’t forget to disable the Windows Hypervisor Platform too when disabling the Hyper-V via Turn Windows features on or off

    • ben

      What do you mean by this? I have the problem that my Hyper-V is UNchecked already. So I suspect something else is maybe still running, though.

      • Avatania

        Disable two features on “Turn Windows features on or off”:
        1. Hyper-V
        2. Windows Hypervisor Platform
        for me i can’t get it to work if only uncheck Hyper-V, i must also uncheck the Windows Hypervisor Platform.
        I use amd ryzen 3


    Thanks man!!

  • Morten Nørgaard

    Hats off!

  • Stewart Andrews

    Brilliant, thank-you.

  • Grant H

    I dont have hyper-v on my computer and I have VT-d enabled, help please

  • Aizaz Khan

    virtualizationn in bios was my issue .. I enable vtx virtualization and voila..!

  • David Hovsepyan

    Thank you very much! In my case BIOS’s options in `Virtualization` tab had been set to `DISABLED`.

  • Wellington Oliveira

    thank you man! you save the day!

  • Xin Inertia

    oh my god same , i also have lenovo , cry , it took me a lot of time cry

  • SamVision

    Didn’t work for me.

  • thanks for the info

  • profile4me

    Yeah!! Thank you guy!!

  • Very Thanks

  • dope

    this doesnt fix my problem. disabled hyper-v went into bios enabled necessary settings booted up virtual box … still wont let me using windows 10 pro

  • Hybris91


  • Raghuveer Singh

    Using these captivating and excellent Thank You Memorial Day Thank You Quotes you can pay profound esteem and appreciations to all your military personnel and give thankful tribute for their selfless efforts.

  • Raghuveer Singh

    Have a look at these sweet and adorable Memorial Day Images 2019 to download and share with everyone out there!! And, don’t forget to celebrate the day with extreme joy, enthusiasm, and glory.

  • blackjoker17

    Run this in an elevated command prompt to ‘enable virtualization’:
    dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

  • Troy Holman

    i found this is 2019 and it helped. just wanted you to know if youre still there lol, that you’re still helping people

  • Daniel De Paula

    Thanks, worked here… in my case, I had it disabled in the BIOS and on Windows Features as well!!

  • groot

    Thank you!

  • Pradeep Thakur

    Thank you so much buddy!https://hugsforsandyhook.com/

  • Pradeep Thakur
  • It is a very valuable information. Thanks for sharing this information.Check Here

  • Thanks for sharing this information. I love your site and i visit your site daily.

  • Brek_kapitany

    Turning on Intel Virtualization in BIOS indeed solved this problem for me ( and also the problem of VirtualBox getting stuck on the Windows 10 install). Many thanks.

  • Thank for sharing. this is very important information.

  • E S

    Thank you so much.. Same exact issue with my Thinkpad after switching to SSD !!!

  • good info man.

  • Jayesh Potnagari

    thanks a lot bro…!! I was getting mad over it and as there wasn’t any article or post available on this issue over the web…and suddenly finding this post of yours seemed to me nothing less than finding a Hidden treasure..!! Thank you

  • Paul

    Wow ok, that worked

  • Loki Deablo

    Worked perfectly

  • Nice Information

  • thanks for sharing this information

  • Raymond Thompson

    Thanks heaps for this. It worked a treat for me.

  • Smile

    Thanks a lot, really helped me out!

  • egbdisqus

    In my case I changed the Hyper V first. But no success. So I noticed BIOS that Intel virtualization was disabled in the BIOS

  • Nice article

  • girish ps

    Thanks a ton man, you saved me a day. I had the same issue and your resolution fixed it for me.

  • thanks for info.
    Orthodontist India

  • Marcin

    You are a legend, my friend!

  • Thank you very much you saved me a lot of hours!

    We have a Calendar Wishes Images and 2020 printable calendar for everyone. Whether you’re looking for a printable blank calendar or you need a calendar with holidays to print, you can download it for free from here. Printable Calendar, Blank Calendar, Calendar Template, Calendar Holidays, Holidays Calendar, 2020 Calendar, Calendar 2020 all are available at this site.
    June Printable Calendar
    July 2020 Calendar

  • We have a Calendar Wishes Images and 2020 printable calendar for everyone. Whether you’re looking for a printable blank calendar or you need a calendar with holidays to print, you can download it for free from here. Printable Calendar, Blank Calendar, Calendar Template, Calendar Holidays, Holidays Calendar, 2020 Calendar, Calendar 2020 all are available at this site. http://bit.ly/34tJluT
    July 2020 Calendar
    August 2020 Calendar
    June Printable Calendar

  • Emad Elsaid

    I had the same issue but for AMD ryzen processor and the solution was the opposite
    1- make sure the cpu virtualization is enabled in UEFI
    2- make sure the hyper-v is installed on the system

  • Mert Gulsen

    Thanks a lot !!.

  • nice information. thanks for sharing this. Home Page

  • Adam K

    I have an issue with the latest Windows 10 updates as of 17/2/21 borking my ability to create 64 bit hosts.
    – I have enabled Virtualization in my bios (VT-d)
    – Checked Windows Features and enabled: “Virtual Machine Platform”
    – Made sure “Hyper-V” is disabled in same section

    64 bit hosts were available prior to the latest update, and are now, no longer available, has anyone else had this issue, or is it just me?

  • Deepshika kasamSetty

    the virtualization technology option for enabling is greyed out what is the solution for this?

  • Ritik

    The best article which we fully thank to their authors & such this great website. Aslo cheack this amaizng ie also

  • Ritik
  • Lineth Arjona

    Thanks a lot! Everything is fine.. now showing 64bit ver

  • Seneca

    For me this did not work, as I needed to go to Control Panel/Programs and Features/Turn Windows features on or off/ and turned Virtual Machine Platform on or check the box. After this I restarted my computer and when I went into the VM VirtualBox all the 64bit operating systems appeared.
    I hope this helps.
    Good luck everyone!

  • Ahsan

    I’m a student and gamer so recently I installed Windows 11 but found some runtime issues so while contacting to Microsoft they told me to activate my operating system but their prices were high so I searched and Google recommended me Takenbest site: https://takenbest.com
    where I found Windows 11 at about 60% off with lifetime warranty and support. Now I bought and have a licensed windows 11 so I want to recommend it to others too.