Integrity error virtualbox

The E_FAIL (0x80004005) error on the Oracle VM VirtualBox prevents you from starting a Virtual Machine session. There are several types of these errors, and you’ll see different messages accompany the error code in separate cases.

So, naturally, there are various possible causes and corresponding fixes. Depending on the nature of your error, you can use the appropriate steps from the guide below.

Reasons for Result Code: E_FAIL (0x80004005)

First, restart your PC and access the VM where you encountered this error. If the error reoccurs, move on to the possible solutions below.

Result Code: E_FAIL (0x80004005) on Particular Virtual Machine

The most common case of this error occurs due to a missing virtual machine file. It usually happens when you force exit the VirtualBox.

This is because the VirtualBox stores all activities to a temporary file during its operation and renames it to the VM file during a normal shutdown.

You can fix this issue by manually renaming the file. Here’s how you can do so:

1. Go to your Virtual Machine file location.
2. In Windows, it is usually C:Users<username>.VirtualBoxMachines<virtualmachine>.
   Here, replace <username> with your user profile name and <virtualmachine> with the VM where you get this error.
3. If <virtualmachine>.vbox does not exist, copy <virtualmachine>.vbox-tmp and name the copied file as <virtualmachine>.vbox

Note: In old versions, the extension is .xml instead of .vbox.

Result Code: E_FAIL (0x80004005) due to Hypervisor

If the error is due to Hypervisor, you’ll likely see VT-x or Hyper-V in the error messages. It’s because Hypervisor conflicts with VirtualBox’s usage of virtualization resources in your system. Try the methods below to debug this issue:

Enable Virtualization in BIOS/UEFI

You must enable Virtualization in your system to operate the VirtualBox. You can do so from your BIOS/UEFI settings.

Check out our article on How to Enable Virtualization in BIOS for more information.

Update VirtualBox

Before, VirtualBox VMs would not run when Hypervision (Hyper-V) was active. So it was impossible to use VirtualBox together with any applications that needed Hyper-V, such as Docker.

However, VirtualBox 6 has introduced experimental support for Hyper-V. So, update VirtualBox to the latest version to avoid this issue.

Restart Hypervisor

If you already use VirtualBox v6+, it is possible that Hypervisor is not running correctly. Resetting its launch type configuration should fix this issue. Here’s how you can do so:

1. Open Run command.
2. Type cmd and press Ctrl + Shift + Enter. It will load the elevated Command Prompt.
3. Type the following command and press Enter to execute it:
   bcdedit /set hypervisorlaunchtype off
   
4. If you have more than one OS, use the command
   bcdedit /set {current} hypervisorlaunchtype off
5. Restart your PC.
6. Open the elevated Command Prompt again and enter:
   bcdedit /set hypervisorlaunchtype auto

Restart your computer and open the virtual machine again.

Disable Hypervisor Processes

As we have mentioned above, the versions before and including VirtualBox 5.x do not support running VMs with active Hypervision. Hyper-V hogs a large portion of virtualization resources and prevents the VirtualBox from launching a VM.

So, you must disable all Hypervision processes to fix this error in those VirtualBox builds. To do so,

1. Open the Run dialog box and enter optionalfeatures. It will direct you to the Turn Windows features on or off wizard.
2. Search for and uncheck the following options:
   • Hyper-V
   • Containers
   • Windows Hypervision Platform
   • Windows Subsystem for Linux
     
3. Close the wizard and open the elevated Command Prompt.
4. Enter the following command: bcdedit /set hypervisorlaunchtype off

Restart your PC and check if the error persists.

Disable Device Guard or Credential Guard

The Device Guard and Credential Guard use virtualization technology to protect your system and credentials from external harm. So, enabling this feature will also take away virtualization resources and cause this error.

You can use one of the following methods to disable this feature:

Through Command Prompt:

Open the elevated Command Prompt and enter the following commands:

mountvol X: /s
copy %WINDIR%System32SecConfig.efi X:EFIMicrosoftBootSecConfig.efi /Y
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "EFIMicrosoftBootSecConfig.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

