Virtualization New Added 19 September 2026

VirtualBox: Kernel driver not installed (rc=-1908)

The vboxdrv module is missing or refused to load, which normally follows a kernel upgrade that left the DKMS build behind. On a machine with Secure Boot the module builds correctly and is then rejected at load time because it is unsigned, which is a different failure with the same message.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

# Is the module there at all
lsmod | grep vboxdrv
sudo modprobe vboxdrv && echo loaded

# Rebuild it for the running kernel
sudo apt install -y linux-headers-$(uname -r) dkms
sudo /sbin/vboxconfig            # or: sudo dpkg-reconfigure virtualbox-dkms

# Secure Boot rejects unsigned modules: the build succeeds, the load does not
mokutil --sb-state
dmesg | grep -i -E 'vboxdrv|key was rejected'

# Sign it yourself and enrol the key, then reboot and confirm at the MOK prompt
sudo mokutil --import /var/lib/shim-signed/mok/MOK.der

# Your user needs the group, otherwise USB and some devices fail later
sudo usermod -aG vboxusers $USER

# The other reason a fresh install fails: KVM already holds the CPU extensions
lsmod | grep -E '^kvm'

How to diagnose Virtualization errors

Virtualisation errors are usually about hardware virtualisation access: either it is disabled in firmware, or another hypervisor already holds it. On Windows, Hyper-V, WSL 2, Docker Desktop, Credential Guard and memory integrity all claim the virtualisation extensions, and VirtualBox or VMware then fails with a message that mentions VT-x but not the actual conflict.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Confirm virtualisation is enabled at the CPU level: grep -E 'vmx|svm' /proc/cpuinfo on Linux, or the Performance tab of Task Manager on Windows.
On Windows, check what else is using the hypervisor: bcdedit /enum | findstr hypervisorlaunchtype and whether Hyper-V, WSL 2 or Core Isolation are enabled.
On Linux, check /dev/kvm exists and that your user is in the kvm group; nested virtualisation must be enabled explicitly on cloud VMs.
Match guest additions and tools versions to the hypervisor version: mismatches cause shared folders, clipboard and display problems that look like guest OS bugs.
For WSL, run wsl --status and wsl --update; most WSL 2 errors are a stale kernel or a disabled Virtual Machine Platform feature.

Tools worth reaching for

grep -E 'vmx|svm' /proc/cpuinfo
wsl --status
bcdedit /enum
ls -l /dev/kvm
systemctl status libvirtd

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

virtualbox.org virtualbox.org

Related Virtualization errors

See all 11 Virtualization errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.