virtualbox.org

Hi,
I have just installed VirtualBoxVersion 6.1.22 on Windows 10. (OS Build - 119042.964)
Now Whenever I open Ubuntu Virtual Machine in full screen mode, my window freezes(black screen) at time of showing logs and when I try to open it on normal(not fullscreen) mode, it opens and runs as usual. I can also switch to fullscreen after that.

Also, I am getting the below error whenever i power off the machine: Kindly help me resolve these issues.

FAQ: Diagnosing VirtualBox Hardening Issues.

Another likely candidate (you may have both problems): HMR3Init: Attempting fall back to NEM (Hyper-V is active).

I updated my Nvidia drivers, disabled my (McAfee) antivirus and I'm getting a V (that means hyper-v is disabled) according to the post. But I am still facing the same issue..
Here is the error log..

You do have a hardening problem, and this memory error at power-off has been happening lately, anecdotally on McAffee-protected infected hosts. Try setting exceptions so McAffee does not scan any Virtualbox folder or file. If that doesn't work, try uninstalling McAffee completely.

Memory reference issue was resolved after uninstalling the antivirus....thank you! (but I can't just keep my PC without AV, so...any other option?)

Also if power on is done using fullscreen, blackout issue still remains....I'll just not start machine in fullscreen...
and idk what this is but thought i should attach this blocks log (this comes at time of booting)......

its_pcc wrote: I can't just keep my PC without AV, so...any other option?

Windows 10 comes with built-in AV & firewall that looks solid and doesn't fight Virtualbox.

I'm not certain about the fullscreen glitch, a vbox.log might help.

The posted error messages can be ignored. They come from a bug in the Ubuntu driver for the VMSVGA video card, but the VM will still boot fine.

I wasn't aware of biult-in AV.....and suppose I keep McAfee and the error persists....It won' t hinder the performance, right?

Heres VBox zip:

The crash happened in the log happened after the VM was shut down and the Virtualbox environment had been cleaned up. So theoretically the error shouldn't cause trouble, at least it didn't this time. Personally I'm leary of "theoretically's" when important data is running. I'd try to prevent the crash myself.

If you're set on McAffee, you might report this to them.

How did the setting of exceptions for all things Virtualbox in McAffee go?

FWIW:

D:\Oracle\VirtualBox\VirtualBoxVM.exe

Seems Virtualbox is not installed in the default "C:\Program Files". While this might not cause the trouble you're having, "C:\Program Files" has special permissions that should be in place around Virtualbox, which could allow greater surface area for malware to attack if Virtualbox is in an unprotected folder. Your host OS appears to be booting from a C:\ drive.

OK thanks!...'ll report this to them and try to resolve this....
I tried excluding but result is the same...
And the reason for installing in D is low storage in my C drive....

its_pcc wrote:And the reason for installing in D is low storage in my C drive....

If you can't afford a few MB for software install then you should definitely be shopping for a new C drive.

And to be sure you understand: where you choose to install the software has no effect whatever on where data files are stored (i.e. VMs, i.e. the files that actually take up significant space).

Data destination hasn't been associated with software install directory since DOS days, just as Windows hasn't needed third party AV since Win8 days (when researching this, don't go to websites that have a vested interest in selling you stuff).

well, I have kept the virtualbox files excluded from mcaffee real time scanning, and I am not getting the error anymore, not sure why but i think excluding them helps.

Thanks for letting us know an exclusion works! I was wondering if it would.

If McAffee is forced to not dig into Virtualbox, then it won't interfere and cause the crash that is happening.