I have a problem. I have a 64-bit Intel i7 processor, and mine does not recognize it. The error is similar to the fact that a 64-bit processor was not found. When choosing a distribution kit, in the settings you can choose only 32-bit versions. My host system is a 64-bit Kali, and I do not see how to debug this problem. Reinstalling does not help.

One Solution collect form web for “VirtualBox gives me only a 32-bit option for a system installation, but I have a 64-bit processor”

If you do not have a host computer around 2000, then the processor is definitely 64-bit. The fact that you are using a 64-bit OS excludes the presence of a 32-bit processor. You may encounter two reasons:

Virtualization technology is not included. To solve this problem, go to the main computer settings (by pressing F1 / F2 / Del, depending on your computer) at boot. Somewhere out there, you should be able to find a place to turn it on (it should be called VTxxx).

You may need to enable PAE (or something like that) before starting the guest OS installation process. It will be installed in the virtual machine settings.

Network and server administrators are often faced with the need to test hardware, software, and certain parameters and settings on real servers. But testing something on a running server is extremely dangerous, as it can lead to data loss and malfunctions.

Specialized software comes to the rescue in this situation. Able to emulate a real computer and perform all necessary actions with it. The most popular program in this case is VirtualBox from Oracle.

How to use virtualbox?

virtualbox 32/64 bit for windows 7 and 8 must be installed on a working computer running Windows. In the future, VirtualBox allows you to create any number of virtual machines with the selected parameters, and install any operating systems on them for testing. In this case, the real physical computer will be the host, and the operating system on it will be the host.

When installing the operating system on a virtual machine, you should pay attention to the fact that it must be configured properly and meet the minimum requirements. In this case, the operating system installed on the virtual computer is called the guest.

Thanks to the use of virtual machines, testing of equipment, software and necessary settings is greatly simplified. With all this, the virtual and physical machines communicate with each other through a network connection. In addition, a virtual machine can take control of any equipment installed on a physical computer.

The program is also available for operating systems such as MacOS and Linux (popular for Ubuntu and Mint).

Hello everyone. Let's talk today about a not-so-pleasant jamb that you might have if you decided to use the VirtualBox virtual machine. The cant lies in the fact that you can not install 64-bit Windows. That is, when creating a virtual machine, you do not have the choice of 64-bit Windows, only 32-bit.

I also had such a joint, but it was a long time ago, about four years ago, then I still had the ancient Pentium 4 percent. I loved my Penk and didn’t get off it for a long time ..

Let me remind you that we are talking about the fact that here in this menu VurtualBox there is no item for installing Windows 64-bit:

Well, why is there no x64 choice in VirtualBox? The first option is the most commonplace, is that your processor does not support virtualization technology. Almost all modern processors have it, that Intel, that AMD. There are even older processors, but not all, for example, the Pentium 4 family does not have it (it is available only in 662/672 models). But with Pentium D and higher, there is already virtualization in almost all percentages. I can’t say anything about AMD, but I think the picture is about the same.

In any case, there is virtualization in the new processes. If you don’t, then you either have an old processor or some kind of rare or special beast.

But how do you know if your processor supports virtualization or not? Of course, it’s best to just look, and then search the Internet for information about the process. You can also download the CPU-Z utility and it will show you the info, for example, I have a Pentium G3220 processor, here is the info CPU-Z prog shows about it:

You see, there is something like Instructions, here there is a list of instructions that the processor supports. True, there is one moment here, each processor company has virtualization technologies called differently. Intel has VT-x (if there is VT-d, this is even cooler), but AMD has the technology called AMD-V. For example, info about the AMD FX-8350 processor, and here it is also indicated that the percent supports AMD-V technology:

By the way, I really like this AMD FX-8350 processor, it costs not so much, it seems to be somewhere half as much as the Core i7. But in terms of power, it’s clear that it loses the i7, although the FX-8350 has 8 cores, and the i7 has only 4. But for me, the advantage of the AMD FX-8350 is that it has 8 cores, that is, where you need it multithreading, the FX-8350 may be more efficient, or maybe not, I don’t know for sure ..

Well, sort of sorted out. That is, to check the processor, whether it has virtualization or not, the fastest way is to download the CPU-Z utility (it is very simple and the computer does not load) and quickly look at it. And then if you need info about the process, then you start CPU-Z and there all the most important info is!

By the way, not everyone knows, but VirtualBox works without virtualization. I’m not sure, but I know for sure that VirtualBox used to have built-in software virtualization, if it is now, I don’t know. However, I personally did not notice the effect of it: without virtualization technology, the virtual machine works with brakes and this is completely uncomfortable.

There is such a joke that VirtualBox does not seem to see that the processor supports virtualization. To fix this problem, you can do this. I will say right away, I'm not sure that this will help you, but it helped some users. You need to disable one component that relates to virtualization, but a little to the other, so to speak. Here's how to do it, right-click on Start and there, in the menu, select Programs and Features (the topmost):

Now look, you will have a list of components, some of them are included, and some are not. What is there to do? Here you just need to uncheck a component such as Hyper-V, here it is:

After that, do a reboot and see if it is possible to install 64-bit Windows. If everything worked out, then you will have such a list here, well, that is, you can put a 64-bit:

