Error while starting VM in headless way (VBoxHeadless.exe) intermittenly on Windows 2016 server

[Jaikumar]

Hi All,

I'm starting VM in a headless way (using VBoxHeadless.exe) on Windows 2016 server and getting the following error:

----------------------------------------------------------------------------------------------------------------------------------------------------------------
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=-5660 fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VBoxRT.dll: Signature #2/2: Expected at least 2 valid paths, not 1.: \Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VBoxRT.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\Oracle\VirtualBox\VBoxRT.dll' (C:\Program Files\Oracle\VirtualBox\VBoxRT.dll): rcNt=0xc0000190
VBoxHeadless: Error -610 in supR3HardenedMainInitRuntime!
VBoxHeadless: LoadLibrary "C:\Program Files\Oracle\VirtualBox/VBoxRT.dll" failed (rc=1790)
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Virtualbox 7.0.8 64bit, Platform : Windows 2016 server.

This error occurs intermittently, not always, because of this behavior every time we test on freshly installed windows 2016 server after installing security updates provided by Microsoft.

Does somebody experienced it or have idea as to what is causing this error?

Regards,
Jaikumar

[scottgus1]

You're definitely having a hardening problem. The VM's VboxHardening.log may say what's up. Be sure to close all VM windows and error boxes before copying the hardening log. Then either analyze it using Diagnosing VirtualBox Hardening Issues (note the exit code at the end of the log) or zip and post the log using the forum's Attachments tab.

For it to fail on a Virtualbox dll is likely indicating an overly-aggressive 3rd-party antivirus app.

This error occurs intermittently, not always, because of this behavior every time we test on freshly installed windows 2016 server after installing security updates provided by Microsoft.

This line is a bit hard to parse. Taken as written, it means you reinstall the host OS and run all updates afresh every time the VM has this issue.

If that's really what you're doing, that's a lot of work.

I am guessing that's not what you're doing, and you really meant this:

This error occurs intermittently, not always, and it happens every time we test on freshly installed windows 2016 server after installing security updates provided by Microsoft.

Please see if you can clarify this part.

[Jaikumar]

Thank you scottgus1 for taking time to look into the post and lending the helping hand
Let me re-phrase my text again:

To make sure that we have a correctly working installation of the product, we make sure that we install the product on a fresh Windows 2016 server with updated security patches provided by Microsoft from time to time

I've checked the link provided by you for diagnosing Virtualbox Hardening issues but nothing concrete found like third party unsigned library or something, also this server does not have any Virusscan tool installed, Windows defender and firewall are on by default - did not make any changes into the same.

Please find attached "VBoxHardening.log"

Thank you.

Regards,
Jaikumar

[scottgus1]

Thanks for the hardening log. I don't see what is wrong in it either. This kind of trouble usually comes from something behaving like malware on the host OS and digging itself into Virtualbox processes.

With a complete fresh host OS install, though, and nothing else installed, I can't figure what could be causing the hack.

Maybe a forum guru could say what's up.

You aren't by any chance running this in a nested VM?

You might also try coming up to 7.0.12, as some bugs have been found.

[fth0]

Is it possible that the Windows certificate stores contained different (root) certificates when the error occurred and when it didn't?

[Jaikumar]

Thanks a lot for suggestion to try version 7.0.12 scottgus1 and issues is resolved. Several rounds of installation and uninstallation on fresh and used Windows 2016 server - it did not even break a single time Worked like a charm.

You might also try coming up to 7.0.12, as some bugs have been found.

Thank you!

Regards,
Jaikumar

[scottgus1]

Great! Glad you're up and running.