virtualbox.org

Hello.
Initially with version 6.1.8 and then with version 6.1.10, with any of the existing virtual machines (Win10, Win7, WinXP and OS2) the error appears:
"Failed to open a session for the WinXP virtual machine.
The virtual machine 'WinXP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D: \ xVM \ Machines \ WinXP \ Logs \ VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} ".
The last "VBoxHardening.log" file is attached.
None of the indications in "FAQ: Diagnosing VirtualBox Hardening Issues" changed the situation.
Host: Windows 8.1 (6.3.9600) with 2 years of use of Virtualbox without abnormalities. All MS updates applied.
In advance I appreciate any help.

The Hardening FAQ has absolutely everything we know about how to fix hardening errors.

The log shows trouble hashing stuff and errors in opengl32.dll, a fundamental Windows file.

Exit code 1 relates to bad Windows files, for which an admin-command-prompt 'sfc /scannow' is in order, or look carefully for web- or banking-security software, which sometimes do not report themselves knowingly in the log. IBM Trusteer Rapport, safe banking stuff, etc?

You'll have to peruse your PC carefully to find the offending trouble software. Unfortunately there is no list of installed software in the log, so we couldn't guess..

I have that problem too. I didn't install any programs, just my nvidea driver was updated from what I can remember. i tried to delete kaspersky, re installed virtualbox, installed all windows updates and i have no success. This problem i have 2 days.
My OS Windows 10

If I change network settings from NAT bridge to NAT and run virtual machine in console mode - it works.

SVK wrote:NAT bridge

Virtualbox doesn't have a "NAT bridge" network setting. There are NAT, NAT network, and Bridged, each separate from the other. It is unlikely that the network type will fix the hardening problem.

SVK wrote:console mode - it works.

again, Virtualbox does not have any way of starting its guests called "console mode" - what is this?

SVK wrote:my nvidea driver was updated

Nvidia just put out a new driver that has a not-signed file, which Virtualbox can't use because of its not being signed. If "console mode" relates to starting the guest in a fashion that does not use 3D acceleration, such as actually turning off 3D acceleration or starting the guest headless or detachable, then the Nvidia drivers are probably the cause of the hardening problem.

Downgrade the video drivers and/or get on with Nvidia to ask them to sign all the files.

Sorry for my incorrect translate titles in gui. I meant "Bridged Adapter" and "Headless Start". My problem was in crashed files in dir \system32\catroot2\. I fixed it and virtualbox is working now

Great! Glad you're up and running.

I did some tests and using "Vboxmanage startvm" vmname "--type separate" or using the manager with the "detachable start" option the virtual machines run normally.
As 3D acceleration is disabled in this mode, the situation is very consistent with the analysis by scottgus1 on the existence of an error in "opengl32.dll". As is common, it must have been due to an update from Microsoft itself .
C´est la vie.
An "sfc / scannow" scan was harmless.
Thanks to all.

egnbr, it could still be possible that a video driver issue could back-feed into a Microsoft dll, making it the video driver's fault instead of Microsoft. Some hardening issues that theoretically can be handled on the fly and still hopefully allow the guest to boot are reported in the vbox.log for a guest.

If you'd like us to look, please right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.