VirtualBox

Opened 5 years ago

Closed 5 years ago

#18939 closed defect (obsolete)

FAILED TO OPEN SESSION FOR ALL VIRTUAL MACHINES. Exit code 1 (0x1). Result Code: E_FAIL (0x80004005)

Reported by: Ricky_001 Owned by:
Component: other Version: VirtualBox 6.0.12
Keywords: failed to open session Cc:
Guest type: Linux Host type: Windows

Description

Host : Windows 10 Pro

Guest : Ubuntu x64 & Debian x64 [tried]

VirtualBox Version : v6.0.10 & v6.0.12 [tried]

After downloading and installing Oracle VM VirtualBox and setting up virtual environments, the error shows up while trying to start any virtual machine, stating "Failed to open a session for the Virtual machine <Machine_Name>"

Exit Code 1 (0x1)

Result Code E_FAIL (0x80004005)

Fixes tried :-

1) Reinstalling the virtual machine(s)

2) Reinstalling VirtualBox [including upgrading to version 6.0.12]

3) Headless or detachable starts

[Detachable starts do start up the machine sometimes, but gives error more often than not]

4) Reinstalling VirtualBox Drivers from E:\VirtualBox\drivers\vboxdrv\VBoxDrv.inf

Log File is attached

Attachments (3)

VBoxHardening.2.log (178.3 KB ) - added by Ricky_001 5 years ago.
The "Ubuntu" Log File
VBoxHardening.log (178.3 KB ) - added by Ricky_001 5 years ago.
The "Ubuntu" Log File
VBoxHardening_Kali.log (178.3 KB ) - added by Ricky_001 5 years ago.
Log file for the Virtual Machines "Kali_Linux" for which the error occurred.

Download all attachments as: .zip

Change History (5)

by Ricky_001, 5 years ago

Attachment: VBoxHardening.2.log added

The "Ubuntu" Log File

by Ricky_001, 5 years ago

Attachment: VBoxHardening.log added

The "Ubuntu" Log File

by Ricky_001, 5 years ago

Attachment: VBoxHardening_Kali.log added

Log file for the Virtual Machines "Kali_Linux" for which the error occurred.

comment:1 by Socratis, 5 years ago

It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Plus a discussion and analysis on the bug tracker is going to help me, you, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

Having said that, you have a hardening problem. From your VBoxHardening.log:

160c.f95c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1990 ms, the end);

Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Those are guidelines, you have to use your judgement as to which program might be responsible...

I'd start by completely removing, not simply disabling:

160c.f95c: Found driver klkbdflt (0x40)
160c.f95c: Found driver klmouflt (0x40)
160c.f95c: Found driver KLIM6 (0x40)
160c.f95c: Found driver kneps (0x40)
160c.f95c: Found driver klflt (0x40)

also known as:

160c.f95c:     ProductName:     Kaspersky™ Anti-Virus ®

comment:2 by aeichner, 5 years ago

Resolution: obsolete
Status: newclosed

No follow up by the reporter for over 6 months, closing.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette