Windows 10 64-bit processor, can only select 32-bit versions

Discussions related to using VirtualBox on Windows hosts.
Post Reply
ben_layton
Posts: 1
Joined: 21. Sep 2015, 10:55

Windows 10 64-bit processor, can only select 32-bit versions

Post by ben_layton »

A few of us are having problems with the above. Seems to be a problem when upgraded to Windows 10. We have 64-bit processors but can only select 32-bit versions from the drop down. We're using version 5.0.4.

Any workarounds?
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Windows 10 64-bit processor, can only select 32-bit vers

Post by mpack »

alex zhao
Posts: 1
Joined: 21. Sep 2015, 12:55

Re: Windows 10 64-bit processor, can only select 32-bit vers

Post by alex zhao »

I have the same problem.
I'm sure my CPU supports Intel visualization technologies, and it worked before I upgrade to Windows 10. My friend also gets the same problem, his CPU is the latest generation of Inter I5, which surly supports visualization.
This must be a compatible bug for Windows 10
loukingjr
Volunteer
Posts: 8851
Joined: 30. Apr 2009, 09:45
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: just about all that run

Re: Windows 10 64-bit processor, can only select 32-bit vers

Post by loukingjr »

FWIW, a CPU may very well support virtualization but it has to be enabled in the BIOS.

I am running 4 64bit guests on a Windows 10 host so it doesn't appear it "must be a compatible bug for Windows 10". You should read the entire thread. There are other reasons even if VT-x/AMD-V is enabled.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Windows 10 64-bit processor, can only select 32-bit vers

Post by mpack »

If 64bit support was previously working on the same host PC, and failed when the host was upgraded to Windows 10, then plainly some software has been installed which contends with VirtualBox for access to the virtualization features. This is dealt with in the linked FAQ.
Post Reply