Page 1 of 1
Host WIN10 - nach Update Vitualbox auf Version 6.1.28 r147628 (Qt5.6.2)
Posted: 28. Oct 2021, 13:21
by enabler
Für die virtuelle Maschine Linux Mint Uma Xfce 20.2 konnte keine neue Sitzung eröffnet werden.
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).
Fehlercode: E_FAIL (0x80004005)
Komponente: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Hat jemand das gleiche Problem gelöst ?
(already done - VB neu installiert, Extension Pack deinstalliert/neu installiert)
Re: Host WIN10 - nach Update Vitualbox auf Version 6.1.28 r147628 (Qt5.6.2)
Posted: 29. Oct 2021, 00:14
by AndyCot
Go back to to 6.1.26 as 6.1.28 has a bug that you are seeing.
Re: Host WIN10 - nach Update Vitualbox auf Version 6.1.28 r147628 (Qt5.6.2)
Posted: 29. Oct 2021, 07:53
by enabler
thx a lot for the hint - does it make sense to wait to the next update Virtualbox (it seems that a lot of user have this problem ..) ?
Re: Host WIN10 - nach Update Vitualbox auf Version 6.1.28 r147628 (Qt5.6.2)
Posted: 4. Nov 2021, 12:25
by MickeyCohen
I have the same bug, going back to 6.1.26.
Code: Select all
Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Re: Host WIN10 - nach Update Vitualbox auf Version 6.1.28 r147628 (Qt5.6.2)
Posted: 4. Nov 2021, 15:48
by mpack
MickeyCohen wrote:I have the same bug, going back to 6.1.26.
The "bug" was introduced in 6.1.28, so if you got this in 6.1.26 then the error message is accurate, the reporting of it is not a bug.
Re: Host WIN10 - nach Update Vitualbox auf Version 6.1.28 r147628 (Qt5.6.2)
Posted: 6. Nov 2021, 02:52
by AndyCot
Try the latest nightly test build as it may work, btu then again...
It did fix the "VERR_NEM_INIT_FAILED" error in 6.1.28, see
viewtopic.php?f=6&t=104360 for info.
Re: Host WIN10 - nach Update Vitualbox auf Version 6.1.28 r147628 (Qt5.6.2)
Posted: 2. Dec 2021, 02:04
by fth0
enabler wrote:Hat jemand das gleiche Problem gelöst ?
Ja.
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.