Opened 7 years ago
Last modified 7 years ago
#16946 new defect
Windows 7 Home Premium with VirtualBox 5.1.24 64-bit VMs not offered
| Reported by: | clairestreb | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.24 |
| Keywords: | 32-bit, 64-bit | Cc: | |
| Guest type: | all | Host type: | Windows |
Description
Problem:
- When I click New in VirtualBox, no matter which Type I select, there are no 64-bit choices listed in the Version, only 32-bit choices.
This is what I have:
- ASUS laptop
- Windows 7 Home Premium, 64-bit
This is what I did:
- Upgraded to VirtualBox 5.1.24.
- Ran this successfully in an elevated cmd window:
bcdedit /set hypervisorlaunchtype off
- Enabled VT-d in my BIOS. I do not see any setting named Virtualization.
Priority is 'blocker', because I cannot install Windows Server 2016.
Change History (5)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
Of course, I did go to the forums and tried everything listed in that post. That's why I thought it was a bug.
comment:3 by , 7 years ago
There is no such bug, that's for sure. The FAQ has never been proven wrong, so please try again. It is difficult to identify which application is using the VT-x exclusively, but there is an application that does. Usual suspects these days are antivirus that have enabled hardware accelerated scanning. Start looking there and then of course, all the other suspects that the FAQ lists.
comment:4 by , 7 years ago
Some AV software might enable Hyper-V as well.
But please attach a VBox.log file of a VM session (dummy is sufficient, just start a VM with no hard disk attached if necessary). I want to see the configuration of your PC.
comment:5 by , 7 years ago
| priority: | blocker → major |
|---|
May I suggest something? It's usually better and faster, if issues like this one get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".
Please go thoroughly through the FAQ: I have a 64bit host, but can't install 64bit guests. Something is capturing your VT-x (not VT-d) and you got to find out exactly what, it's not a given recipe. Some ideas are provided in the FAQ.
And no, this is not a blocker, a blocker involves loss of data, which (fortunately) is not the case.