Note: Replace X with an unused drive.

Through Device Guard and Credential Guard hardware readiness tool:

1. Download the Device Guard and Credential Guard hardware readiness tool.
2. Open PowerShell as administrator and navigate to the location of the downloaded file. 
3. Enter the command DG_Readiness_Tool_v3.6.ps1 -Disable -AutoReboot while replacing v3.6 with the version of the readiness tool.

Disable Memory Integrity

Similar to the above case, Memory Integrity uses virtualization to isolate processes while protecting your core system from external threats. You need to disable this option as well if you encounter the E_FAIL (0x80004005) error.

You can do so by following any one of the ways mentioned below:

Through Settings:

1. Press Win + I to launch Settings.
2. Go to Update & Security > Windows Security > Device security.
   
3. Click Core isolation details.
4. Toggle off Memory integrity.
   

Through Group Policy Editor:

1. Enter gpedit.msc in the Run command.
2. Navigate through: Computer Configuration > Administrative Templates > System > Device Guard.
3. Search for and double-click on Turn on Virtualization Based Security.
4. Check Disabled and Click Ok.

If you use the Home Edition of Windows, here’s how you can Enable Gpedit on your machine.

Result Code: E_FAIL (0x80004005) due to Duplicate Config Values

In this case, you’ll see the message “Duplicate config values’/CPUM/CMPXCHG16B’ and ‘/CPUM/IsaExts/CMPXCHG16B’ – please remove the former! “. Just like the message says, you need to remove the former instruction from the Virtual Machine vbox file. To do so on Windows,

1. Open the elevated Command Prompt.
2. Enter the following commands:
   • cd “%systemdrive%Program FilesOracleVirtualBox”
   • VBoxManage.exe list vms
3. Look for the name of the VBOX machine where you got the E_FAIL (0x80004005) error.
4. Enter the command: VBoxManage.exe setextradata “VBOX Machine” VBoxInternal/CPUM/CMPXCHG16B while replacing “VBOX Machine” with the name from the previous step.
5. Open VirtualBox and launch the VM again and check if the error persists.
6. If the error appears again, close the VirtualBox, go to the Command Prompt and enter: VBoxManage.exe setextradata global VBoxInternal/CPUM/CMPXCHG16B

Other Solutions for Result Code: E_FAIL (0x80004005)

While the sections above involve troubleshooting the most common reasons for this error, there are still some cases where those methods are ineffective. Here are some additional solutions that are applicable in such circumstances.

Manually Run the Process

If opening the VM or mounting an iso file through the VirtualBox causes the error, you can attempt to manually execute these processes.

Go to the VM folder in the file explorer and open the program for the first case. Similarly, instead of mounting the file with the VirtualBox, use the mount feature in your OS to mount it to a virtual disk.

Discard the Session or Snapshot

VirtualBox updates or improper shutdowns can corrupt VM save states and snapshots. You need to discard the save state or the snapshot tree branch to fix this issue.

Disable/Uninstall Interfering Parties

There are many cases of other processes interfering with VirtualBox. The VirtualBox hardening log created after encountering this error should contain additional information on responsible parties. You can check the log or seek help from VirtualBox technical support personnel to diagnose this issue.

The most common third-party programs responsible for this include IBM Security Trusteer Rapport and Cyclance Protect. Many third-party antivirus programs are also known to cause this issue. So, make sure to disable or uninstall these programs.

Some users have also mentioned that they suffered from this error after running the Driver Verifier. To disable this feature, launch Command Prompt as administrator and enter:
verifier /reset

Reinstall to Latest Version

Some of the old versions of VirtualBox had many bugs. So, we recommend updating to the latest edition as soon as possible. It is better to uninstall the old version and install the newest build using its installer. Here are the steps for this process:

On Windows:

1. Download the latest VirtualBox along with the matching ExtPack.
2. Uninstall third-party antivirus if you haven’t already done so.
3. Go to Control Panel > Programs and Features > Uninstall a program and uninstall your VirtualBox application.
   
4. Go to the installer file from step 1.
5. Right-click it and select Run as administrator.
6. Follow the on-screen instructions.
7. On the last installation page, check Start Oracle VM VirtualBox…after installation and click Finish.
8. On the VirtualBox, select File > Preferences > Extensions.
9. Click the icon with a downwards orange arrow and select the ExtPack.
   

On Linux:

Open the terminal and enter the following commands:

sudo apt-get update
sudo apt-get purge virtualbox
sudo apt-get purge virtualbox-ext-pack
sudo apt-get install virtualbox
sudo apt-get install virtualbox-ext-pack

Restart VirtualBox and check if you encounter the 0x80004005 error.

Roll-back to Old Version

The latest versions of VirtualBox no longer support old Operating Systems like Windows 7. You will have to roll-back to an earlier version of VirtualBox in such cases. Check which version works and download its installer. Then install it using the steps from the above method.

It is also possible for the latest versions to contain some unresolved bugs. You should roll back to the last stable version until a new update appears in such cases.

Reset Network Adapters

Some minor issues with the VM network adapters have been known to cause this error as well. It mostly happens after an update. You need to reset the network adapter to fix this issue. To do so,

1. Select your VM and click Settings.
2. Go to Network and uncheck Enable Network Adapter.
   
3. Start the VM while the network adapter is disabled.
4. Close the VM properly and enable the Network Adapter again.

Now launch the VM again and check if the error reoccurs.

You can also enter the following commands on the PowerShell to reset Network Adapters for VirtualBox:
disable-netadapter -InterfaceDescription "VirtualBox*" -confirm:$false
enable-netadapter -InterfaceDescription "VirtualBox*" -confirm:$false

Install VirtualBox Driver

VirtualBox uses VBoxDrv.inf as a driver. It should automatically install on your system while installing the VirtualBox. However, the installation process is known to fail in some cases.

You need to manually install it to fix the issue. Here’s how you can do so: 

1. Go to the driver installer folder.
2. In the default installation on Windows, it should be in:
   C:Program FilesOracleVirtualBoxdriversvboxdrv
3. Right-click on VBocDrv.inf and select Install.
   

Update Graphics Drivers

This error can also happen if the application tries to access an invalid memory address. It occurs mostly because of a graphics-related DLL. Update your graphics card driver to fix this issue. Follow the steps below to do so,

1. Enter devmgmt.msc on the Run command.
2. Expand Display Adapters and right-click on your graphics device.
3. Select Update Driver.
   
4. Click Search automatically for drivers.

Restart your PC.

If your graphics driver is fully updated, you can uninstall it and restart your system to reinstall the driver. It will fix any minor errors present in the driver.

Repair System Corruption

Missing or corrupted DLL files are responsible for several system and application errors. If you encounter the E_FAIL (0x80004005) error, it is worth running the System File Checker to repair the DLL files.

A lot of users receive the “VBOX_E_FILE_ERROR (0x80BB0004)” error message when trying to attach a virtual disk or export a created appliance into VM. Don’t worry. This post of MiniTool summarizes 8 effective ways to fix it.

Possible Reasons for the VBOX_E_FILE_ERROR (0x80bb0004)

After investigating extensive user reports on forums, we found the VBOX_E_FILE_ERROR (0x80BB0004) error code usually appears in two situations. The first situation is when they were trying to attach a virtual disk to the virtual machine using VirtualBox. The other is when they failed to export a previously created appliance into VM.

According to user reports, the several common scenarios below will trigger the result code: VBOX_E_FILE_ERROR (0x80BB0004).

