I’m using an Intel Wi-Fi 6E AX210 (Gig+) wireless card on an ASRock B760M Pro RS/D4 motherboard. I need Wake on Wireless LAN (WoWLAN) to work, so I can remotely wake the PC over Wi-Fi. However, when WoWLAN is enabled, an issue appears: the computer wakes up on its own from sleep or hibernation, without receiving a magic packet.
Additionally, it was observed that disabling the second power management checkbox on the adapter (the one that allows the device to wake the system) completely stops the unexpected wakeups. However, this also breaks WoWLAN functionality, as the adapter can no longer wake the system even via a proper magic packet — making this workaround unacceptable for the intended use case.
Here’s what I’ve configured:
Windows 11 Pro 24H2 26100.3476
All power management options for the adapter are enabled.
Only wake on magic packet is allowed — pattern match and other triggers are disabled.
Fast startup is disabled everywhere (Windows and BIOS).
Wake timers are disabled in the power plan.
BIOS allows wake only via PCI, all other wake sources are off.
The system is currently running the latest Intel Wi-Fi 6E AX210 (Gig+) driver — version 23.140.0.3, released in June 2025. Previously, version 23.120.0.3 from February 6, 2025 was tested — and the spontaneous wake issue occurred on that version as well.
Wake timers have also been checked — running powercfg /waketimers returns no active timers, confirming that there are no scheduled tasks or events set to wake the system.
Back when fast startup was enabled, the PC would power on almost every hour, even from shutdown (which I now realize was hybrid shutdown). After disabling it, the issue persists.
Additionally, the Event Viewer logs system wake events with no identifiable source. In the System log, you’ll find entries from Kernel-Power with Event ID 107, indicating that the system resumed from sleep or hibernation. However, the parameter WakeRequesterType is set to 0, which means Windows was unable to determine which device triggered the wake event.
Anyone encountered this? Could it be AX210 drivers, BIOS quirks, or ACPI misbehavior?
