Issues with VB on version 6.1.30

[NahumE]

Hi,

I downloaded the new version a couple of days ago, and i'm having the same issues as in the version 6.1.28

My error is:

Failed to open a session for the virtual machine Ubuntu5.

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}

and it's the same error in version 6.1.28


I thought that if I'll install the new version, maybe i won't see this error, but seems i was wrong.

My OS host is windows 10 version:21H1 (build19043.1348)

The error logs are:


00:00:04.800022 Failed to load VMMR0.r0 (VERR_LDR_GENERAL_FAILURE)}, preserve=false aResultDetail=-618
00:00:04.800552 Console: Machine state changed to 'PoweredOff'
00:00:04.839493 Power up failed (vrc=VERR_LDR_GENERAL_FAILURE, rc=E_FAIL (0X80004005))
00:00:05.341519 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:05.341699 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up (Display::setVideoModeHint)}, preserve=false aResultDetail=0
00:00:05.343958 GUI: Aborting startup due to power up progress issue detected...

is there's a solution for this error, or is it a known bug?

[scottgus1]

6.1.28 had a bug when running on Windows 10 while Hyper-V is enabled. 6.1.30 may still have the bug.

Use 6.1.26 and matching Extension Pack here: https://www.virtualbox.org/wiki/Download_Old_Builds_6_1

[NahumE]

Hi Scott,

I've installed the version you've mentioned (After removing the VB from my computer and restarting it), but unfortunatlly seems like the same error i had in versions: 6.1.28, 6,1,30 is reccuring in this version (6.1.26).

any ideas on how can i solve it, or maybe i need to downgrade the installation of this the to an older one?

The error i'm having is this:

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).

The log files are:

00:00:05.444658 VMSetError: Failed to load VMMR0.r0
00:00:05.445315 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed (VERR_LDR_GENERAL_FAILURE).
00:00:05.445436 Failed to load VMMR0.r0 (VERR_LDR_GENERAL_FAILURE)}, preserve=false aResultDetail=-618
00:00:05.445932 Console: Machine state changed to 'PoweredOff'
00:00:05.467319 Power up failed (vrc=VERR_LDR_GENERAL_FAILURE, rc=E_FAIL (0X80004005))
00:00:05.967459 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1920x978
00:00:05.967521 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up (Display::setVideoModeHint)}, preserve=false aResultDetail=0
00:00:05.968097 GUI: Aborting startup due to power up progress issue detected...

[scottgus1]

That's weird. This error wasn't happening until 6.1.28 came out.

This kind of error is happening due to Hyper-V being enabled on your host PC. If you don't use Hyper-V, you can disable it and get Virtualbox to work. Use the procedure here: VERR_NEM_VM_CREATE_FAILED: What do I do?

[mpack]

That's weird. This error wasn't happening until 6.1.28 came out.

It was. Here's an example from 2017: viewtopic.php?f=6&t=82689.

I think there's a tendency since 6.1.28 to blame everything on the infamous "bug". IMO it was always more likely to be a host PC problem, a conflict with Hyper-v or AV. Either that or permissions have prevented VirtualBox from being installed properly. Or all of the above.

[scottgus1]

Yup, sure enough! Should've googled it...

[fth0]

On your Windows host, please go to Start > Settings > Update & security > Windows Security > Open Windows Security, select Device security, then Core isolation details. Under Core Isolation, check if Memory integrity is turned on or off. If it's on, turn it off, reboot the Windows host, and check if your issue persists.

[NahumE]

Hi.

Thanks a lot for the assistance, the problem was, as mentioned in the core isolation. (in Windows security).
After disabling it, i restarted my PC host and the VM's are up and running.

Do you think that now i can upgrade to 6.1.28, or 6.1.30, or avoiding from taking this chance, and stay with what i have?

[mpack]

Upgrade to 6.1.30.

[fth0]

Do you think that now i can upgrade to 6.1.28, or 6.1.30

Yes, that's the whole idea: You reported an issue with VirtualBox 6.1.28 and 6.1.30, and we want to find out if it is caused by an incompatibility between the Windows Memory integrity feature and those VirtualBox versions.

[NahumE]

Hi there.

Just wanted to update (removed the 6.1.26 version) that i installed the 6.1.30 version. and so far so good!

Have a great day.