Windows7 64-bit cannot create linux 64-bit visual machine

[GotoAZ]

After installed VisualBox 4.3.10 on Win7-64, I find I cannot create new visual machine with 64-bit linux, like Ubuntu 64, etc.
All items in drop down list are about 32bit. It is also for other OS, for example, Windows, Solaris, ...
How can I create 64bit vpc on Win7-64 with VisualBox?

Thinks!

[mpack]

FAQ: I have a 64bit host, but can't install 64bit guests.

[Dwalin_7]

Same problem here on Win 8 machines : the list of OS at the creation of a new VM only contains 32bits versions. Since it doesn't work better on win 7, it's not hyper-v's fault as suggested in the FAQ you linked.

We tried downgrading to several older versions, with no success.

No problem in the BIOS, the virtualization is already enabled (and it has worked before, when we ran Win 7, same machines, and also after we went 8 in last june).

Thanks for your help.

[michaln]

How can I create 64bit vpc on Win7-64 with VisualBox?

You can't, there's no such thing as VisualBox

[mpack]

Same problem here on Win 8 machines

Uh huh, and you read the FAQ I linked to in my previous answer, right?

Basically, if you diligently went through the checklist and still can't run 64bit VMs - then you simply can't run 64bit VMs, and you should already know why.

[Dwalin_7]

Thank you for your answer, even if I sensed a bit of irony ^^.

They are the same machines as they were before, so we (nor do the teacher) can't figure out why we can't run 64 bits VM anymore. It's not just the new version since I tried reinstalling older versions and it was not better.

CPU 64 bits
Win 8 64
Virtualization enabled in the BIOS
VB 4.3.16 -> only 32 bits OS proposed when new VM created ; for example : Windows 7 (32 bits)

What else than what's in your checklist could it be ? Malware ?

[michaln]

What else than what's in your checklist could it be ? Malware ?

Or antivirus software. Hard to tell the difference anyway.

[mpack]

VB 4.3.16 -> only 32 bits OS proposed when new VM created ; for example : Windows 7 (32 bits)

It would help if you said what VirtualBox version you upgraded from. Past versions of VirtualBox would not always complain if VT-x/AMD-v was enabled in the VM settings but not available on the host PC. Usually what happened then is that the user went on to install 32bit versions of the guest OS, while assuming that they were 64bit versions.

Since VirtualBox 4.3.0, VirtualBox gives you an error message when VT-x/AMD-v is enabled for a VM, but is not available on the host. Note that 4.3.0 didn't introduce the error, it simply reports it more clearly.

So, start by assuming that VT-x was in fact never available on that host, you just thought it was. Return to the checklist, and check the possible reasons why it isn't available.

Incidentally: the checklist does not attempt to itemise all possible software packages that could potentially grab VT-x/AMD-v. It's really up to you to know what software you have installed on your own PC. Hyper-v is mentioned as a common culprit, but that certainly isn't the only possibility.