By the way, on the Internet there is an opinion that VirtualBox is better than VMware, but is it really so? Well, in general, there is not so much debate on this subject, but enough, but many, as I understand it, do not argue at all, because they are confident that they are right. Well, there’s such a thing, I don’t argue either, because I’m sure that I’m right. But I’m sure, because I have tested more than once, and I have VMware in all cases (and to be more precise, the free version of VMware Player ) always worked faster than VirtualBox. In terms of convenience, I like VirtualBox more. But if you need to often work with a virtual machine, then here I choose only VMware. Well this is so, just to your note, my opinion would be so to say ..

But I still haven’t written something, I forgot, this is my cant, excuse me. It may be that your processor supports virtualization (if it is modern, then it supports 95%), but there is still no choice for 64-bit Windows. What's the matter? And the thing is that virtualization technology is an option that is turned on or off in BIOS. And not on all motherboards, this option is on by default! In general, you need to go into the BIOS (turn on the computer\u003e press ten seconds on the F1, F2, Del buttons, wait for the BIOS, the method works on a lot of hardware) and enable this virtualization there. Something will be written there like Virtualization Technology and it will be Enabled (enabled) or Desabled (disabled). Something in this style, here is an example, but your design may be different:

I forgot to say something else, in Windows 10 in the manager you can also see if virtualization is enabled or not. On the Performance tab, there is such a Virtualization item, everything is indicated there:

I’ll also say in a nutshell what virtualization is. This is when the virtual machine can send commands to the processor directly. Well, something like this. Intel's basic virtualization is VT-x, and advanced is VT-d. VT-x allows you to simply send commands to the processor directly, but VT-d allows you to transfer entire devices on the PCI bus, such as a video card, to the virtual machine. But as a rule, VT-d comes in more expensive processors. I'm not sure about AMD, but most likely there is something similar

Well, all the guys, that's all. I hope that you can still find out the reason why there is no x64 choice in VirtualBox. I think that you will solve this problem, because most likely you have a modern processor that supports this virtualization in hardware. Good luck in life, good mood

10.01.2019

Hello admin! An interesting question for you. I installed a virtual machine on 64-bit Windows 10 and wanted to create a 64-bit virtual machine, but the program does not display the items responsible for creating 64-bit virtual systems. Turns out that i can only create 32-bit virtual machine  (Windows XP, Vista, 7, 8.1, 10)!What do you think could be the matter?

Why installed on a 64-bit Windows VirtualBox does not allow creating 64-bit virtual machines

Failure or disabling hardware virtualization

Hello friends! Being installed on 64-bit Windows, the Oracle VirtualBox hypervisor allows you to create both 32- and 64-bit virtual machines, but at some point the program may stop displaying items responsible for creating 64-bit virtual systems. Often a similar problem occurs after a sudden power outage on a computer, and it can also be caused by incorrect settings of some components.

If the problem appeared after a sudden power outage, the cause of the problem is most likely either a temporary failure in the virtualization settings, or its shutdown at the BIOS level. In most cases, it is possible to solve the problem by simply restarting the computer correctly, if the options for creating 64-bit virtual systems do not appear in VirtualBox and after rebooting, you need to go into the BIOS and see if hardware virtualization is disabled there.

Surely it will be turned off and it needs to be turned on. In Intel-VT, the necessary option is located in the Advanced → CPU Configuration section and is usually called Virtualization Technology, in AMD-V it can be called Secure Virtual Machines.

Disable Hyper-V

Windows has its own Microsoft Hyper-V hypervisor, but it is disabled by default. If you enable it, VirtualBox will not be able to work correctly, because these two software products conflict with each other. Checking if Hyper-V is enabled on the system is very simple. Open the Windows Components snap-in with the optionalfeatures command and see if the Hyper-V Platform and Hyper-V Controls checkboxes are ticked. If so, be sure to remove them, save the settings and restart the computer.

Disable Device Guard

In corporate versions of Windows 10, the problem can be caused by the operation of Device Guard - a special technology that allows you to run only those applications that meet certain security requirements. On Dell computers, the option may be enabled by default. Disconnect it and check the operation of VirtualBox.

Having opened the local group policy editor with the gpedit.msc command, go to Computer Configuration → Administrative Templates → System → Device Guard, on the right, double-click on the “Enable Security-based Virtualization” policy and set it to “Disabled”.

For the tinctures to take effect, restart the computer. If you do not have the specified policy, just skip this step.

Disable kernel isolation

To provide additional security in Windows, a special core isolation technology has been developed that allows you to run processes in a protected memory space. Being closely related to virtualization, enabled kernel isolation can lead to conflicts and malfunctions of third-party hypervisors. Try disabling it. To do this, in the registry key HKLM / SYSTEM / CurrentControlSet / Control / DeviceGuard / Scenarios / HypervisorEnforcedCodeIntegrity, set the Enabled parameter to 0.

Alternatively, you can disable Secure Boot in the BIOS, this will lead to the inability to use kernel isolation technology.

Remove other third-party hypervisors

Finally, the conflict between VirtualBox and other third-party hypervisors, if installed on the computer, may be the source of the problem. The likelihood of such a scenario is small, but in order not to torment yourself with doubts, it is worth excluding it.

Additionally