Started up just fine 2 days ago on Win10 host. Saved the state and shut it down and now tried starting it back up but getting this error message. Posting to see if there are any other options besides deleting the snapshot and having to lose everything again. Thanks in advance for the help.
Failed to open a session for the virtual machine Kali-Linux-2021.1-vbox-amd64.
Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed (VERR_LDR_GENERAL_FAILURE).
Failed to load VMMR0.r0 (VERR_LDR_GENERAL_FAILURE).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
E_FAIL (0x80004005) Failed to load VMMR0.r0
-
- Posts: 7
- Joined: 14. Nov 2021, 19:29
- Primary OS: MS Windows 10
- VBox Version: OSE Debian
- Guest OSses: Kali Linux
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: E_FAIL (0x80004005) Failed to load VMMR0.r0
This error is happening lately because of a bug in 6.1.28 on Windows 10 hosts.
You don't mention your Virtualbox version, but if you are running 6.1.28, roll back to 6.1.26, see https://www.virtualbox.org/wiki/Download_Old_Builds_6_1
Or disable Hyper-V on your Windows host OS, see HMR3Init: Attempting fall back to NEM (Hyper-V is active).
Note that saved states are not compatible with Virtualbox version changes. If you upgraded to 6.1.28 from an earlier version, you need to go back to that earlier version to get the save-stated VM to start again, then shut it down fully. Then you can upgrade if needed (but not to 6.1.28 if you need Hyper-V enabled).
You don't mention your Virtualbox version, but if you are running 6.1.28, roll back to 6.1.26, see https://www.virtualbox.org/wiki/Download_Old_Builds_6_1
Or disable Hyper-V on your Windows host OS, see HMR3Init: Attempting fall back to NEM (Hyper-V is active).
Note that saved states are not compatible with Virtualbox version changes. If you upgraded to 6.1.28 from an earlier version, you need to go back to that earlier version to get the save-stated VM to start again, then shut it down fully. Then you can upgrade if needed (but not to 6.1.28 if you need Hyper-V enabled).
-
- Posts: 7
- Joined: 14. Nov 2021, 19:29
- Primary OS: MS Windows 10
- VBox Version: OSE Debian
- Guest OSses: Kali Linux
Re: E_FAIL (0x80004005) Failed to load VMMR0.r0
Sorry about that. Yea, the VBox version installed is 6.1.28. Gonna roll back to 6.1.26 now and see if it works. Thanks!
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: E_FAIL (0x80004005) Failed to load VMMR0.r0
The Windows Hypervisor-enforced Code Integrity (HVCI) feature rejects the VirtualBox component VMMR0.r0. A workaround is to disable HVCI aka Memory integrity as follows:
On your Windows host, go to Start > Settings > Update & security > Windows Security > Device security > Core isolation details, turn off Memory integrity and reboot the Windows host.
On your Windows host, go to Start > Settings > Update & security > Windows Security > Device security > Core isolation details, turn off Memory integrity and reboot the Windows host.
-
- Posts: 7
- Joined: 14. Nov 2021, 19:29
- Primary OS: MS Windows 10
- VBox Version: OSE Debian
- Guest OSses: Kali Linux
Re: E_FAIL (0x80004005) Failed to load VMMR0.r0
Just to update: rolling back to 6.1.26 did in fact do the trick! At least for a little while. Found again I'm unable to start the VM