Google Chrome unable to access internet for several minutes after hibernate

Posted on

Problem :

Recently my Google Chrome on Windows 10 (only on a single machine out of 4) has had issues with connecting to websites for 2-5 minutes after the machine coming out of hibernate/sleep.

The issue is specific to chrome, as I can open IE and get to sites immediately. In addition, when working on local development through Visual Studio, Chrome can’t even manage a localhost hosted page show up, until the issue has resolved itself after the 2-5 minutes.

Has anyone experienced this before, and know what kind of settings I should look at to diagnose and/or fix?

Solution :

Not sure why this fixed it, but turning off “automatically detect settings” for LAN settings fixed it.


enter image description here

Show advanced settings:

enter image description here

Change proxy settings:

enter image description here

LAN Settings:

enter image description here

Uncheck automatically detect settings:

enter image description here

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!

I disabled use of predictive service in chrome advanced settings and turned of automatic in Lan windows settings and it worked

I had a similar problem which i discovered was due to virtual network adaptors, easy fix. I posted a 2 min video on youtube Showing the issue and the fix. hope this is of some help.

Leave a Reply

Your email address will not be published. Required fields are marked *