No interent connection for ethernet after hibernation/gateway shutdown

I'm on Windows 10 1909 and I use this PC as a HTPC which I allow to hibernate after 30-minutes of inactivity, also, I have it set to reboot every other night. I have been shutting down my internet gateway every night now and the gateway is turned back on every morning.

Often, when I bring it out of hibernation, the network icon in the system tray claims that there is no internet connection; however, the gateway is on and I can run Firefox and browse the internet all I want.

I run the Hulu and the Netflix apps, however, when the system tray network icon says "no internet connection" the Netflix app (I run that more often than Hulu) says that it cannot connect to the internet. This is clearly not correct as I have no problems browsing with Firefox.

After waiting for some time, I am not exactly sure how long - sometimes it seems like about 10-minutes, Windows finally figures out once again that it has an internet connection and Netflix runs happily - even though Firefox had no problems running and browsing the internet since the PC came out of hibernation.

What I am wondering is if there is a way to set the network subsystem to check for an internet connection immediately or within a minute or so after the PC comes out of hibernation. Or, have the network subsystem check for an internet connection once every two minutes or something like that.

Thanks in advance!

Settings > Network & Internet > Change adapter options

Right-click on the specific adapter and select Properties.

Select Configure.

Click on the Power Management tab.

Uncheck the power saving options.

OldNavyGuy said:

Settings > Network & Internet > Change adapter options

Right-click on the specific adapter and select Properties.

Select Configure.

Click on the Power Management tab.

Uncheck the power saving options.

Thank you for your reply.

I tried this last night. Unfortunately, there was no change in the outcome.

It seems like if I disable, then enable the adapter, it sometimes helps. However, it does not appear to work all the time.

I am guessing that windows periodically checks to see if it recognizes the current network. When my gateway is off, it seems to think that somehow the network has changed, and changes the state to "no internet access". Then after the gateway is on again and after this PC has come out of hibernation, it checks again to see if it recognizes the network, and finally Windows does recognize the network and then allows internet access - this even though I can use Firefox on the internet all I want.

Is there anything else that I might change to try to resolve this?

Thanks again!

How are you shutting down the gateway?

How long has the gateway been on when you come out of hibernation?

Thanks for the replies.

dalchina said:

One possible more extreme option might be to schedule a task to run on resume from hibernation (yes, that is possible) to turn your NIC off and on
How to enable or disable Wi-Fi and Ethernet network adapters on Windows 10 | Windows Central

- but it does seem odd it takes so long.

I have a batch file that runs on an event (off-hand, I do not know the event name) to re-enable a WiFi hotspot on this PC when the PC reboots/comes out of hibernation. At the time I set up the hotspot, I was unable to find out how to reenable the hotspot on reboot/wake from hibernation without this. Depending on whether I find a solution to the problem, I may write another script to do this and then run it on the same event.

OldNavyGuy said:

How are you shutting down the gateway?
How long has the gateway been on when you come out of hibernation?

My gateway is a Linux PC, and I have a resident process that runs and looks for a minor variant of the MAC address so that when it sees that MAC address as part of a "wake-on-lan" sequence, it executess a "shutdown on lan". So I send what amounts to a wake-on-lan signal with the variant MAC address, and then when the Linux PC sees that, the script executes a shutdown command. It allows me to turn the Linux PC on/off without having to go to the machine physically. I do not expect that it would make a difference if I were to go to the machine and shut it down manually as what happens is essentially the same thing.

When I bring the Windows PC out of hibernation, the gateway has typically been on for at least four hours.