VBoxSVC.exe prevents logoff

[mskov]

If you kill a running virtualbox.exe process, then VBoxSVC.exe would stay running (as it always did) and would prevent logoff/shutdown saying that it "Has active connections". That was never the case at least up to VirtualBox 5.1.0. The way to reproduce: 1) start any VM 2) kill the running virtualbox.exe process 3) try to logoff.

I can always reproduce the problem (at least) on a Win7 x64 host.

[cvandesande]

Same issue here, same host operating system. Windows 7x64. Noticed the issue the first time I tried to shutdown the host after updating 5.1.4.

Workaround is to kill VBoxSVC.exe but that feels cruel.

[Eric Johnson]

I also have the same issue; version 5.1.6 r110634, running on windows 10 x64.

Usually after running a VM I get the error "has active connections", and I have to kill VBoxSVC.exe, and sometimes I don't.

[cpriest]

I also am having this issue with the latest Version 5.1.10 r112026 (Qt5.6.2) on Win 10 Pro 14965.1611004-1700

[Dmitry Rukavishnikov]

Same here. Windows 10 x64, Virtual Box 5.1.4. Got this message when shutting down host OS.

[JorisMeys]

Problem still exists with Windows 7 x64 and Virtual Box 5.1.12 r112440

Message is persistent.

I am using the Oracle VM VirtualBox in combination with the Docker Toolbox ( ​https://www.docker.com/products/docker-toolbox ) in case this might be of any significance.

I also noticed a VBoxNetDHCP.exe process that stays active even after shutting down the machine in the VirtualBox and closing the program.

[mkurskiy]

Promblem still exists with Windows 7 x64 (Version 6.1.7601 Service Pack 1 Build 7601) and Virtual Box Version 5.1.14 r112924 (Qt5.6.2).

[Faxpl Enus]

I see the problem in Windows 10. VirtualBox prevents reboot saying "Has active connections". Version 5.1.18. I didn't kill any running processes. But before the problem started I had a virtual machine crashed with something like "instruction 0 accessed memory at address 0". I am not sure of course that this is related.

[Klaus Espenlaub]

This unfortunately is related, and even more unfortunately is outside our control (well, we might be able to fix some remaining crashes, but not with half a line of text as the only hint, we'd need a memory dump). If a Windows COM client process crashes then it takes the server process about 6 minutes to detect this (actually somewhere between 6 and almost 8 minutes, since COM polls client liveness every 2 minutes, and needs 3 failed polls to declare it dead - all totally hardcoded by Microsoft). If you want to shut down your system in that time then VBoxSVC will veto since it can't know if the client is gone or not.

[cesarjorgemartinez]

Same problem with Vbox 5.1.22 in Windows 7 I do not know how to do a dump (I try this in task manager but say access denied), but it failed after installing three windows updates and try to restart. I have made a kill process in task manager of VBoxSVC

[Ruslan Tagirov]

Same problem on Windows 10 x64 (version 1709, all current updates installed) with VirtualBox 5.2.6

[Klaus Peiffer]

Same here: Vbox 5.1.32 on W7-64 Pro host. I continuously have a W7-64 guest running (started via VboxHeadlessTray 5.1) which on a shutdown of the host is saved and terminated as expected. But next the host-shutdown hangs with the "Has active connections" message and I have to cancel the shutdown, manually kill the VboxSVC process and the continue the shutdown/restart.

[cferrante]

Same problem on Windows 10 x64 with VirtualBox 5.2.6

Found this article: ​https://stackoverflow.com/questions/42594325/vagrant-shutting-down-host-machine

Realized I should have been using vagrant suspend instead of vagrant halt.

Resolved the issue for me.

[Socratis]

FYI, Vagrant is a program that relies on VirtualBox but modifies its configuration files in unknown ways. They have their own ​Vagrant support channels.

[Martin Boissonneault]

I had the same problem, on shutdown/reboot Windows would say "VBoxSVC Has active connections". All VMs where shut down.

Strangely, running <VBoxManage list vms> in the host closed VBoxSVC and allowed Windows to restart.

The problem did not show up again after.

Could it be related to improper shutdowns?

Host: Windows 7 x64
Guest: Ubuntu 16.04 LTS x64

VirtualBox-5.2.8-121009-Win
Oracle_VM_VirtualBox_Extension_Pack-5.2.8-121009