• The .vdi or .vmdk file gets corrupted or missing. A lot of users encounter the error when they failed to import a virtual appliance that was torrent files downloaded via a brave browser. This error could occur due to an incomplete download or a network issue.
• The path of the created appliance doesn’t exist in the current laptop. It often occurs when importing a virtual machine that contains multiple appliances into a new laptop. For instance, some users find that the original VM path was “drive I:” which doesn’t exist on the new laptop. In this case, you can fix it by changing its path to a C drive.
• The vbomxmanage.exe lacks administrator privileges. This situation is mostly reported to happen when trying to attach a virtual disk hosted on a USB flash drive.
• The .vdi or .vmdk file is saved on a drive that has bad sectors. If the vdi file contains bad sectors, the error can occur due to file corruption.
• The VM disk image format is incorrect. Some users find the “failed to import appliance VirtualBox” error can occur when the image became other formats like “.qcow” or “.vhd”. The error can disappear after converting it to VDI.
• The saved state file inside .vbox is invalid. Some users get the error 0x80BB0004 in the log file after VM refused to start. This can occur due to an invalid saved state file.
• The virtual machine configuration gets outdated or corrupted. It is also responsible for the VirtualBox failed to import appliance error. For that, you can create a new virtual machine.
• The VM VirtualBox installation is corrupted. Some users have managed to fix the error by uninstalling the whole VirtualBox client.

How to Fix the VBOX_E_FILE_ERROR (0x80bb0004)

Based on the above analysis, we summarize several effective ways to fix the VBOX_E_FILE_ERROR. Let’s try them one by one.

Solution 1. Re-download the .vmdk or .vdi File

If download the .vmdk or vdi file via a brave browser instead of a torrent client, then the file may get corrupted or incomplete. That’s why you receive the “result code: VBOX_E_FILE_ERROR (0x80BB0004)” error when importing a virtual appliance into VM. In this case, you need to re-download the file using a torrent client like QBitTorrent or download via HTTPS directly.

Solution 2. Change the Path of the Created Appliance to C Drive

A lot of users get the error 0x80BB0004 after exporting a virtual machine into a new laptop. This is because the drive path of the VM doesn’t exist in the laptop. In this case, you need to change the path of the VM to C drive. Also, you can create a new partition and assign a correct drive letter to it, and transfer the VM into the new partition. Once done, you can reboot the virtual machine from the drive and check if the error code disappears.

Solution 3. Run Vboxmanage.exe File as Administrator

If the VirtualBox failed to import appliance error stuck on an Access Denied error, it is possible that you are not running the vboxmanage.exe file with administrator privileges. This is because accessing a virtual disk hosted on a USB drive requires Admin rights. To avoid the error code, we recommend you run both VirtualBox and vboxmanage.exe as administrators.

Step 1. Right-click the VirtualBox shortcut on your desktop and select Properties.

Step 2. In the Properties window, navigate to the Compatibility tab and tick the checkbox next to Run this program as an administrator. Then click on OK to save the change.

Step 3. Press Win + E keys to open the File Explorer, and then find the vboxmanage.exe file and run it as administrator by following the above 2 steps.

Solution 4. Check Bad Sectors on the Hard Drive

Another common reason for the “failed to import appliance VirtualBox” error is that the .vdi or .vmdk contains bad sectors. To fully check hard drive errors, we highly recommend you use the professional utility – MiniTool Partition Wizard. It is a reliable multifunctional partition manager that can help you convert MBR to GPT, recover lost data, migrate OS, etc.

Free Download

Step 1. In the main interface of this program, select the hard disk that contains the vdi/vmdk file and click on the Surface Test from the left pane.

Step 2. Click on the Start now button in the pop-up window. After that, this program will scan the whole disk immediately and show you the test result.

Step 3. Once any bad sectors are tested, you will the red blocks in the disk map. To mark the bad sectors as unusable, you can utilize the CHKDSK utility. Specifically, you can run Command Prompt as administrator, and then type chkdsk /f /r command and hit Enter in the elevated command prompt.

Once done, you can reboot your computer. Then re-download the .vdi file and use it to create a VM, and check if the error is fixed.

Solution 5. Convert the Virtual Disk Image into VDI

In some cases, users get the “result code: VBOX_E_FILE_ERROR (0x80BB0004)” accompanied with the “file not accessible or erroneous file contents” message. If you find the virtual disk image inside the VM is .vhd or .qcom instead of the .vdi format, then you may encounter the issue. To fix it, you need to convert the disk image into .vdi. For that:

