Hello,
VirtualBox stopped working on my Windows 10 host, the VirtualBox application does not start, it used to work perfectly and one day it stopped.
I cannot open the application but I can see processes in the task manager. I used it to run a Arch Linux VM but I don't think there is an issue because I cannot even start the VirtualBox application to select a VM now.
When I restart or shutdown the Windows host I have an error saying VirtualBox Interfaces has active connections.
I'm on the 6.1.32 build but I tried with the 6.1.30 and 6.1.28 without success.
I downgraded my graphics drivers (nvidia) without success, I reinstalled Windows 10 without succes, I tried with and without Hyper-V enabled without success.
It used to work but something happen and I don't know what. Maybe a driver update or Windows update.
I don't know how to get more information or log on the situation it's not related to a certain VM as
What can I do?
VirtualBox stoped working on Windows 10
Re: VirtualBox stoped working on Windows 10
I found out that it was because of a new USB device, I unplugged the device and Virtual Box started working again.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: VirtualBox stoped working on Windows 10
Glad you found the problem!
Re: VirtualBox stoped working on Windows 10
Hi,scottgus1 wrote:Glad you found the problem!
I would expect to see an answer/suggestion regarding why the USB device caused Virtual Box not to function. As a first post, I expect tat I am missing something. Yes/No?
Ralf
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: VirtualBox stoped working on Windows 10
This has happened a few times, and it would be nice to figure out why. Personally I'm not certain how to start investigating it, though.
If someone who has this happen to them could pin it down to a certain device that always stops Virtualbox from opening when the device is plugged in first, but Virtualbox can start without the device plugged in, a comparison of the VboxSVC.logs found in "C:\Users\{accountname}\.Virtualbox" for both situations might offer a clue.
If someone who has this happen to them could pin it down to a certain device that always stops Virtualbox from opening when the device is plugged in first, but Virtualbox can start without the device plugged in, a comparison of the VboxSVC.logs found in "C:\Users\{accountname}\.Virtualbox" for both situations might offer a clue.