VirtualBox Won’t Show 64-bit: How to Fix It in 5 Steps?

Checking some Hyper-V settings will prove efficient

Reading time icon 4 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Key notes

  •  Virtualbox not showing 64-bit can be frustrating when you know your device meets all the requirements.
  • This issue could be due to some system app, or Hyper-V enabled on your PC.
  • This guide will discuss all the possible methods to fix the problem.
VirtualBox Won’t Show 64-bit: How to Fix It in 5 Steps

Wondering why Virtualbox is not showing a 64-bit option when creating a new virtual machine? Well, there could be several reasons for the same. 

In this guide, we will discuss the potential reasons along with the fixes to resolve the problem.

What causes VirtualBox won’t show 64-bit guest OS in Windows?

Spotting the exact reason the issue is occurring can be difficult, as there can be several reasons. However, we have listed some of the popular ones here: 

  • Virtualization Disabled – If Virtualization is disabled from the BIOS utility, the issue can occur.
  • Hyper V – Hyper V is a  hardware virtualization product that allows you to create a virtual machine. However, it could conflict with VirtualBox and hence the issue. It needs to be disabled.
  • Core Isolation – Core Isolation protects against viruses and attacks by separating computer processes from your OS and device. However, this could cause problems in running a virtual machine. Therefore, it needs to be disabled.
  • VM platforms  – If you have another VM software on your PC, conflict could arise when using resources, causing the problem.
  • Device Guard and Credential Guard– Apps like Device Guard provide hardware security and only let those apps run, defined in Windows code integrity policies. This can also cause problems. 

How can I fix VirtualBox won’t show 64-bit?

Before moving to the detailed troubleshooting steps, make sure you try these quick fixes:

  • Ensure your computer supports x64 bit.
  • Uninstall and reinstall Oracle VirtualBox.
  • Make sure you are using the latest version of VirtualBox.
  • Restart your computer
  • Make sure you have Microsoft C++ 2019 Redistributable package installed.

1. Disable Hyper V

  1. Press Windows + R to open the  Run command window.Windows Features
  2. Type optionalfeatures.exe and press Enter to open the Windows Features window.
  3. Locate and remove the checkmark beside Hyper V and click OK.Windows Features Hyper V
  4. Restart your PC.

2. Enable Intel Virtualization Technology

  1. Press Windows + I to get Settings.
  2. Go to System, then click Recovery.System - Recovery Windows 11
  3. Now locate Advanced Startup and click Restart Now.Recovery Advanced Startup -Virtualbox won't show 64 bit
  4. On Choose an option screen, click Troubleshoot.Choose an option - Troubleshoot
  5. Now select Advanced Options.Advanced options
  6. Select UEFI Firmware Settings and click Restart.UEFI 2
  7. Now the screen will present options; choose the one to enter BIOS.
  8. Click Configuration, then Virtualization Technology, and mark it Enabled.Virtualization
  9. Go to the Exit menu and choose Save changes and Exit.

Note: For AMD processors, ensure AMD SVM(Secure Virtual Machine) is enabled.

3. Disable Core Isolation

  1. Press Windows + I to get Settings.Privacy & Security - Windows Security
  2. Go to Privacy & Settings, then click Windows Security.
  3. Click Open Windows Security.Windows Security Open
  4. Go to Device Security, then Core isolation, and click on Core isolation details.Device Security - Core isolation
  5. Toggle off the switch under Memory IntegrityCore Integrity
  6. Restart your PC.

4. Disable Device Guard & Credential Guard

4.1 Use Group Policy Editor to disable Device Guard 

  1. Press Windows + R to get the Run window. GPEDIT RUN COMMAND
  2. Type gpedit.msc and press Enter. 
  3. Copy and paste the following path: Computer Configuration\Administrative Templates\System\Device GuardTurn On Virtualization Based Security
  4. Double-click on Turn On Virtualization Based Security and set it as DisabledDisabled
  5. Click Apply and then OK

4.2 Use Registry Editor & Command Prompt to Disable Credential Guard

  1. Press Windows + R to get the Run window. REGEDIT RUN COMMAND
  2. Type Regedit and hit Enter.
  3. Copy and paste these paths one by one in the address bar—Right-click on LsaCfgFlags, EnableVirtualizationBasedSecurity, and RequirePlatformSecurityFeatures keys and select DeleteHKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\LsaCfgFlags HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\DeviceGuard\EnableVirtualizationBasedSecurity HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\DeviceGuard\RequirePlatformSecurityFeatures
  4. Now, press the Windows key, type CMD, and click Run as administrator.DOS COmmand Prompt
  5. Copy and paste these commands mentioned below one by one and press Enter after every command mountvol X: /s copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi" bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215} bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X: mountvol X: /d
  6. Click Yes to the UAC prompt asking to disable Windows Defender Credential Guard.
  7. Restart your computer.

5. Uninstall other VM apps

  1. Press Windows + R to open the Run box.APPWIZ RUN COMMAND
  2. Type appwiz.cpl and press Enter.
  3. Go to the installed apps, select other VM apps, and click Uninstall.Uninstall Apps
  4. Restart your PC.

So, these steps you need to follow to resolve VirtualBox won’t show 64-bit. Try them and let us know which methods worked for you in the comments section below.

More about the topics: Hyper-V issues