- When trying to create a Virtualbox VM recently I was only presented with the option of creating a 32-bit client. After a bit of research it turns out this can be caused by incorrect settings in the BIOS or by a competing Virtual Machine software cohabiting the system. First of all your CPU must support the virtualization extensions.
- VirtualBox Only Shows 32-Bit OS Options. November 29, 2015. I ran into an interesting (read: frustrating) problem this week at work. I was wanting to install a Linux VM so that I could do some testing on a few applications, as well as use it as an excuse to.
- Virtualbox Only Shows 32 Bit
- Virtualbox Only Shows 32-bit Windows 10
- Virtualbox Only Display 32 Bit
- Virtualbox Only Shows 32-bit Windows 10
Virtualbox Only Shows 32 Bit
I am running VirtualBox v5.2.32 on an Ubuntu 18.04 host. I have created a Windows 10 (64-bit) guest. I installed VirtualBox v6.0.10 in the Windows 10 guest (Windows 10 Pro – v1903 – 64-bit). I am trying to create an Ubuntu (64-bit) guest inside the Windows 10 guest. I only see 32-bit options inside the Windows guest. After several attempts to resolve this, I am still only seeing 32-bit options.
Saya telah mengunduh dan menginstal virtualbox 4.3.20 terbaru untuk saya Windows 7 (64-bit OS), tetapi ketika saya ingin menginstal 64-bit Linux, New- Create Virtual Machine hanya menampilkan 32-bitopsi, tidak ada 64-bitopsi. After deleting the VM, and trying to re-add it, I was greeted with another issue. Even though I’m running a 64-bit OS (Windows 10), and have a 64-bit CPU architecture, I couldn’t create a 64-bit VM. I could only select a 32-bit option from the dropdown menu. Now not only will my VMs not boot, I can’t even select a 64-bit version. Issue: Virtualbox sometimes shows only 32 bit VM can be created on some Windows 10 AMD processors computer, no 64 bit VM available. Solution: Following are the steps to enable Virtualbox to be able to create 64 bit VM.
The purpose for creating a VM inside a VM is to be able to ensure that VirtualBox is working so that I can test Vagrant configuration inside a Windows 10 environment. Our Vagrant config is using 64-bit base images, so I need to be able set up 64-bit guests inside this Windows 10 guest.
…on the Ubuntu Host
I have checked Enable VT-x/AMD-V on the System > Acceleration tab in the Ubuntu host's VirtualBox config for the Windows 10 guest machine.
…on the Windows Guest
In the Windows guest machine, I can see that the host's physical CPU details are passed through in Settings > System > About and it shows as a '64-bit operating system, x64-based processor'.
This is a vanilla Windows 10 Pro installation, no additional software (i.e., no addon virus protection software).
I inspected Windows Features to ensure that the following are not checked:
- Guarded Host
- Hyper V
- Virtual Machine Platform
- windows Hypervisor Platform
- Windows Subsystem for Linux
…because my googleing seems to indicate that some or all of these might be an issue.
Based on a VirtualBox forum (I have a 64bit host, but can't install 64bit guests), using gpedit.msc, I set Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security to Disabled. I also check that Windows Security > Device Security > Core Isolation Details is set to Off.
I have 'repaired' the VirtualBox installation. I have uninstalled VirtualBox, rebooted, reinstalled, and then rebooted again.
I looked at these related, previously asked questions and followed their suggestions as indicated in the steps above. Everything I am finding seems to be related to a Windows 64-bit host running directly on the host machine, not dealing with a Windows host which is itself a guest VM.
Virtualbox Only Shows 32-bit Windows 10
Below is a posting from another user just recently. The answer to this problem was gibberish by the site moderator (Apple Host?). Since that link is locked because it is resolved(?) I am repeating the question here and looking for a valid answer. I am having the exact same problem and I would like a valid answer. I have Virtual box on a Intel Xenon server and Ubuntu 64 bit shows up. When I installed Virtual Box on my laptop (Windows 7 Professional 64 bit with a Intel Core i5-4300M CPU @2.60GHz), I only have the option for 32-bit Linux (Ubuntu) and other OS's. I sure would like to use the 64-bit OS's like I was on my desktop!Postby jopps » 12. Feb 2018, 16:20
So I have this weird problem that I have been trying to fix for a couple of days now. When installing the latest version of VirtualBox, I can only choose 32 bit when creating a new Machine. After some googling, I found a solution where all I had to do was to Repair the program using the installation file. After repairing, the 64 bit versions shows up. However, after repairing, Virtualbox tells me to reboot my system in order to complete the reparation. But after rebooting the system, I'm back where I started, where only 32 bit is showing up which has left me in some sort of evil circle.
Also, if I try to run a 64 bit Machine after repairing, but before a reboot, I get the following pop-up error: NtCreateFile(DeviceVBoxDrvStub) failed: 0x000000e STATUS_NO_SUCH_DEVICE (164 retries)(rc=-101).
I am using Windows 7 Professional 64 bit with a Intel Core i5-2540M CPU @2.60GHz. I have(atleast I think I have) disabled Hyper-V and the Intel Processor Identification Utility says the Intel Virtualization Technology and Intel VT-x is enabled(I dont have the BIOS password so I can not verify this in the BIOS itself).
Does anyone have any solution to my annoying problem?