virtualbox.org

Hi All,
I have installed Virtual Box 6.1.6 on Windows 10 Enterprise and have Fedora 27 - 64 bit Guest installed. It was working fine until sometime back.
I have installed Windows/BIOS updates recently on my Lenovo T480. So not sure if this is the reason, every time I try to start my VM, I get the below error.

The virtual machine 'Fedora 27 New' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Could the Windows update cause issues?
Please help

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log and the hardening log next to it, zip them, and post the zip file, using the forum's Upload Attachment tab.

@scottgus1
Please see Vbox.log file attached. I am unable to see any hardening log file.
The only files present are Vbox.log, Vbox.log.1, Vbox.log.2 and Vbox.log.3

A hardening error with no hardening log seems strange. Even stranger is that the posted log shows a VM that booted seemingly fine then runs for some 92 and a half hours.

No indication of a hardening error appears.

The timestamp on the log shows: Apr 9 2020. So could this be an old set of logs and the latest?
Also i had deleted some temp folders on my PC to free up space, could I have deleted soemthing that was needed?
My old VM's are not working and also I am unable to create a new Virtual Machine as well. Creating a new Virtual machine also fails with the same errorcode.

deep wrote:The timestamp on the log shows: Apr 9 2020. So could this be an old set of logs and the latest?

You should look at the 2nd line of the log file to see that this VM run began 2020-12-11, and at the file name to see that it ended 2020-12-15. So it's an old log file indeed.

In this case, we should rather look at C:\Users\dsukumar\.VirtualBox\VBoxSVC.log IMHO.

Please find attached all log files from C:\Users\dsukumar\.VirtualBox\.
I can see the following errors:
25:40:10.308480 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&d1fe901&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 4
25:40:10.308573 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&d1fe901&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 7
25:40:10.308632 USBPROXY Getting USB descriptor (id 0) failed (dwErr=31) on hub USB#ROOT_HUB30#4&d1fe901&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8} port 8

and also
27:05:48.079006 main VirtualBox: object deletion starts
27:05:48.080465 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium 'C:\Users\dsukumar\OneDrive - CommScope\Deepika\VirtualBox\VirtualBox VMs\Fedora 19\Fedora 19.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0

VBoxSVC.log.1 wrote:

00:00:00.001476 main     VirtualBox COM Server 6.1.16 r140961 win.amd64 (Oct 16 2020 16:33:17) release log
00:00:00.001481 main     Log opened 2021-01-19T22:50:59.425413400Z

00:00:00.182566          Installed Drivers:
00:00:00.187609            C:\WINDOWS\system32\DRIVERS\VBoxDrv.sys (Version: 6.1.6.37129)
00:00:00.188419            C:\WINDOWS\system32\DRIVERS\VBoxUSBMon.sys (Version: 6.1.16.40961)
00:00:00.189373            C:\WINDOWS\system32\DRIVERS\VBoxNetAdp6.sys (Version: 6.1.16.40961)
00:00:00.189956            C:\WINDOWS\system32\DRIVERS\VBoxNetLwf.sys (Version: 6.1.16.40961)

00:00:00.512174          Support driver version mismatch: DriverVersion=0x2d0001 ClientVersion=0x300000 rc=VERR_VERSION_MISMATCH

You're using a mixture of 2 different VirtualBox versions here. Uninstall VirtualBox (the VMs will stay behind), reboot the host, and install VirtualBox 6.1.16 (or 6.1.18). Now that you know which log messages to look at, you can verify yourself if the un-/re-installation is successful. Let us know if the problem is solved or if you have further problems.