Home Oracle VirtualBox Solve “Result Code: NS_ERROR_FAILURE (0x80004005)” VirtualBox Error In Arch Linux

Solve “Result Code: NS_ERROR_FAILURE (0x80004005)” VirtualBox Error In Arch Linux

By sk
Published: Last Updated on 47.9K views

I just upgraded to kernel 4.18.7 in my Arch Linux system and it broke the VirtualBox. VirtualBox has stopped working after updating the kernel. When I start a VM, I got this error:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing


as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

And this error too:

The virtual machine 'Ubuntu 18.04 LTS Server' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code:NS_ERROR_FAILURE (0x80004005)
Interface:IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
VirtualBox Error

VirtualBox Error

Weird? I ran the command the following command as suggested in the first image to reinstall the kernel module.

$ sudo /sbin/vboxconfig

But my Arch Linux systems said there was no such command:

sudo: /sbin/vboxconfig: command not found

Then, I head over to Arch Linux forum. While looking through the forum, someone has suggested to run this command:

$ sudo modprobe vboxdrv

And.. I got this error:

modprobe: ERROR: could not insert 'vboxdrv': Exec format error

After spending few more minutes on the forum, finally I fixed this error by updating virtualbox-host-modules package.

If ever run into this error, all you have to do is update your virtualbox-host-modules package or better run a complete update.

To do so, simply run:

$ sudo pacman -Syyu

Finally, run this command to reload the kernel module:

$ sudo /sbin/rcvboxdrv setup
Unloading modules: 
Loading modules: vboxnetadp vboxnetflt vboxpci vboxdrv

VirtualBox should work now.

For Ubuntu systems, refer this link:

This guide is bit old. I can't guarantee this guide still applies to the new kernel.


If you still get the same error, find the installed virtualbox host modules:

$ pacman -Q | grep virtual
virtualbox 5.2.18-1
virtualbox-guest-iso 5.2.18-1
virtualbox-host-modules-arch 5.2.18-8
virtualbox-sdk 5.2.18-1

And, replace virtualbox-host-modules-arch package with virtualbox-host-dkms
package like below.

$ sudo pacman -Syu
$ sudo pacman -S virtualbox-host-dkms

You will prompted to remove virtualbox-host-modules-arch package. Just type Y and hit ENTER to install virtualbox-host-dkms.

Make sure you have installed the kernel headers:

$ sudo pacman -S linux-headers

Finally, run the following commands:

$ sudo modprobe vboxdrv
$ sudo /sbin/rcvboxdrv setup

Reboot the system and now VirtualBox should work.

Related read:

You May Also Like


Gerard Arthus March 19, 2018 - 10:30 am

Worked great, many thanks.

Waket Zheng September 24, 2018 - 12:39 am

Worked! Thanks.

Ostheer December 7, 2018 - 8:07 pm

In order to install the correct host modules for your kernel, you must specify which ones you want to install.
Refer to Lynob’s answer on https://unix.stackexchange.com/questions/202396/manjaro-module-vboxdrv-not-found.

In essence, do:
sudo pacman -S linux316-virtualbox-host-modules
where ‘linux316’ should be altered to you appropriate kernel version.

elias January 17, 2019 - 2:26 pm

i try to start centOs 7 in virtual box and i still get the same error
Result Code:
NS_ERROR_FAILURE (0x80004005)

what should i do ?

Emanuel February 19, 2019 - 9:35 pm

I received the same error. It was caused by the `/usr/` directory not being owned by root.

ron April 6, 2019 - 1:04 am

DOESN’T WORK! I get this message (Ubuntu 16.04):
~$ sudo pacman -Syyu
[sudo] Passwort für ich:
sudo: pacman: Befehl nicht gefunden
(=means “pacman” command not found).
What is “pacman, anyway??

sk April 6, 2019 - 12:38 pm

This tutorial is for Arch Linux, not Ubuntu. Pacman is not available in Ubuntu.

Xeon November 25, 2019 - 12:45 am

Erase the file ~/.config/VirtualBox/VirtualBox.xml, and then load manualy the virtual’s machine again.

Piyush Bisen December 6, 2019 - 1:03 pm

Thanks, It really saved me.

SrimalPriyanga March 21, 2020 - 8:45 am

Host: Ubuntu 18.04
Guest: Windows 10
The machine was work smoothly until unexpectedly this error occurs
Result Code: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap
******* Solution ******
I haven’t made any update or any changes to host or guest recently, Therefor I looked carefully “VirtualBox VM” folder and recognize
” *.vbox ” file name has changed as follows ” Windows10-1.15-linux.vbox ” so first I rename the file as ” Windows10.vbox” now vdi and vbox file appear as follows
” Windows10.vbox ”
” Windows10.vdi ”

close all the windows and restart both Host and Guest, IT’S WORKING …!!
In my case this the simple solution that worked for me. 😀

Mario August 3, 2022 - 9:01 am

2022 Update: You need to install the latest Virtualbox Extension Pack version


Leave a Comment

* By using this form you agree with the storage and handling of your data by this website.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

This website uses cookies to improve your experience. By using this site, we will assume that you're OK with it. Accept Read More