Opened 10 years ago
Closed 9 years ago
#13654 closed defect (obsolete)
Failed to open a session for the virtual machine
Reported by: | ryee | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.20 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
How to Reproduce
Can't start the sessions, the session would be ended and changed to 'Aborted' status.
The error screen was prompted: Failed to open a session for the virtual machine XXXXXXX.
The VM session was aborted.
Result Code: E_FAIL (0x80004005) Component: SessionMachine Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}
Attachments (1)
Change History (4)
by , 10 years ago
Attachment: | VBoxStartup.log added |
---|
comment:1 by , 10 years ago
comment:2 by , 10 years ago
The first problem in the log is an error -23021 (VERR_CR_X509_CPV_NO_TRUSTED_PATHS) on a DLL (c:\progra~1\agnitum\outpos~1\wl_hoo~1.dll) related to Agnitum Outpost Security, and thereby refusing to load it. That error means we weren't able to verify the signature embedded in the DLL. Either because it uses some root certificate that isn't trusted by your system or because it's incorrectly signed. I'm unsure whether this DLL is used by the crypto subsystem and is responsible or related to the other errors we're seeing further down in the log.
The second problem is failure to find a valid signature for user32.dll. This could be related to the above DLL or it could be a totally different issue - like user32.dll might be actually modified. Best way to find out is running sigcheck -i c:\windows\system32\user32.dll
. sigcheck is a tool from microsoft/sysinternals.
Would potentially be really helpful to get the output of sigcheck -i c:\progra~1\agnitum\outpos~1\wl_hoo~1.dll
as well.
comment:3 by , 9 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant (please do also check the most recent 5.0.x test build). In that case please provide the requested information.
This seems related to Agnitum Outpost Security... why does any software aiming at tightening security inject its DLLs into every application? Truly secure software would monitor from the outside, as the DLL could be used as an attack vector.