Step 1. Navigate to the VirtualBox installation that is mostly located at C:Program FilesOracleVirtualBox, and then find the .vhd file inside the VirtualBox folder and write down its path.

Step 2. Type cmd in the search box, and then right-click the Command Prompt app and select Run as administrator.

Step 3. In the elevated command prompt, type the following command and hit Enter. Here make sure you change the correct path of the .vhd file. For example, the file path is C:Program FilesOracleVirtualBoxWindows 8.vhd.

VBoxManage.exe clonemedium disk «C:Program FilesOracleVirtualBoxWindows 8.vhd» —format vdi

Solution 6. Delete the Saved State Value in the .vbox File

Some users get the VBOX_E_FILE_ERROR (0x80BB0004) error after VM refused to start. In the log file, they find the “VM cannot start because the saved state file is invalid, VERR_FILE_NOT_FOUND” error message. If you are in this situation, you can try deleting the saved state file and restart VM. This method has been proven by some affected users to be helpful.

Step 1. Open the File Explorer and navigate to the C:UsersmeVirtualBox VMs Snapshots path.

Step 2. Open the Snapshots folder and find the .vbox file (its XML) inside it. Then right-click it and select Open with Notepad.

Step 3. Find the Variable LastStateChange and delete it. And also delete the stateFile= Snapshots value.

Step 4. Press Ctrl + S keys to save changes and restart the VM.

Solution 7. Create a New Virtual Machine

Some users managed to resolve the VirtualBox failed to import appliance error by creating a new virtual machine. Here is a full guide on how to do that:

Step 1. Launch your Oracle VM VirtualBox as administrator, and then select the New button from the top toolbar and select an OS that you want to create.

Step 2. In the pop-up window, name your virtual machine, and select the Machine Folder from File Explorer, and then select the Type and Version of the operating system. After that, click on Next to go on.

Step 3. Select the allocated memory size for the VM by using the blue toggle and click on Next to continue. Here the recommended memory size is 1024MB.

Step 4. Now, you need to select a virtual disk for the VM. Here we take the Use an existing virtual hard disk file option for example, and then click on the Folder icon and browse to the location of the .vdi file. Then click on Create to confirm it.

Step 5. Wait for the process to complete. Once done, you can repeat the steps that you provoke the error 0x80BB0004 and see if it has been solved.

Solution 8. Reinstall Oracle VirtualBox

If all the above methods can’t help you fix the error, then you may have to consider reinstalling Oracle VirtualBox Manager. To do so, follow the steps below:

Step 1. Press Win + R keys to open the Run dialog box, and then type appwiz.cpl in the box and hit Enter to open Programs and Features.

Step 2. Scroll down the list of installed programs to find Oracle VM VirtualBox, and then right-click it and select Uninstall. Click on Yes/Uninstall in the confirmation prompt and follow the on-screen to complete the uninstallation.

Step 3. Once installed, restart your computer and click here to re-download the VirtualBox manager.

Step 4. The VirtualBox packages vary from different operating systems. Make sure you select the correct one.

Step 5. Open the executable file in the installation folder and follow the on-screen instructions to reinstall the program on your computer.

Now, you can try attaching the virtual disk to the VM and check if the error code disappears.

Are you still troubled by the VBOX_E_FILE_ERROR (0x80BB0004)? You can get 8 applicable methods from this post now! Click to Tweet

Have a Try Now

How to fix VBOX_E_FILE_ERROR (0x80BB0004)? The top 8 solutions have been told to you. Now, it’s your turn to have a try. If you have any other ideas on this topic, you can leave them in the comment area below. For any difficulties in using MiniTool Partition Wizard, you can send us an email at [email protected].

При попытке запуска операционной системы Windows или Linux в виртуальной машине VirtualBox пользователь может столкнуться с ошибкой 0x80004005. Она возникает до старта ОС и препятствует любой попытке ее загрузки. Есть сразу несколько способов, помогающих устранить существующую проблему и продолжить пользоваться гостевой системой в обычном режиме.

