Cannot access the kernel driver virtualbox как исправить

Обновлено: 02.07.2024

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

И затем идут подробности ошибки, с указанием технических данных:

The virtual machine 'Название виртуальной машины' has terminated unexpectedly during startup.
Код ошибки: E_FAIL (0x80004005)
Компонент: Machine
Интерфейс: IMachine

Пошаговая инструкция по устранению этой ошибки:

Шаг 1. Переходим в папку

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

Шаг 2. Находим нужный файл

В открытой папке будет всего 3 файла. Нам нужен файл VBoxDrv.inf - обычно он находится посередине от остальных. На некоторых операционных системах иконка файлика будет с шестеренкой.

Шаг 3. Нажимаем на файле правой кнопкой мыши, и выбираем пункт "Установить" - он будет сверху, обычно вторым.

Шаг 4. Запускаем виртуальную машину. Если вышла ошибка - перезагрузите сам сервер.

Если при запуске виртуальной машины в Oracle VM Virtualbox у вас появляется ошибка "Cannot access the kernel driver" , значит по какой то причине не произошла установка всех необходимых драйверов, и один их них нужно доставить вручную.

Алгоритм действий следующий:

1. Заходим в %ProgramFiles%\Oracle\VirtualBox\drivers\vboxdrv

VirtualBox: Cannot access the kernel driver

When I try to launch VM in Oracle VirtualBox on Windows 10 it says "Cannot access the kernel driver". I tried complete reinstall (remove everything and install), repair installation (repair in the installer) and installing 2 drivers manually (VBoxUSBMon and VBoxDrv). Nothing worked. I'm using VirtualBox 4.3.12 because I was not able to launch newer version on Windows 10 for some reason.

165 1 1 gold badge 1 1 silver badge 7 7 bronze badges

VirtualBox error : kernel driver not installed(rc=-1908) [closed]

Closed 8 months ago .

I tried to set up an virtual machine on Ubuntu 12.10.I installed Oracle Vm VirtualBox Manager. Then, i followed the steps and i choose .iso file from settings>storage.Then clicked live cd/dvd option.Then OK,when i clicked to start button i get such an error :

I reinstalled program and rebooted pc, but not worked.Also, updated kernel driver but not worked.What can be done to solve it ?

18 Answers 18

Thought I'd give my 2 cents for those who use MACs

@ChristophH. I did the same as Jannik mentioned. I ran the command then went to Security & Privacy, allowed Oracle, then ran the command again. It should work the second time. VirtualBox has to be closed and it will work on MacOS Big Sur

ps. I have this issue everytime I get a Linux kernel update in Ubuntu. The instructions that it gives do not work for me but these two commands work everytime. It would be nice if everytime I got a kernel update these two commands would automatically run afterwards.

