Menu
I experienced an extremely nettlesome problem after swapping out my traditional hard drive for a faster ( SSD). I, copied over all my software ( but I was too lazy) and then mindlessly enabled a bunch of options that I never enabled before.
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, VirtualBox categorically refused to display any 64-bit guest OSes in the Create Virtual Machine dialog box. 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.
Virtualbox For Windows 8.1 64 Bit Download
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? 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 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. 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. 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. 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.
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. Sports arb software. 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 ?. 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. @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.
Download Oracle Virtualbox For Windows 8.1 64-bit
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:.
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.
The solution was to power up, click escape to interrupt booting, select boot options from the resulting menu, navigate to the boot configuration menu, and then enable 'Virtualization Options', which must be an abstraction of various things including VT-x and AMD-x. In any event, the result is that now I can choose 64 bit RHEL in VirtualBox to hopefully create a CentOS installation within windows 8.1. I will mark this as answered and +1. If another subsequent problem arises, I will just post another question. Thank you again. – Jun 19 '15 at 20:28.