Windows 10 1703 / 1709 - WOL issues

[CHiLL]

Hello. Since we have upgraded from Windows 10 1607 to 1709, we have noticed that Wake-on-Lan has stopped working. WOL was working correctly when using 1607 and Windows 8.1.

 

I think it has something to do with the way that Windows 10 shuts down the computer, as the Ethernet link lights are off. On 1607/Windows 8.1...they would still be flashing, even with the PC off.

 

I have performed the following:

1) Checked that 'Allow the computer to turn off this device' is unchecked on the Ethernet connection.

2) Ensured that Wake-on-LAN is enabled in BIOS.

 

What I have found, is that if I manually shut down the computer or use Impero to shut down, the link lights are off.

If I power on the PC and go into BIOS...and THEN press the power button to shut down the PC...the link lights are on.

 

That to me points this to being a Windows 10 1709 issue. After some quick Googling, others have had issues with 1703 Creators Update, but I can't seem to find a solution.

 

I'm wondering has anyone else encountered this or got it sorted?

[Michael]

I suspect it's driver related. If you upgraded 1607 > 1709, try going into Device Manager and rolling back the driver.

[CHiLL]

I suspect it's driver related. If you upgraded 1607 > 1709, try going into Device Manager and rolling back the driver.

Cheers for that. We did a clean install. I'll find the latest Intel driver and see how that works.

[Michael]

I agree with your diagnosis perfectly though, it has to be OS related.

[Joh619]

Do you have fast startup enabled on the machines? I've seen that cause loads of WOL issues on Windows 10.

[NightsWatch]

Hi were having the same problem now with Windows 10 1709. Did you find a fix for this?

 

Thanks

[Oaktech]

Have you disabled hybrid sleep/fast start? That screws up everything as it puts the machine into a state that very few NICs can restore from.

 

https://www.windowscentral.com/how-disable-windows-10-fast-startup

[CHiLL]

Hi were having the same problem now with Windows 10 1709. Did you find a fix for this?

 

Thanks

Turns out that in our scenario, the Intel drivers were not being installed correctly by SCCM. Therefore we were using the very basic drive (or the default one that Windows 10 installs), which didn't include the WOL features. After deploying out the driver package to the clients, WOL started working again.