10.3k 10 10 gold badges 51 51 silver badges 73 73 bronze badges In my case (Ubuntu 20.04) I have to do the same, for each kernel update: sudo apt-get remove virtualbox-dkms sudo apt-get install virtualbox-dkms sudo modprobe vboxdrv the restart the VirtualBox application `

I have a solution that works for MacOS users:

You have to restart your system and press Command (⌘) + R during the loading. It will start the Recovery mode.

Now that you're on the Recovery Mode, click on Utilities (top bar) and Terminal.

You have your terminal opened? Enter, it will add Oracle in the authorisation list to access the kernel.

spctl kext-consent add VB5E2TV963

382 2 2 gold badges 6 6 silver badges 12 12 bronze badges This helped me. Also after 4. restart again. 5. start virtualbox, then start your vm and open system prefs --> security --> and you will Allow button. Now you can see it and press For Mac Users. Nothing in these threads worked for me. So, I found my own solution, Homebrew. I deleted VirtualBox from Applications in Finder. Then, I installed VirtualBox via Homebrew with the command brew install --cask virtualbox. Follow this link for more information - formulae.brew.sh/cask/virtualbox

(I'm on a Mac with this solution) I tried the first few answers on this board (so you might need those as well first), but then finally I Allowed Oracle to "load software" under System Preferences -> Security & Privacy -> in the bottom right, click "Allow. " Then a dialog box with checkbox options might come up, search for Oracle and check the box next to it. Click OK out of everything. (I also updated the preference above the "Allow. " button to Allow apps downloaded from: to "App store and identified developers") After all of this I rebooted and I no longer see this -1908 error when running a VM. Again, I'm on a Mac, running Big Sur 11.2.1.

23.9k 20 20 gold badges 60 60 silver badges 112 112 bronze badges

Goto BIOS setup and Make secure boot Disable It worked for me.

did you try the command /etc/init.d/vboxdrv setup What was the output ?

bash : /etc/init.d/vboxdrv setup : No such file or directory actually,yes i did but i dont know how it went to a way it works, there are lots of recommendations on the internet, it isnt true but i applied whatever i saw, then boom, it works, i hope you find the way how actually it works.

Had recently the same problem on Ubuntu 18.04. Apparently, virtual box 6.+ has some issues with gcc-7. These steps did the job for me:

sudo apt-get purge virtualbox-*

sudo apt-get install gcc-8 g++-8

setting default gcc to gcc-8

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 800 --slave /usr/bin/g++ g++ /usr/bin/g++-8

Cannot boot Windows guest in VirtualBox without kernel module error

I'm running Vagrant (1.8.1) + VirtualBox (5.0.12) on Windows 7 and trying to boot up a Windows 7 image (modernIE/w7-ie8). However, I get this error:

I ran the query command, but the service "is not found".

I tried rebooting, too. Nothing.

20.7k 20 20 gold badges 96 96 silver badges 177 177 bronze badges

9 Answers 9

The problem is with the installer. The new location of the driver is at C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys . However the installer points to the old driver location of C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys .

To fix the problem you need to point the registry value to the new location. Step to do that:

Close VirtualBox
Open regedit.exe from the Start Menu
Navigate to HKEY_LOCAL_MACHINE\system\currentcontrolset\services\vboxdrv
Double click the name ImagePath
Change the value from \??\C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys to \??\C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys
Restart VirtualBox

I found this answer in the VirtualBox Forum

what if there is no VBoxDrv? the only directory there similar to what you said is VBoxNetAdp

Downgrade to VirtualBox 4.3.10.

165 1 1 gold badge 1 1 silver badge 7 7 bronze badges Thank you for advice. Here is December 2018 year. Bug with "Cannot access the kernel driver" not fixed. There is Virtual Box ver. 6 and it is not working so virtual Box was downgraded to ver. 4.3.10 This is holy shit.

I have VirtualBox 4.3.14 and I got the "Cannot access the kernel driver" . I did the traditional repair ,reboot and didn't solve a thing.

After a manual installation of these drivers everything works again.

C:\Program Files\Oracle\VirtualBox\drivers\USB\filter Select VBoxUSBMon.inf and click the right mouse button. Then pick Install.

C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv Select VBoxDrv.inf and click the right mouse button. Then pick install.

VirtualBox should now work again as expected. I hope this helps ! :D

532 1 1 gold badge 6 6 silver badges 14 14 bronze badges This seems to have solved the problem for me on 4.3.30, after a reboot to trigger a restart of the service.

I went to Control Panel > Programs and Feature (or right click Windows logo) then selected Oracle VM VirtualBox(4.3.12) and then hit repair at the top. I restarted then it worked!! Im running windows 10.0 Home

This worked fine for me after trying all that is mentioned above.

Download an old copy of your Virtualbox installer (make sure it's the same version!)
Run the installer
Select "Repair"
Reboot
Uninstall the old version
Install the new version

3,830 2 2 gold badges 27 27 silver badges 45 45 bronze badges

Just faced this problem after updating to virtual box 6.1.2 version in windows.

The answer by AllanT worked for me, except that it required one more step:

Execute this from the command line as admin: sc.exe start vboxdrv (restarting the vbox service was not enough).

Note: I would've added this as a comment to AllanT's post but I still don't have enough rep!

Just wanted to add, I had this problem on Windows 10. None of the fixes I found worked. Turned out it was due to Trusteer Endpoint Protection, which once uninstalled fixed this perfectly.

This is because VirtualBox gets confused about some of their files and settings. When i updated my VirtualBox to 6.0.14 from 6.0.10 then i got this error.

In my case i just deleted C>Username>Program Files>Oracle>VirtualBox folder. And after that i uninstalled VirtualBox from my machine.

After these steps i did a simple fresh install of VirtualBox on my machine and this solves my issue. Hope you also got some help.

4 Answers 4

I am on windows 10 and following steps works for me:

Navigate to "C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv"
Right click on "VBoxDrv.inf" file and select Install option

Open the Console as a administrator and run the following command

101k 15 15 gold badges 226 226 silver badges 310 310 bronze badges

2,569 2 2 gold badges 15 15 silver badges 14 14 bronze badges Just had the same issue! This worked for VirtualBox 5.1.6 version. Confirmed to work on Windows 10 Pro running VirtualBox 5.1.8 I tried your solution on Windows 7, VB 5.1.22. But after executing the command, its showing error "A device attached to the system not functioning". Any idea how to fix that?

There's something wrong with the installation of VirtualBox (I've been seeing reports of this problem as far back as 4.x). The installer registers an incorrect location for the driver SYS file (the ImagePath in this example).

Читайте также: