Mhh... But what can I do to prevent that? I ran and shut down a virtual box. And now I have that problem with the 10010 errors again. Altough no box runs.
You would need to disable the Virtual Switch that VirtualBox installs, I moved all my Virtual Environments to Azure for this reason...Mhh... But what can I do to prevent that? I ran and shut down a virtual box. And now I have that problem with the 10010 errors again. Altough no box runs.
I think you have to disable Hyper-V.
Hyper-V will disable Connected Standby and Hibernation will be your only option outside of Shutdown. Windows 10 implementation of Hyper-V supports Connected Standby though...I already disabled Hyper-V. That was necessary for using VirtualBox. But maybe it's an idea to use this instead of VirtualBox.
Azura is not an option for me. I have to work in the train and there is a bad internet connection.
Hyper-V will disable Connected Standby and Hibernation will be your only option outside of Shutdown. Windows 10 implementation of Hyper-V supports Connected Standby though...
I use my 4G Tethering for access to my Azure Cloud outside the Office.
Not the coziest solution but better than nothing.You have your anwser, now just create a PowerShell Script that disables the adapter....
mode="DISABLED"
if [ -n "$1" ]; then
mode="ENABLED"
fi
netsh interface set interface "VirtualBox Host-Only Network" "$mode"
My guess would be a task with a Trigger....entering into S0iX Power StateNot the coziest solution but better than nothing.
I have written a small and really dump script but it does its job:
Code:mode="DISABLED" if [ -n "$1" ]; then mode="ENABLED" fi netsh interface set interface "VirtualBox Host-Only Network" "$mode"
Is there a way to run the script when Windows entering the sleepmode?
@echo off
netsh interface set interface "VirtualBox Host-Only Network" DISABLED
echo "VirtualBox Host-Only Network is now DISABLED