Unable to enable WoWLAN  

Hi, I'll be as descriptive as I can here.

I am trying to enable WoWLAN on my wireless card (Intel AX201).

I don't have a Power Management tab in Device Manager for this device so I can't enable it that way.

My laptop is a Lenovo Yoga 7 and the BIOS does not have a Power Management tab either, or any other 'wake on' option.

I've tried logging in as Administrator and enabling the WoWLAN through command line and I get the following message:
powercfg /deviceenablewake "Intel(R) Wi-Fi 6 AX201 160MHz"
You do not have permission to enable or disable device wake.

However, the device is listed when I execute the powercfg -devicequery wake_from_any command so I think it has the required capability.

I've also tried adding the registry entry to enable the Power Management tab, but this also led to nothing.

Anyone have any suggestions?

Try disabling Fast Startup.

The reason why the Power Managemet tab is missing is because your system doesn't support the S3 (Standby) power state. If you run the powercfg a command from a command window, you will notice that, instead, it supports S0 (Low Power Idle). This specific type of Standby is also known as Modern Standby. To bring back support for traditional-old S3, what you can do on Windows 10 version 20H2 is open an elevated command prompt and execute the following command that will add a registry value to the Windows registry:

Code:

reg add HKLM\System\CurrentControlSet\Control\Power /v PlatformAoAcOverride /t REG_DWORD /d 0

Next, restart your laptop. Now, if you run the powercfg a command again, you should see that the S3 (Standby) power state is supported, and the Power Management tab is visible in the properties window of the Intel WiFi AX 201 adapter.

The official documentation of this Windows registry setting is here:
https://docs.microsoft.com/en-us/win...modern-standby

hdmi said:

The reason why the Power Managemet tab is missing is because your system doesn't support the S3 (Standby) power state. If you run the powercfg a command from a command window, you will notice that, instead, it supports S0 (Low Power Idle). This specific type of Standby is also known as Modern Standby. To bring back support for traditional-old S3, what you can do on Windows 10 version 20H2 is open an elevated command prompt and execute the following command that will add a registry value to the Windows registry:

Code:

reg add HKLM\System\CurrentControlSet\Control\Power /v PlatformAoAcOverride /t REG_DWORD /d 0

Next, restart your laptop. Now, if you run the powercfg a command again, you should see that the S3 (Standby) power state is supported, and the Power Management tab is visible in the properties window of the Intel WiFi AX 201 adapter.

The official documentation of this Windows registry setting is here:
https://docs.microsoft.com/en-us/win...modern-standby

Many thanks, that did the trick regarding the extra options. I'm sure I can take it from there.

My observations after enabling S3 and changing the settings on the network adapter, the laptop goes into sleep mode and can't be wakened by button presses any more. Also, I can no longer ping the network card (in modern standby I could). However this has given me something to work with. Thank you.

Different laptops can have different reasons why a keypress doesn't wake them from sleep.

• 'Wake up from keyboard' setting was set to Disabled in BIOS
• Power & Sleep settings | Edit Plan Settings | Change advanced power settings | Sleep | Allow Wake Timers was set to Disabled in Windows Settings
• https://answers.microsoft.com/en-us/...505bcfb?auth=1
• The keyboard device has an 'Allow this device to wake the computer from sleep' checkbox
• ...

- - - Updated - - -

jmatt said:

Try disabling Fast Startup.

Disabling Fast Startup may be required if the goal is to use WoWLAN to power up the laptop, but if the goal is only to use WoWLAN to wake up from S3 Standby, then disabling Fast Startup is not required.

Thanks for all the answers.

I did some reading and understand that I won't be able to do this the way I had hoped.

I've moved on to the scheduled task route, however there seems to be a bug on this one (according to other users) that prevents it from waking my machine from sleep/hibernate. The task seems to only execute when I manually wake my laptop from sleep.