VirtualBox does not start

VirtualBox virtualization tool is distinguished by stable operation, but it can stop running due to certain events, whether it is incorrect user settings or an operating system update on a host machine.

Launch Error VirtualBox: Major Causes

Various factors can affect the operation of the VirtualBox program. It can stop working, even if it was easily launched quite recently or at the time after installation.

Most often, users face that they cannot run exactly a virtual machine, while the VirtualBox manager itself works as usual. But in some cases the window itself does not start, allowing you to create virtual machines and manage them.

Let's deal with how to eliminate these errors.

Situation 1: Unable to execute the first launch of the virtual machine

Problem: When the installation of the VirtualBox program itself and the creation of a virtual machine has been successful, an operating system installation turn arises. It usually happens that when attempting the first launch of the created machine, this error appears:

"Hardware acceleration (VT-X / AMD-V) is not available on your system."

At the same time, other operating systems in VirtualBox can easily start and work without any problems, and with such an error you can face far from the first day of using virtual box.

Solution: You must enable the BIOS virtualization support feature.

Restart the PC, and when you start, press the BIOS input key.
- Way for Award BIOS: Advanced Bios Features - Virtualization Technology (in some versions the name is reduced to Virtualization);
- Path for AMI BIOS: Advanced - Intel (R) VT for Directed I / O (or just Virtualization);
- The path for ASUS UEFI: Advanced - Intel Virtualization Technology.
For non-standard bios, the path may be different:
- SYSTEM Configuration - Virtualization TECHNOLOGY;
- Configuration - Intel Virtual Technology;
- Advanced - Virtualization;
- Advanced - CPU Configuration - Secure Virtual Machine Mode.
If you did not find the settings on the tracks specified above, go through the BIOS sections and find the parameter responsible for virtualization. In his title should be attended by one of the following words: Virtual, VT, Virtualization.
To enable virtualization, put the setting to the Enabled state.
Do not forget to save the selected setting.
After starting the computer, go to the settings of the virtual machine.
Click the "System" tab - "Acceleration" and check the box next to the "Enable VT-X / AMD-V" item.
Turn on the virtual machine and start installing the guest OS.

Situation 2: not launched VirtualBox Manager

Problem: The VirtualBox Manager does not respond to starting attempt, and it does not give any errors. If you look into the "View Events", you can see a record testifying about the launch error.

Solution: rollback, update or reinstalling VirtualBox.

If your version of VirtualBox is outdated or installed / updated with errors, it is enough to reinstall. Virtual machines with installed guest OS at the same time will not go anywhere.

The simplest way is to restore or delete virtual boks through the installation file. Run it and select:

Repair - Correction of errors and problems due to which VirtualBox does not work;
Remove - removal of the VirtualBox manager when the correction does not help.

In some cases, the specific versions of VirtualBox refuse to work correctly with separate PC configurations. There are two outputs:

Wait for the new version of the program. Check the official website www.virtualbox.org and follow upgrades.
Roll into the old version. To do this, first delete the current version. This can be made in the method specified above, or through the "Installation and Delete Programs" in Windows.

Do not forget to backup copies of important folders.

Run the installation file or download the old version from the official website on this link with archival releases.

Situation 3: VirtualBox does not start after updating OS

Problem: As a result of the latest update of the VB operating system, the manager does not open or the virtual machine is launched.

Solution: Waiting for new updates.

The operating system can refresh and become incompatible with the current version of VirtualBox. Usually in such cases, developers promptly release virtual box updates that eliminate such a problem.

Situation 4: Some virtual machines do not start

Problem: If you try to start certain virtual machines, an error or bsod appears.

Solution: Disconnect Hyper-V.

The hypervisor enabled interferes with the launch of the virtual machine.

Open the "Command Line" on behalf of the administrator.
Write the command:
BCDEDIT / SET HYPERVISORLAUNCHTYPE OFF

And press ENTER.
Restart PC.

Situation 5: Errors with Kernel Driver

Problem: When trying to start a virtual machine, an error appears:

"CANNOT ACCESS THE KERNEL DRIVER! Make Sure The Kernel Module Has Been Loaded SuccessFully. "

Solution: Reinstall or update VirtualBox.

Reinstall the current version or update VirtualBox to the new assembly can be the method specified in the "Situation 2".

Problem: Instead of launching a machine with a guest OS (delicately for Linux) an error appears:

"Kernel Driver Not Installed".

Solution: Disconnect Secure Boot.

Users with UEFI instead of the usual Award or AMI BIOS have a Secure Boot feature. It prohibits the launch of non-authorized OS and software.

Restart PC.
During boot, press the BIOS entry key.
- Ways for ASUS:
  Boot - Secure Boot - OS Type - Other OS.
  Boot - Secure Boot - Disabled.
  Security - Secure Boot - Disabled.
- Way for HP: System Configuration - Boot Options - Secure Boot - DSABLED.
- Ways for Acer: Authentication - Secure Boot - Disabled.
  Advanced - System Configuration - Secure Boot - Disabled.
  If you have a laptop Acer, then you will simply fail to disable this setting.
  First go to the Security tab using the SET Supervisor Password, set the password, and then try to disable Secure Boot.
  In some cases, you may need to switch from UEFI to CSM or Legacy Mode.
- Way for Dell: Boot - UEFI BOOT - Disabled.
- The path for Gigabyte: Bios Features - Secure Boot - Included.
- Way for Lenovo and Toshiba: Security - Secure Boot - Disabled.