So, last night I successfully installed XP 32bit and at first I didn’t noticed the 64-bit options missing. But when I tried to transfer data between the host and the guest, I literally started to sweat, and finally gave up.Īfter Googling I came to know “VirtualBox” seems to be what I am looking for. 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. I am noob to Virtual Machines and just trying to dive into the pool. 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 faced the same problem last night on my MSI GE70 Apache Pro Notebook with Windows 10 (圆4). Hopefully this little article will spare you the hours of mind numbing frustration that besieged me for the last few Thank you so much. I hope this helps you – I don’t know if my situation will apply to your system configuration but I wanted to share.
If VirtualBox is only showing 32 bit versions in the Version list make sure: I think I literally pumped my fists in the air when I saw this screen. It turns out, upgrading my hard drive wasn’t even remotely causally related to my problem. Because it used to work before I upgraded my hard drive. I couldn’t have been more elated – something like this might seem trivial to some people but it was really worrying me. When my system came back up, I swiftly logged back into the Windows, kicked open VirtualBox and checked the versions list: Windows quickly displayed a progress bar denoting the removal of the Hyper-V platform and after about a minute prompted me to reboot. Could this be conflicting with the Intel settings in my BIOS? I decided to uncheck the option to see.
It’s the native virtualization component that is available to all Windows 8.1 users. In Windows 8.1 Hyper-V is the successor to Microsoft Virtual PC. I scanned a few options but one in particular was salient: I quickly pressed Windows Key + q to open the Search box and typed in: turn windows features on or off
I wanted to see what administrative Windows features were enabled – perhaps something was conflicting with the visualization settings in the BIOS? I couldn’t figure it out so I decided to poke around the administrator options in Windows to see what I could find.
But since both were already enabled I was utterly flumoxed.ĭo I need to toggle the values? In other words, do I need to disable both options, save changes, reboot, and then enable them again? These were two key options that VirtualBox was expecting. Intel (R) Virtualization Technology was enabled and Intel (R) VT-d Feature was also enabled. In the Security Section, I noticed an option called Virtualization.įilled with a bracing hope, I tabbed over and hit enter but then noticed all relevant settings were already enabled! 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. That’s seriously the only way to get around that one resetting the CMOS won’t fix a forgotten Supervisor password. Thank God I didn’t enable a Supervisor Password or else I would have to replace the system board.
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! Uninstalling and reinstalling VirtualBox made no observable difference so I booted into the BIOS to see what I could find there. This was super annoying because all my ISOs were 64-bit therefore I couldn’t use them until I fixed this problem. This post is going to be succinct and to the point.Įven 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. Today I want to save you the pain I encountered by showing you how to fix a problem I experienced in VirtualBox.
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.īut Alas! Stupidity has a cost and in my case it cost hours of discomfiting nights scouring Google for a solution.
I experienced an extremely nettlesome problem after swapping out my traditional hard drive for a faster Solid State Drive ( SSD).