If VirtualBox is not showing 64-bit Windows 10 as an option when you create a new virtual machine, the fix is usually to enable hardware virtualization (VT-x/AMD-V) in your PC’s BIOS or UEFI settings, and to ensure you have the latest VirtualBox version installed. This article walks you through the exact steps, explains why the option disappears, and covers related issues like Hyper-V conflicts and missing CPU features.
Why 64-Bit Options Disappear in VirtualBox
VirtualBox only lists 64-bit guest operating systems if your host CPU supports hardware virtualization and that support is enabled and accessible. The 64-bit option is hidden when any of the following is true:
- Hardware virtualization (Intel VT-x or AMD-V) is disabled in the BIOS/UEFI.
- Your CPU is 32-bit (rare for Windows 10 hosts, but possible on very old hardware).
- Another hypervisor (like Hyper-V, Windows Sandbox, or Windows Hypervisor Platform) is holding the virtualization resources.
- VirtualBox is running inside a virtual machine (nested virtualization) without the necessary settings.
- You are using an outdated VirtualBox version that doesn’t recognize your CPU’s features.
The most common cause by far is the BIOS/UEFI setting. Most modern PCs ship with virtualization disabled by default, and the 64-bit guest list is intentionally hidden until the host can guarantee the required performance and security features.
Step-by-Step: Enable Virtualization in BIOS/UEFI
Follow these steps to enable VT-x (Intel) or AMD-V (AMD) on a typical Windows 10 host:
- Restart your computer and press the key that opens the BIOS/UEFI setup. Common keys are F2, Del, F10, or Esc – the exact key appears on the first screen during boot.
- Navigate to the advanced settings. Look for a menu named Advanced, CPU Configuration, Security, or Virtualization.
- Find the setting called Intel Virtualization Technology, Intel VT-x, AMD-V, SVM Mode, or Virtualization Extensions.
- Set it to Enabled.
- Save and exit (usually F10) and let Windows boot normally.
- Open VirtualBox and try creating a new virtual machine – the 64-bit Windows 10 option should now appear.
If you cannot find the setting, consult your motherboard or laptop manual. Some systems hide it under a submenu like “Processor” or “Advanced Chipset Control.”
Check If Virtualization Is Already Enabled in Windows
Before you restart and dig through BIOS, verify whether virtualization is already on. Open Task Manager (Ctrl+Shift+Esc), go to the Performance tab, and select CPU. Look for the “Virtualization” line at the bottom right. It will say either Enabled or Disabled.
If it says Enabled but VirtualBox still hides 64-bit options, the problem is likely a hypervisor conflict or a VirtualBox version issue, not the BIOS.
Hyper-V and Windows Hypervisor Platform Conflict
Windows 10 includes Hyper-V, a built-in hypervisor. When Hyper-V is enabled, it takes exclusive control of the CPU’s virtualization extensions, and VirtualBox (which uses its own hypervisor) cannot access them. The result: 64-bit guests disappear or fail to start.
To fix this, you have two options:
- Disable Hyper-V (and related features) if you don’t need it. Go to Control Panel > Programs > Turn Windows features on or off, and uncheck Hyper-V, Windows Hypervisor Platform, and Windows Sandbox. Restart.
- Use VirtualBox 6.1.28 or later, which can run alongside Hyper-V on Windows 10 by using the Windows Hypervisor Platform API. If you need Hyper-V for Docker or WSL2, this is the better path.
Update VirtualBox and Extension Pack
An outdated VirtualBox may not recognize newer CPUs or may have bugs that hide 64-bit options. Always use the latest stable release from the official website. Also install the matching Extension Pack – it adds USB 3.0, NVMe, and other features, though it does not directly affect the 64-bit list. After updating, restart VirtualBox completely (close all windows, not just the VM).
Verify Your CPU Actually Supports 64-Bit and Virtualization
All mainstream CPUs from the last 15+ years support 64-bit, but virtualization support is not universal on very old or low-end processors. To confirm your CPU’s capabilities:
- Open Command Prompt and run
systeminfo. Look for the lines “Hyper-V Requirements” – if they all say “Yes,” your CPU supports virtualization and it is enabled. - If any line says “No,” your CPU either lacks the feature or it is disabled in BIOS.
- You can also use the free tool CPU-Z to see the VT-x/AMD-V flags under the “Instructions” section.
If your CPU genuinely lacks virtualization support, you cannot run 64-bit guests in VirtualBox. The only workaround is to use a different hypervisor that does not require VT-x/AMD-V, but those are rare and slow.
Frequently Asked Questions
Why does VirtualBox only show 32-bit Windows 10?
This is the classic symptom of virtualization being disabled in the BIOS. Enable VT-x/AMD-V as described above, and the 64-bit option will appear. If it still doesn’t, check for Hyper-V conflicts or update VirtualBox.
I enabled virtualization but still no 64-bit option – what now?
First, verify in Task Manager that Windows actually sees it as “Enabled.” If it does, disable Hyper-V and Windows Hypervisor Platform, then restart. If that fails, try the latest VirtualBox version or check if your CPU model supports VT-x/AMD-V (some older Celeron and Atom CPUs do not).
Can I run 64-bit Windows 10 without VT-x/AMD-V?
No. VirtualBox requires hardware virtualization for 64-bit guests. Without it, the 64-bit option is hidden and the VM will not start even if you force it. Your only option is to use a 32-bit guest or upgrade your hardware.
Does enabling virtualization in BIOS slow down my PC?
No. Enabling VT-x/AMD-V has no noticeable performance impact on normal Windows use. It only allows hypervisors like VirtualBox to work efficiently. It is safe to leave enabled.
I have an AMD CPU – is the setting called something different?
Yes, on AMD systems the setting is often called SVM Mode (Secure Virtual Machine) or simply AMD-V. It is usually found in the same BIOS sections as Intel VT-x.
Do I need to enable “VT-d” as well?
No. VT-d (Intel) and IOMMU (AMD) are for direct hardware passthrough, not for basic 64-bit guest support. You only need VT-x/AMD-V for the 64-bit option to appear.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Show User Library in macOS High Sierra & Sierra
- Device Manager Shortcut: Windows 10 Desktop
- How to Remove Forgotten Passcode from iPhone
- Fix Slow Wi-Fi Problem iPhone X: 9 Steps
- How to Check if a Candidate Accepts Crypto Donations
- How to Listen to Deleted Voicemails on iPhone