windows 10 chrome not connecting to internet after sleep
Source: https://superuser.com/questions/1101707/google-chrome-unable-to-access-internet-for-several-minutes-after-hibernate
Not sure why this fixed it, but turning off "automatically detect settings" for LAN settings fixed it.
Settings:
Show advanced settings:
Change proxy settings:
LAN Settings:
Uncheck automatically detect settings:
- Thank you, your solution works fine so far. Windows 10 (version 10.0.16299.19) and Chrome 62. – AnAurelian Nov 1 '17 at 15:06
- 2I found a Chrome bug report about this a year ago without a fix. This fixed it, finally! I'm quite curious about how you found this. :) – Wouter Nov 28 '17 at 19:37
- For reference, in case Chrome devs find this. My version is 62.0.3202.94 – Wouter Nov 28 '17 at 19:37
- I don't really recall how I eventually figured it out... could have been something someone suggested, could have just been trial and error. Was too long ago for me to remember, but it seems it's been more of an issue for people lately as this question has gotten a few upvotes recently :O – Kritner Nov 28 '17 at 19:39
- I'm not sure if this will fix it for me yet or not (I'll try to reply in a few days after testing). If this DOES work, I have a feeling it has something to do with the new Windows 10 Fall Creators Update (Version 1709). In Hyper-V, they added a new "Default Switch" that you cannot get rid of. It "hijacks" your network connection so that your VMs can communicate with your host OS. – DaleyKD Nov 28 '17 at 20:56
Sledgers answer is more relevant now after the Windows 10 Fall Creators edition, as addressed by daleykd in his initial response to the option to fixing in "Internet Options".
If using Hyper-V (even if not directly, i.e. for Docker), then Windows 10 creates a default switch network adaptor, that will route all traffic. This switch seems to fail on Chrome (and Firefox) for 30 to 60 seconds, and then reverts to the auto selected one (Wifi or Ethernet).
The simplest solution is to disable the interface:
netsh interface set interface "vEthernet (Default Switch)" admin=disable
Second Edit: This only actually occurs if Docker is using the new linux subsystem to create linux containers, and even if they are then the "Automatically detect settings" in "Internet Options" fixes it after a sleep. It was good to know the cause, though!
- Won't that cause problems when actually using Hyper-V? I. e. inability for any virtual machine using that switch to access the network? – plocks Feb 8 at 9:50
I disabled use of predictive service in chrome advanced settings and turned of automatic in Lan windows settings and it worked
