Windows 10 Stopped working over the weekend

[NairbEekcM]

I'm not sure what changed... Perhaps an MS Update?

The error message is well known, but none of the fixes I found worked for me.

This is a well worn VM that I've been using for years. I did recently move it to a new hardware, but it had been working for a couple of weeks before this error message popped up.

Here is the error message:

Code: Select all

Failed to open a session for the virtual machine Windows 10.

The virtual machine 'Windows 10' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Any suggestions would be very welcome.

Thanks much.

[scottgus1]

Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

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

go to C:\Users\{youraccount}\.Virtualbox, and zip & post the VboxSVC.log, using the forum's Upload Attachment tab.

[NairbEekcM]

Thanks for the quick reply, but I can't start the guest at all. It won't start.

Also, sorry for not mentioning. I'm running linux as the host OS.

The log doesn't change when I try to launch the guest OS Win 10...

Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

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

go to C:\Users\{youraccount}\.Virtualbox, and zip & post the VboxSVC.log, using the forum's Upload Attachment tab.

[fth0]

Depending on your Linux distribution, you'll probably find the VBoxSVC.log file in /home/<username>/.config/VirtualBox (don't ignore the "." in the path ).

[NairbEekcM]

That's definitely pointing to the issue:

Code: Select all

00:13:16.691364 nspr-6   Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:13:19.861856 nspr-3   Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:13:20.221628 nspr-7   Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:13:20.618300 nspr-3   Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:13:20.736523 nspr-7   Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:13:28.058932 nspr-5   Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:13:28.237131 nspr-4   Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:13:28.242866 nspr-5   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlo1: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:13:28.247429 nspr-5   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlo1: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:13:28.375790 nspr-7   Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:14:50.636038 nspr-2   Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
00:14:59.581248 main     VirtualBox: object deletion starts
00:14:59.581288 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium '/home/brian.mckee/.VirtualBox/Machines/Windows 10/Windows 10.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:14:59.581886 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={0169423f-46b4-cde9-91af-1e9d5b6cd945} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:14:59.581943 main     VirtualBox: object deleted

I think the implication is that something is still using the vbox object...

I have already tried re-installing virtualbox and it's modules. The option to forget the previous disconnect is greyed out...

The modules are loaded:

Code: Select all

lsmod | grep vbox
vboxnetadp             28672  0
vboxnetflt             28672  0
vboxdrv               479232  2 vboxnetadp,vboxnetflt

Hmmm. /dev/vboxusb also exists, yet the tool doesn't see it...

Let's look at the devices:

Code: Select all

ls -lah /dev/vbox*
crw------- 1 root root      10, 57 Aug 17 14:53 /dev/vboxdrv
crw------- 1 root root      10, 56 Aug 17 14:53 /dev/vboxdrvu
crw------- 1 root root      10, 55 Aug 17 14:53 /dev/vboxnetctl

/dev/vboxusb:
total 0
drwxr-x---  4 root vboxusers   80 Aug 17 14:53 .
drwxr-xr-x 21 root root      4.9K Aug 17 14:53 ..
drwxr-x---  2 root vboxusers  100 Aug 17 14:53 001
drwxr-x---  2 root vboxusers   80 Aug 17 14:53 003

The group is wrong? Shouldn't it be vboxusers? Must resist strong urge to change owners on the modules.

I'm running kernel 5.7.12 because last I checked vbox doesn't support 5.8.

How do I clear this up?

[NairbEekcM]

Apparently I corrupted the executables so that I had to remove them and reinstall them.

It's working again.

[scottgus1]

Great! Glad you found the problem and are up and running.