Ситуаций, из-за которых не получается открыть сессию для виртуальной машины, может быть несколько. Зачастую данная ошибка возникает спонтанно: еще вчера вы спокойно работали в операционной системе на VirtualBox, а сегодня выполнить то же самое не удается из-за сбоя при запуске сессии. Но в некоторых случаях не удается выполнить первичный (установочный) запуск ОС.

Это может произойти вследствие одной из следующих причин:

1. Ошибка при сохранении последней сессии.
2. Отключенная поддержка виртуализации в BIOS.
3. Некорректно работающая версия VirtualBox.
4. Конфликт гипервизора (Hyper-V) с VirtualBox на 64-разрядных системах.
5. Проблемное обновление хостовой Windows.

Далее мы рассмотрим, как устранить каждую из этих проблем и начать/продолжить пользоваться виртуальной машиной.

Способ 1: Переименование внутренних файлов

Сохранение сессии может завершиться ошибочно, в результате чего последующий ее запуск будет невозможен. В этом случае достаточно выполнить переименование файлов, связанных с запуском гостевой ОС.

Для выполнения дальнейших действий вам необходимо включить отображение расширений файлов. Это можно сделать через «Параметры папок» (в Windows 7) или «Параметры Проводника» (в Windows 10).

1. Откройте папку, где хранится файл, отвечающий за запуск операционной системы, т.е. сам образ. Он располагается в папке VirtualBox VMs, место сохранения которой вы выбирали при установке самой VirtualBox. Обычно она находится в корне диска (диска С или диска D, если HDD разбит на 2 раздела). Также она может располагаться в персональной папке пользователя по пути:

   С:UsersИМЯ_ПОЛЬЗОВАТЕЛЯVirtualBox VMsИМЯ_ГОСТЕВОЙ_ОС
2. В папке с операционной системой, которую вы хотите запустить, должны быть следующие файлы: Name.vbox и Name.vbox-prev. Вместо Name будет имя вашей гостевой операционной системы.
   

   Скопируйте файл Name.vbox в другое место, например, на рабочий стол.

3. Файл Name.vbox-prev необходимо переименовать вместо перемещенного файла Name.vbox, то есть удалить «-prev».
   
4. Эти же действия необходимо проделать и внутри другой папки, находящейся по следующему адресу:

   C:UsersИМЯ_ПОЛЬЗОВАТЕЛЯ.VirtualBox
   

   Здесь вы будете менять файл VirtualBox.xml — скопируйте его в любое другое место.

5. У файла VirtualBox.xml-prev удалите приписку «–prev», чтобы получилось имя VirtualBox.xml.
   
6. Попробуйте запустить операционную систему. Если не сработало, восстановите все назад.

Способ 2: Включение поддержки виртуализации в BIOS

Если вы решили воспользоваться ВиртуалБокс впервые, и сразу же столкнулись с вышеупомянутой ошибкой, то, возможно, загвоздка кроется в не настроенном BIOS для работы с технологией виртуализации.

Чтобы осуществить запуск виртуальной машины, в БИОС достаточно включить всего лишь одну настройку, которая называется Intel Virtualization Technology.

• В Award BIOS путь к этой настройке следующий: Advanced BIOS Features > Virtualization Technology (или просто Virtualization) > Enabled.

  

• В AMI BIOS: Advanced > Intel(R) VT for Directed I/O > Enabled.

  

• В ASUS UEFI: Advanced > Intel Virtualization Technology > Enabled.

  

Настройка может иметь и другой путь (например, в BIOS на ноутбуках HP или в БИОС Insyde H20 Setup Utility):

• System Configuration > Virtualization Technology > Enabled;
• Configuration > Intel Virtual Technology > Enabled;
• Advanced > Virtualization > Enabled.

Если вы не нашли данной настройки в своей версии BIOS, то ищите ее вручную во всех пунктах меню по ключевым словам virtualization, virtual, VT. Для включения выбирайте состояние Enabled.

Способ 3: Обновление VirtualBox

Возможно, состоялось очередное обновление программы до последней версии, после чего и появилась ошибка запуска «E_FAIL 0x80004005». Есть два выхода из сложившейся ситуации:

1. Дождитесь выхода стабильной версии VirtualBox.

   Те, кто не хочет заморачиваться с выбором рабочей версии программы, может просто дождаться обновления. Узнать о выходе новой версии можно на официальном сайте VirtualBox или через интерфейс программы:

   1. Запустите Менеджер виртуальных машин.
   2. Нажмите «Файл» > «Проверить обновления…».

      

   3. Дождитесь проверки и при необходимости установите обновление.
2. Переустановите VirtualBox на текущую или предыдущую версию.
   1. Если у вас есть установочный файл VirtualBox, то используйте его для переустановки. Для повторного скачивания актуальной или предыдущей версии перейдите по этой ссылке.
   2. Нажмите на ссылку, ведущую к странице со списком всех предыдущих релизов для текущей версии VirtualBox.

      

   3. Выберите подходящую для хостовой ОС сборку и скачайте ее.

      

   4. Для переустановки установленной версии VirtualBox: запустите инсталлятор и в окне с типом установки выберите «Repair». Установите программу в обычном режиме.

      

   5. Если вы делаете откат до предыдущей версии, то лучше сперва удалить VirtualBox через «Установку и удаление программ» в Windows.

      

      Или через установщик VirtualBox.

      

      Не забудьте сделать резервные копии своих папок с образами ОС.

Способ 4: Отключение Hyper-V

Hyper-V — система виртуализации для 64-разрядных систем. Иногда у нее может возникнуть конфликт с VirtualBox, что и провоцирует появление ошибки при старте сессии для виртуальной машины.

Для отключения гипервизора выполните следующее:

1. Запустите «Панель управления».
   
2. Включите просмотр по значкам. Выберите пункт «Программы и компоненты».

   

3. В левой части окна нажмите на ссылку «Включение или отключение компонентов Windows».

   

4. В открывшемся окне необходимо снять галочку с компонента Hyper-V, а затем нажать «ОК».

   

5. Перезагрузите компьютер (необязательно) и попробуйте запустить ОС в VirtualBox.

Способ 5: Изменение типа запуска гостевой ОС

В качестве временного решения (например, до выпуска новой версии VirtualBox) можно попробовать изменить тип запуска ОС. Этот способ помогает не во всех случаях, но, возможно, сработает у вас.

1. Запустите Менеджер VirtualBox.
2. Нажмите по проблемной операционной системе правой кнопкой мыши, наведите курсор на пункт «Запустить» и выберите вариант «Запуск в фоновом режиме с интерфейсом».

   

Данная функция доступна только в VirtualBox, начиная с версии 5.0.

Способ 6: Удаление/исправление обновления Windows 7

Этот способ считается устаревшим, поскольку после неудачного патча KB3004394, приводящего к прекращению работы виртуальных машин в ВиртуалБокс, была выпущена заплатка KB3024777, устраняющая данную проблему.

Тем не менее, если у вас на компьютере по каким-то причинам отсутствует фикс-патч, а проблемный присутствует, то есть смысл либо удалить KB3004394, либо установить KB3024777.

Удаление KB3004394:

1. Откройте «Командную строку» с правами администратора. Для этого откройте окно «Пуск», напишите cmd, правым кликом мыши выберите пункт «Запустить от имени администратора».

   

2. Пропишите команду

   wusa /uninstall /kb:3004394

   и нажмите Enter.

   

3. После выполнения этого действия может потребоваться перезагрузка компьютера.
4. Попробуйте еще раз запустить гостевую ОС в ВиртуалБоксе.

Установка KB3024777:

1. Перейдите по этой ссылке на сайт Microsoft.
2. Скачайте версию файла с учетом разрядности своей ОС.

   

3. Установите файл вручную, если необходимо, перезагрузите ПК.
4. Проверьте запуск виртуальной машины в VirtualBox.

В подавляющем большинстве случаев точное выполнение данных рекомендаций приводит к устранению ошибки 0x80004005, и пользователь может без труда начать или продолжить работать с виртуальной машиной.