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.

About

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

  • 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!

  • Wow.. Thanks a lot.

  • Eyog Yvon

    Thanks.

  • 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

    ERES EL MEJOR. GRACIAS

  • 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.

  • OMG THANKS!!!

  • 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
    worked!

  • 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.

        • ラミらみ Rami Hamouda

          Thank you man . It really worked for me !!

        • Hotair10

          My hero!

      • 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!

      • 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
        TYPE : 1 KERNEL_DRIVER
        STATE : 3 STOP_PENDING
        (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT : 0x0
        WAIT_HINT : 0x0

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

  • 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.

    Marko

  • 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

    helpful(Y)

  • 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.
    VERY
    VERY
    VERY
    VERY
    VERY
    VERY THANKS.
    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

    https://download.sysinternals.com/files/Coreinfo.zip

    Thanks!

  • 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

          • _neo

            Thanks, will give that a try.

  • 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

    Thanks!

  • Hans Schmid

    Thanks!

  • 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

    Awesome!!!

  • 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!