Windows 10 build 1809 wake-up on LAN issue

My MSI MEG creation x399 motherboard uses dual Intel i211 NIC's that I needed in a LAG team which couldn't be done in Windows 10 build 1809 without installing the new Intel 23.5.2 drivers that require the use of POWERSHELL to implement teaming as Microsoft is removed the Windows interface properties in 1809.

This brings me onto the issue in my question is it now seems that the windows properties interface implementation of wake-up on LAN now seems to not work as it did previously on 1803 with the same BIOS configuration and standard setup as before like disabling fast start-up in the power options et cetera.

I would be grateful if somebody could confirm that they've got it working on their motherboard with our without an Intel NIC's in Windows build 1809, and if so how?

MSI support recommend going to a older Intel driver that is not supported in Windows 1809 and would require me roll them back to 1803. Also Intel support has also not been helpful as they also require me to also roll back to the earlier version of Windows and the older MSI Intel drivers which is no solution at all.

Total qualify this doesn't seem to be my implementation as I followed the steps I previously used that worked but it seems to be that Microsoft and Intel haven't coordinated the testing of this functionality which was also the case with the teaming issue that required them to bring out a new 23.5.2 driver that you can read about in this Intel thread.

Hi,

 

Thank you for writing to Microsoft Community Forums.

 

The feature completely depends on the device hardware and the drivers. As the MSI suggests going to an older version of Intel driver, which is not supported with Windows 10 version 1809, I would suggest to install the driver in compatibility mode and see if it works.,

Make older programs compatible with this version of Windows

 

I would also suggest to check if wake up on LAN is enabled in BIOS. Kindly refer to the following article.

MSI MEG CREATION X399 Wake up on LAN

 

Disclaimer: Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk. 

 

You may also want to get in touch with Intel to have a check if the new device driver (update) supports the feature on Windows 10 1809.

 

Hope it helps.

 

Regards,

Peer Samie

Microsoft Community-Moderator

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Peer_Sam

Thank you for your suggestion and I will continue to prompt MSI the release and up to date version their network current drivers as I feel this is the only solution that will allow me to keep the functionality of NIC bonding in a teaming scenario as I believe Microsoft has removed this functionality in Windows 10 1809 requiring MSI to implement a powershell solution.
As this is the priority above wake-up on LAN I would rather leave things as they are as I'm pretty sure the compatibility mode would not solve the teaming issue but it might solve the wake-up on LAN issue.

What makes this even more frustrating is that Intel have confirmed that there latest network drivers, being generic, may not have the wake-up on LAN functionality I need so I have to wait for MSI to update their drivers.

All in all nearly 6 months after Windows 10 1809 build release a lot of third-party don't seem to have been ready for its implementation.

Anyway thanks for your speed reply this

PS. You can imagine my amusement as I realise that you had linked to my MSI thread, I was the original OP that started that thread so you can see I've been dealing with this issue over many builds of Windows 10.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

A  post 1/2019  1803 (and beyond) update broke Wake On Lan on all 88 of our network workstations of varying makes.

With 1803 and before, we had no issues using WOL even if the machine was fully shut down by the user. As long as there were no power outages WOL would bring all of our units ouf of full shutdowns.

Now the magic packets are being received by the workstations but they are not woken by those packets.

And yes, Fast Boot is disabled, PME is enabled, etc. etc. etc....

It is not a BIOS, Driver, Setting or Network issue. The problem is with Windows 10.

These machines are all using the native NIC drivers provided in the Windows 10 release which has a fairly old date as issued by Microsoft. Updated Intel NIC drivers for Windows 10 are not available from Intel's site.

The issue also occurs with non Intel Nics.

If I install WIN 10 1803 and only apply updates issued up to about 12/2018 or so, those same machines will work properly. I have been unable to find the single offending update.


-JMS

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Optical10,

I'm not sure if you've been able to resolve this yet but I've recently had a similar issue with a windows 10 tablet not wanting to WOL post update with and Intel I211 NIC.

As you've done, I've been though my BIOS settings with a fine tooth comb, nothing exceeds S3 sleep state. Fast startup is disabled, energy efficient Ethernet etc are disabled in the network driver settings in the device manager as well as enabling wake on magic packet. Yet still I couldn't get this tablet to WOL after a shutdown. It would wake from sleep mode though...

In the end my problem was resolved when I installed the Intel proset configuration utility.

When I reviewed the adaptor settings from within this app, I had an extra setting "Wake on magic packet from power off state" which ISN'T available through the advanced tab of the network adaptor properties in device manager. When I enabled this option, WOL started behaving itself again from a shutdown state.

As your symptoms and network adaptor were the same as mine I thought i'd share this nugget in case this resolves your issue too.

I'm using network driver version 12.15.181.1 which was released on 11/01/2019

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi MarkMQ

Many thanks as I came to the same conclusion via Proset but didn't report back here earlier.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello,

I did all you post. In the first 2 minutes after hybernation or shutdow  , i can wake on lan without problem  however, after 2 minutes wake on lan doent works.....Did you test wol after 2 minutes...any news about this problems. Thanks!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello,

I did all you post. In the first 2 minutes after hybernation or shutdow  , i can wake on lan without problem  however, after 2 minutes wake on lan doent works.....Did you test wol after 2 minutes...any news about this problems. Thanks!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated April 19, 2025 Views 1,191 Applies to: