Enabling Hyper-V feature turns my wi-fi off #139

londoncalling · 2016-10-10T21:07:50Z

@rneugeba @friism I'm adding this issue per feedback we got through the docs, docs issue #100 "Feedback for: docker-for-windows/index.md" from https://github.com/shazChaudhry

Expected behavior

Install Docker for Windows (which enables Hyper-V), or enable Hyper-V manually, and all works, with Wi-Fi enabled.

Actual behavior

I am using Docker v1.12.1 on a Windows 10 laptop. Enabling Hyper-V feature turns my wi-fi off. How do I ensure that my wi-fi stays on while using Hyper-V features?

We need this information from the user:

Information

Diagnostic ID from "Diagnose & Feedback" in the menu.
a reproducible case if this is a bug, Dockerfiles FTW
page URL if this is a docs issue or the name of a man page
host distribution and version (Windows version, build number, etc)

Steps to reproduce the behavior

...
...

rn · 2016-10-10T22:33:10Z

@shazChaudhry the issue you reported on docker/docs#100 has been moved here.

We enable Hyper-V on installation if it is not enabled. This should not interfere with your networking setup and the rest of the installation does not touch the network interface either.

Could you describe in a bit more details what's happening and how to reproduce it, what the version of Windows is, you are using etc. Could you please upload diagnostics and provide the ID?

Thanks

simonferquel · 2016-10-11T07:46:23Z

There are known issues with some old wireless device drivers and Hyper-V. Can you try to update your wifi drivers ?

tommiehansen · 2016-10-20T12:54:39Z

Try running a repair on your default connection, if that fails try it on dockerNAT.

If all fail uninstall Docker and run a repair on your default connection. Then re-install Docker.

shazChaudhry · 2016-10-20T15:02:01Z

I have done windows updates, uninstalled and installed Docker several time. However, my wi-fi is still turned off every time hyper-v feature is enabled. wi-fi drivers are also up to date.

I have just done:

Got docker for windows (beta) from https://docs.docker.com/docker-for-windows/
Installed Docker (1.12.2, build bb80604, experimental), enabled Hyper-V feature, double checked that Virtualization was enabled and waited for Docker to start. As expected, wi-fi was automatically turned off.
To turn wi-fi back on and to connect to internet, I have disabled "vEthernet (DockerNAT)"
Uploaded diagnostic and feedback: 4F7DC077-55A5-43DC-974E-2A86B75AB998/2016-10-20_15-06-18
Host info: Windows 10 Enterprise; Version = 1511; OS Build = 10586.633, Dell Latitude E5250

Please let me know if there is any other info you need.

londoncalling · 2016-10-28T00:21:14Z

@yongshin thanks, I'll figure out a place to include this in the troubleshooting docs and link to it from other relevant topics

rn · 2016-10-28T11:56:01Z

@shazChaudhry it looks like you had VirtualBox installed and it didn't install cleanly. There are still some VirtualBox network adapters lingering on the system. I'm closing this issue, for now. Please re-open if, after un-installing VirtualBox the issue persists.
Thanks

ladvishal1985 · 2017-02-20T14:07:46Z

I am facing the same issue. I downloaded Docker(stable windows) from https://docs.docker.com/docker-for-windows/install/. Post installation Hypervisor is enabled which leads to Windows restart. Then the wifi never starts. I tried uninstalling the Docker and disabled the Hyper-V which leads to Windows restart and again the wifi works normally. I tried this twice.
I have Windows 10 Enterprise. Again post installation I am unable to start docker I get an error message that asks me to enable Virtual Technolgy from BIOS(I am not sure if this is expected behavior)

Thanks

londoncalling · 2017-02-21T04:58:34Z

@ladvishal1985 Disabling Hyper-V would cause problems, as it must be enabled.

Can you read through these topics and make sure you are following the protocols?

[What to know before you install](https://docs.docker.com/docker-for-windows/troubleshoot/#virtualization-must-be-enabled

Hyper-V (in Troubleshooting) (includes a link to how to enable Hyper-V manually if this is necessary

Virtualization must be enabled (in Troubleshooting)

Also, make sure you do not have Virtual Box installed or enabled.

@rneugeba @friism can you help? This issue seems to be re-surfacing.

friism · 2017-02-21T16:02:18Z

The networking clean-up scripts from Microsoft are another good resource: https://github.com/Microsoft/Virtualization-Documentation/tree/master/windows-server-container-tools/CleanupContainerHostNetworking

kenchilada · 2017-02-22T02:19:59Z

I had the same problem. I had a "External Virtual Switch" that functioned, and my docker host got an IP from DHCP on the LAN. When WIFI is enabled, it all breaks. Seems a problem with bridging? I read elsewhere that I needed to remove external switch and create a NAT virtual switch with "New-NetNat". This actually worked fine until the next time I rebooted.

Hyper-V feels so fragile, I feel like VirtualBox was a better option. We were just wanting to find a stable environment for developers to work in.

kenchilada · 2017-02-22T02:43:30Z

Followup to previous... if I reboot it starts working again.

In case it helps anyone, I followed this guide to setup the NAT switch...
http://www.thomasmaurer.ch/2016/05/set-up-a-hyper-v-virtual-switch-using-a-nat-network/

Then I stood up a dhcp server on that network to assign ipv4 addresses.

gkorndorffer · 2017-06-04T18:08:22Z

I'm experiencing the same issues, Windows 10, no Virtualbox drivers... Virtualization is enabled, hyper-v is enabled...but when I install Docker, all network adapters get disabled

evra · 2017-09-02T19:56:43Z

I solved this issue by enabling "Shared Usage" of the WiFi adapter (Docker restart is required).

dkouzhel · 2017-09-27T12:45:41Z

Try to disable "LAN / VLAN Switch" in BIOS. The laptop automatically switch off WLAN with other online connection (ethernet or vlan or vpn). Also this feature may be exist in WLAN "Driver Properties".

sukumarsk · 2017-10-20T08:37:17Z

I faced the same issue and tried all the above suggestions.

Finally , I disabled the DocketNAT adapter (Control Panel\Network and Internet\Network Connections)
Connected back WiFI and at command prompt, issued below commands
ipconfig /release
ipconfig /renew

Enabled DockerNAT.

Now I am able to connect WiFi and also DockerNAT,

sukumarsk · 2017-10-24T04:54:58Z

Further to my previous comment, I researched little more and found solution at

https://superuser.com/questions/1100336/issue-with-wifi-adapter-with-docker-windows-native-hyper-v

I have chosen option #2 and it resolved my issue.

Hope this helps.

benmccallum · 2018-05-09T04:21:49Z

Had this on my Dell XPS13 9360. Upgrade from Windows Home to Pro, never had any other virtualization software on this laptop. Installed Docker for Windows, was prompted that they'd enable Hyper-V and accepted. After reboot no wi-fi connection.

Played around with a few of the suggestions above but couldn't get bridges to work. Also enabled sharing but nothing. Ran the network troubleshooter and no problems found. In the end for some reason clicked the Network PC icon in the system tray and up came the list of wi-fi networks in range. Clicked the one I usually use and it connected...

Thought that was just a fluke but I've restarted Docker, still works, restarted the laptop, still works, updated Docker, still works. Yet to run anything in there, but seems promising so far.

TL;DR; I guess it seems like it had forgot about my Wi-Fi network creds because I was going over a new adapter I guess.

olivierlevy · 2018-09-14T10:32:28Z

Disable the vEthernet (default Switch)
Open Hyper-V Manager, select your computer on the left, you should have the possibilities to create the virtual network switch, but if you already have DockerNAT change from Internal to External network and select your wifi adapter

jerrychong25 · 2019-08-28T00:40:54Z

Disable the vEthernet (default Switch)
Open Hyper-V Manager, select your computer on the left, you should have the possibilities to create the virtual network switch, but if you already have DockerNAT change from Internal to External network and select your wifi adapter

Hi @olivierlevy,

After follows your settings, I could connect to my WIFI.

However, after reboot, I need to configure same steps every time I reboot my laptop.

Is there any ways to permanently fixes this issue?

Thanks.

olivierlevy · 2019-08-28T07:31:30Z

Hi @jerrychong25 , unfortunately, yes, you shall add a shortcut in you desktop to quickly go to your adapter ; or create or find a software that does the changes for you. My company made this kind of software that solved the issue, but I cannot share this :(

jerrychong25 · 2019-08-28T08:37:24Z

Hi @jerrychong25 , unfortunately, yes, you shall add a shortcut in you desktop to quickly go to your adapter ; or create or find a software that does the changes for you. My company made this kind of software that solved the issue, but I cannot share this :(

Hi @olivierlevy, it is pretty annoying to turn off everytime after reboot.

Hope anyone that can share this software.

docker-robott · 2020-06-18T03:12:57Z

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

londoncalling added area/windows 10 kind/bug labels Oct 10, 2016

londoncalling mentioned this issue Oct 10, 2016

Feedback for: docker-for-windows/index.md docker/docs#100

Closed

rn added area/network and removed area/windows 10 labels Oct 10, 2016

rn added the status/needs-information label Oct 10, 2016

dgageot added the area/hyper-v label Oct 18, 2016

rn closed this as completed Oct 28, 2016

dgageot removed the status/needs-information label Feb 2, 2017

londoncalling mentioned this issue Jun 5, 2017

d4win troubleshooting topic on wifi, networking issues docker/docs#3497

Merged

docker-robott added the lifecycle/locked label Jun 18, 2020

docker locked and limited conversation to collaborators Jun 18, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Enabling Hyper-V feature turns my wi-fi off #139

Enabling Hyper-V feature turns my wi-fi off #139

londoncalling commented Oct 10, 2016

rn commented Oct 10, 2016

simonferquel commented Oct 11, 2016

tommiehansen commented Oct 20, 2016

shazChaudhry commented Oct 20, 2016

londoncalling commented Oct 28, 2016

rn commented Oct 28, 2016

ladvishal1985 commented Feb 20, 2017

londoncalling commented Feb 21, 2017

friism commented Feb 21, 2017

kenchilada commented Feb 22, 2017

kenchilada commented Feb 22, 2017

gkorndorffer commented Jun 4, 2017

evra commented Sep 2, 2017

dkouzhel commented Sep 27, 2017 •

edited

sukumarsk commented Oct 20, 2017

sukumarsk commented Oct 24, 2017

benmccallum commented May 9, 2018 •

edited

olivierlevy commented Sep 14, 2018

jerrychong25 commented Aug 28, 2019

olivierlevy commented Aug 28, 2019 •

edited

jerrychong25 commented Aug 28, 2019

docker-robott commented Jun 18, 2020

Enabling Hyper-V feature turns my wi-fi off #139

Enabling Hyper-V feature turns my wi-fi off #139

Comments

londoncalling commented Oct 10, 2016

Expected behavior

Actual behavior

We need this information from the user:

Information

Steps to reproduce the behavior

rn commented Oct 10, 2016

simonferquel commented Oct 11, 2016

tommiehansen commented Oct 20, 2016

shazChaudhry commented Oct 20, 2016

londoncalling commented Oct 28, 2016

rn commented Oct 28, 2016

ladvishal1985 commented Feb 20, 2017

londoncalling commented Feb 21, 2017

friism commented Feb 21, 2017

kenchilada commented Feb 22, 2017

kenchilada commented Feb 22, 2017

gkorndorffer commented Jun 4, 2017

evra commented Sep 2, 2017

dkouzhel commented Sep 27, 2017 • edited

sukumarsk commented Oct 20, 2017

sukumarsk commented Oct 24, 2017

benmccallum commented May 9, 2018 • edited

olivierlevy commented Sep 14, 2018

jerrychong25 commented Aug 28, 2019

olivierlevy commented Aug 28, 2019 • edited

jerrychong25 commented Aug 28, 2019

docker-robott commented Jun 18, 2020

dkouzhel commented Sep 27, 2017 •

edited

benmccallum commented May 9, 2018 •

edited

olivierlevy commented Aug 28, 2019 •

edited