This tutorial will show you step by step what to do when VirtualBox is only showing 32-bit and no 64-bit versions of operating systems as options while creating a new virtual machine.
Note: This may be obvious for most of you, but your host operating system should be 64-bit to run 64-bit guest operating systems in VirtualBox.
Install Kali Linux on Virtual Box. Once you have installed VirtualBox and downloaded the Kali Linux image, you just need to import it to VirtualBox in order to make it work. Here’s how to import the VirtualBox image for Kali Linux: Step 1: Launch VirtualBox. You will notice an Import button – click on it.
If VirtualBox has no 64-bit option on Windows 10, then you can try the solutions on this page to fix the problem.
- If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed.
- Sha256sum kali-linux-2018.1-vbox-i386.ova”-If the checksums dont match, its a bad image and you can re-download. If it does match, check the following:-Are you able to boot other linux 32-bit ova images(for ex: linux mint 32bit) into virtualbox on your MAC?
- Under “Type”, select Linux. If you expand the Version drop-down menu, you’ll notice that there’s no option for Kali. Since Kali Linux is a Debian based Linux kernel, we’ll select Debian as the version. Choose between either 64 bit or 32 bit depending on your processor architecture and the version of Kali you downloaded.
- I want to play two tf2 games at once in Steam by using Virtualbox for tf2 community servers. And this guy told me I should get Kali Linux 32 bit instead of Ubuntu Linux so I took his words. I don't wanna start all over again though by changing it.
Methods:
My experience with this problem
I experienced the same problem while trying to install a 64-bit version of Linux Mint inside VirtualBox.
I opened VirtualBox, clicked on NEW, entered a name for the virtual machine, choose the type of operating system, but when I wanted to choose a version, I only saw 32-bit versions and NO 64-bit versions as an option.
But:
Fortunately, I found a simple solution online and on this page, I will share that solution with you.
Note! Your host operating system (OS installed on your PC) must be 64-bit.
I was using a 64-bit version of Microsoft Windows 10 Pro while creating this tutorial.
Make sure that “Intel Virtualization Technology” and “VT-d” are enabled
Enter BIOS settings and check if “Intel Virtualization Technology” and “VT-d” are enabled.
The following steps may be slightly different on your computer.
1. Start (or restart) your PC.
2. Press the right keyboard key to enter the BIOS setup. This must be done before Windows starts, so it's best to press the key a few times directly after you start your PC.
The exact key or key combination depends on your computer manufacturer and model.
Common keys to enter the BIOS are F1, F2, F10, DEL, and ESC.
3. Look for the following settings Intel Virtualization Technology and VT-d.
4. Make sure that they're both enabled.
5. If you made changes, then you must save the settings.
Windows 10 (host) must be a 64-bit operating system
To check if your Windows 10 is a 64-bit operating system, press the [Windows] + [pause] keyboard keys.
At System type (located under System), you should see something like 64-bit Operating System, x64-based processor.
Hyper-V must be disabled
Hyper-V is Microsoft's hardware virtualization product.
It lets you create and run virtual machines (like VirtualBox).
But:
Many third-party virtualization applications (including VirtualBox) do not work together with Hyper-V.
That's why you must make sure that Hyper-V is disabled.
To check if Hyper-V is disabled, follow the following steps:
1. Right-click on the Windows start menu button.
2. Click on Run. Download adobe premiere pro cc 32 bit full version.
3. Enter optionalfeatures.exe in the Run window.
4. Click on OK or press Enter.
The Windows Features window will appear.
5. Check if the Hyper-V option is unchecked.
6. If the Hyper-V option unchecked (like in the screenshot above), then you can close the Windows Features window.
But:
If the option is checked, then you will need to uncheck it and then click on OK.
If you want to be 100% sure that Hyper-v is disabled then follow these steps:
1. Right-click on the Windows start menu button.
2. Click on Command Prompt (Admin).
3. Enter the following command:
4. Press Enter.
5. After the command is finished, you will need to power down and reboot your PC.
Solution 1: Repair VirtualBox installation
1. Right-click on the installer file (the one you used to install VirtualBox) and choose Run as administrator.
If you don't have the installer file anymore, then you will need to download it from the VirtualBox website (www.virtualbox.org). The installer file must be the same version as the version of VirtualBox that's installed on your computer.
2. When the Windows User Account Control window appears, you click Yes.
Note: You might need to enter an administrator password in the User Account Control window and then click Yes.
A setup window will appear.
3. Click on Next.
4. Click on the Repair icon.
5. Click on Repair located at the bottom right.
VirtualBox will now start the repairing process. This will only take a few seconds.
6. After the repair process is finished, you click on Finish.
VirtualBox may ask you to restart your PC.
Hopefully, this simple solution will solve your problem.
Solution 2: Disable “Memory integrity” in Windows 10
1. Open Windows Security.
2. Click on Device security.
3. Under Core isolation, you click on Core isolation details.
4. Make sure that Memory integrity is turned off.
If Memory integrity was enabled and you just disabled it, then you may need to restart your PC.
Hopefully, this simple solution will solve your problem.
☕ Buy me a coffeeMaybe you're also interested in:
With Diskinternals VMFS Recovery, you can mount any VMDK file that belongs to any given virtual machine on a server. In order to use the available file access and data recovery tools, you will need to connect to the ESX/ESXi server and mount its disks, partitions and VMDK files. You will be able to repair and open VMDK files and no need in VMDK viewer tool.
Make sure that SSH connectivity is enabled on your ESX/ESXi server. Configure connection settings by entering the IP address of your server, login and password information, and click “Connect”.
How to open VMDK file? There are three different ways to access files after connecting to an ESX (ESXi) server.
Method 1: mounting a *.vmdk disk from a certain Datastore.
Select a folder with the virtual machine being recovered. There, select *.vmdk (or other type) files to mount.
Note: the ESX server does not normally permit low-level disk access to a running virtual machine. With VMFS Recovery, you can still mount the working disk by following the steps described in the how-to guide: Mounting Hard Drives (VMDK files) of a Running Virtual MachineMethod 2: mounting a physical hard drive hosting the ESX (ESXi) server
In this mode, the actual physical hard drive will be mounted, allowing you to access all partitions and unpartitioned areas of the drive. By mounting the physical drive, you’re essentially replicating physical access to the actual hard disk as if it’s been removed from the server and connected directly to your PC.
Method 3: mounting any file from an ESX (ESXi) server
With this method, you can mount any file from an ESX (ESXi) server. This method includes both methods #1 and #2. You can look up Datastore at /vmfs/volumes/. The hard drives are located at /dev/disks/
After selecting the files or drive images to mount, click Mount to add newly mounted disks into the main window.
Diskinternals VMFS Recovery is a tool which makes easy for a user to mount VMDK file on Windows.
Method 4. Mount VMDK disk with 7-Zip
'Unpacking' or mounting VMDK disk is possible with the help of the well-known 7-Zip archiver. This method is quite fast compared to the others and, at the same time, is fairly simple. You just need to right-click on the VMDK file and select “Open Archive”.
You can also try the following method, if this does not suit you.
Method 5. Use Windows Explorer for VMDK disk mounting
You can try to mount VMDK on Windows using built-in tools; Windows Explorer should help you with this.
Here's how to do it: right-click Start and select “Explore”. Now you need to open the folder with the VMDK file using the right mouse button. From the list, select 'Virtual Disk Map'. Next you need to select the drive letter where you intend to mount the VMDK disk. Then click on “OK”.
Method 6. Use VMware Workstation for VMDK disk mounting
VMware Workstation is a desktop program for mounting VMDK on Windows. Just open it, and on the taskbar, select the File tab. Then from the list, select 'Map Virtual Disks ..'. Next, you need to select the drive letter where you want to mount the VMDK file and click OK. Again, this is a simple and efficient method for mounting VMDK on Windows.
Method 7. Try vSphere Disk Development Kit for VMDK disk mounting
You can use vSphere Disk Development Kit to mount VMDK on Windows. This program must be downloaded and installed before use.
Depending on what you want to do, you need to enter certain commands; for example:
- to mount a read-only disk — vmware-mount.exe X: “C:TempTestVM.vmdk”
- to mount several volumes — vmware -mount.exe /v:2 X: 'C:TempTestVM.vmdk'
- to mount the disks for recording - vmware-mount.exe /m:w X: 'C:TempTestVM.vmdk'
- to list all the mounted VMDK disks: vmware-mount.exe /L
A – A physical hard drive of an ESX (ESXi) server connected via method #2. A new partition labeled “data_store_2TB” with VMFS file system appears immediately after mounting the drive. B – A *.vmdk disk from a virtual machine mounted via method #1. Partitions “/” and 'Linux Swap Volume 1” are available immediately after mounting. C – This is just a file connected via method #3. All *.vmdk disks and physical drives of ESX servers can be scanned with any tool included with VMFS Recovery: Recovery mode: NTFS, FAT, Ext2/3/4, VMFS Uneraser and Reader modes: NTFS, FAT, Ext2/3/4, VMFS, Reiser4, ReiserFS, HFS, UFS2, exFAT, ReFS In addition, the mounted *.vmdk disks can be assembled into a RAID array (LDM, Linux RAID).