如何修复 Windows 中的“VirtualBox 接口具有活动连接”错误？
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/56562630/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
How to fix "VirtualBox Interface has active connections" error in Windows?
提问by Ricardo Mendes
Windows 10 is displaying a VirtualBox Interface has active connectionserror message when shutting down after using Docker Quickstart Terminal on Virtual Box.
在 Virtual Box 上使用 Docker 快速入门终端后关闭时，Windows 10 显示VirtualBox Interface has active connections错误消息。
I tried to fix this by typing exitto close the terminal.
我试图通过键入exit关闭终端来解决此问题。
How can I smoothly close the terminal and get rid of the error message?
如何顺利关闭终端并摆脱错误消息？
回答by Kjeld
I came here because the title of this topic does not mention Docker. I had the same problem when using the application BlueStacks in Windows 10, without Docker. Windows did not shut down (or took a long time to do so) because 'VirtualBox still has active connections'. I'd like to share my solution here, using BlueStacks as just an example. I solved this by creating a task in task manager that runs a script on shutdown. The script kills the VirtualBox process, which is perfectly safe. Creating such a task is described here: https://superuser.com/questions/165142/using-task-scheduler-to-run-a-task-before-shutdownThe script for killing a process: wmic process where "name='BstkSVC.exe'" delete
我来这里是因为这个话题的标题没有提到Docker。在没有 Docker 的情况下，在 Windows 10 中使用应用程序 BlueStacks 时遇到了同样的问题。Windows 没有关闭（或花了很长时间才关闭），因为“VirtualBox 仍然有活动连接”。我想在这里分享我的解决方案，仅以 BlueStacks 为例。我通过在任务管理器中创建一个在关机时运行脚本的任务来解决这个问题。该脚本杀死了 VirtualBox 进程，这是非常安全的。这里描述了创建这样的任务：https: //superuser.com/questions/165142/using-task-scheduler-to-run-a-task-before-shutdown杀死进程的脚本：wmic process where "name='BstkSVC.exe'" delete
Maybe this helps anyone who came here and is not using a container. Thanks.
也许这对来到这里并且不使用容器的任何人都有帮助。谢谢。
回答by Ricardo Mendes
Using the bellow commands should fix it:
使用波纹管命令应该修复它：
docker-machine stop
exit
