Window keeps waking up laptop from Modern Standby

Page 1 of 3 123 LastLast
  1. hdmi's Avatar
    Posts : 561
    10 Home (21H1)
       #1

    Windows keeps waking up laptop from Modern Standby


    Hi,
    On my new laptop (it's in my specs) that came with 2004 preinstalled so far I have figured out that updating it to 20H2 has brought back the option to enter
    Code:
    reg add HKLM\System\CurrentControlSet\Control\Power /v PlatformAoAcOverride /t REG_DWORD /d 0
    (in an elevated command window, and reboot after that) to revert from Modern Standby, or S0 Low Power Idle compatibility back to traditional-old S3 so I am using that for my temporary working solution.
    There's no option to disable Modern Standby in BIOS, and disabling Wake Timers also didn't help. And there wasn't even a Power Management tab to be found in the Intel WiFi 6 adapter's hardware properties panel until finally I got tired of getting frequent wakeups and decided to use the above registry hack.
    Running on 20H2, before the registry hack here's what it gave me:
    Code:
    C:\Windows\system32>powercfg waketimers
    Timer set by [PROCESS]  \Device\HarddiskVolume3\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\StartMenuExperienceHost.exe  expires at 4:00:00 on .
    C:\Windows\system32>powercfg devicequery wake_armed
    NONE
    C:\Windows\system32>powercfg lastwake
    Wake History Count - 0
    C:\Windows\system32>powercfg requests
    DISPLAY:
    None.
    SYSTEM:
    None.
    AWAYMODE:
    None.
    EXECUTION:
    None.
    PERFBOOST:
    None.
    ACTIVELOCKSCREEN:
    None.
    C:\Windows\system32>powercfg a
    The following sleep states are available on this system:
        Standby (S0 Low Power Idle) Network Connected
        Hibernate
        Fast Startup
    The following sleep states are not available on this system:
        Standby (S1)
            The system firmware does not support this standby state.
            This standby state is disabled when S0 low power idle is supported.
        Standby (S2)
            The system firmware does not support this standby state.
            This standby state is disabled when S0 low power idle is supported.
        Standby (S3)
            This standby state is disabled when S0 low power idle is supported.
        Hybrid Sleep
            Standby (S3) is not available.
    After the registry hack with reboot, here's what I got instead:
    Code:
    C:\Windows\system32>powercfg a
    The following sleep states are available on this system:
        Standby (S3)
        Hibernate
        Hybrid Sleep
        Fast Startup
    The following sleep states are not available on this system:
        Standby (S1)
            The system firmware does not support this standby state.
        Standby (S2)
            The system firmware does not support this standby state.
        Standby (S0 Low Power Idle)
            The system firmware does not support this standby state.
    C:\Windows\system32>powercfg waketimers
    Timer set by [PROCESS]  \Device\HarddiskVolume3\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\StartMenuExperienceHost.exe  expires at 4:00:00 on .
    C:\Windows\system32>powercfg devicequery wake_armed
    Intel(R) Wi-Fi 6 AX201 160MHz
    C:\Windows\system32>powercfg lastwake
    Wake History Count - 1
    Wake History [0]
      Wake Source Count - 1
      Wake Source [0]
        Type: Device
        Instance Path: PCI\VEN_8086&DEV_A0F0&SUBSYS_00748086&REV_20\3&11583659&5&A3
        Friendly Name: Intel(R) Wi-Fi 6 AX201 160MHz
        Description: Intel(R) Wi-Fi 6 AX201 160MHz
        Manufacturer: Intel Corporation
    C:\Windows\system32>powercfg requests
    DISPLAY:
    None.
    SYSTEM:
    None.
    AWAYMODE:
    None.
    EXECUTION:
    None.
    PERFBOOST:
    None.
    ACTIVELOCKSCREEN:
    None.
    Next, I unchecked the "allow this device to wake the computer" for the WiFi adapter, and I also turned the Wake Timers back on, just to see how stuff will behave. So far it hasn't woken up in a while.
    Is there anything I could try to get Modern Standby to work properly without it waking itself back up for no good reason, usually within the next hour?
    Last edited by hdmi; 07 Jan 2021 at 04:38.
      My Computers


  2. Posts : 288
    Windows 10 Home
       #2

    Hi. I recently noticed a similar problem with my desktop pc waking from sleep randomly. If I put it to sleep manually it would wake up within a minute or so. Only seemed to happen after using pc for long periods. I use an ethernet connection and in the Device Manager under Network Adapters in Realtek Gaming GbE Family Controller Power Management I unchecked Allow this device to wake the computer. The problem never happened again after that.
      My Computer

  3. hdmi's Avatar
    Posts : 561
    10 Home (21H1)
    Thread Starter
       #3

    Mcd73165 said:
    Hi. I recently noticed a similar problem with my desktop pc waking from sleep randomly. If I put it to sleep manually it would wake up within a minute or so. Only seemed to happen after using pc for long periods. I use an ethernet connection and in the Device Manager under Network Adapters in Realtek Gaming GbE Family Controller Power Management I unchecked Allow this device to wake the computer. The problem never happened again after that.
    Yeah, unchecking "Allow this device to wake the computer" is probably the most common solution, and that has worked for me on several computers over the years. But in this case the WiFi controller didn't actually have a Power Management tab because, as it turned out, this new laptop supports a form of sleep known as Modern Standby, or Low Power Idle (S0). In a nutshell, it basically means that Windows can keep running the system with only limited functionality, kind of like how an Android smartphone also does it when you put it in ultra power saving mode. BUT... it also means that any system that supports Modern Standby can not support Standby (S3). I suppose that explains why the WiFi had no Power Management tab. I was lucky enough that the registry hack worked for me, as that's what effectively removed support for Modern Standby, thereby bringing back support for Standby (S3). The powercfg a command output confirms this.

    My only question I have now is, how do I keep my laptop from waking itself up after I undo the registry hack. Does anyone know?
      My Computers

  4. Ander's Avatar
    Posts : 31
    Windows 10
       #4

    hdmi said:
    My only question I have now is, how do I keep my laptop from waking itself up after I undo the registry hack. Does anyone know?
    Why on Earth would you want "Modern Standby" on your PC? Really, you want your hard drive, CPU and memory to keep running when you're not using it, depleting your battery, keeping your system hot and shortening its life, just because Microsoft thinks laptops should be like smartphones?

    I'm utterly grateful for that registry "hack". Forcing Modern Standby on us was a thoughtless thing for MS to do. (They didn't even announce the change till after it was in effect for some time—is that creepy or what?) I still don't don't understand what they were thinking. No, our PCs do not have to stay running and online even when we're not using them.

    When Modern Standby was pushed onto us nearly two years ago, I was forced to use Hibernation, even when stepping away from my PC for brief periods, and wait for my entire Windows session to reload from disk each time I returned. It's wonderful having normal Standby back again! IMHO, "Modern" Standby is like "modern" pollution or overpopulation... Just because something's new doesn't mean it's good.
      My Computer


  5. Posts : 1,657
    Windows 10 Pro 21H1 19043.928
       #5

    My MSI laptop (winver 2004) is too old to support S0. Powercfg -a shows S3 is available, however; while using Sleep, the battery state of charge (SOC) is depleted at a rate of about 2%/hour.

    The laptop does not suffer from waking ever, I keep all Power Management settings set to 'not allow wake'.

    Are you suggesting that upgrading to 20H2 and using the registry tweak in post #1 will fix this rapid battery decay and fully restore the previous features of S3?

    This tweak doesn't fix anything on the MSI laptop while using 2004.

    I stopped using Hibernation after adding an SSD for the OS.

    S3 Sleep was perfect for standby before it started consuming the battery SOC.

    I desperately want this PC to have the ability to Standby as it as it always had before S3 was destroyed.
      My Computer

  6. hdmi's Avatar
    Posts : 561
    10 Home (21H1)
    Thread Starter
       #6

    W10 Tweaker said:
    My MSI laptop (winver 2004) is too old to support S0. Powercfg -a shows S3 is available, however; while using Sleep, the battery state of charge is depleted at a rate of about 2%/hour.

    The laptop does not suffer from waking ever, I keep all Power Management settings set to 'not allow wake'.

    Are you suggesting that upgrading to 20H2 and using the registry tweak in post #1 will fix this rapid battery decay and fully restore the previous features of S3?
    No, the registry setting gets ignored by Windows 10 if the system hardware cannot support "Standby (S0 Low Power Idle)"─also known as Modern Standby. In addition to this, the registry setting only applies to Windows 10 version 20H2 or later. A different registry setting that has the same effect as this one can be used on Windows 10 versions older than 2004, but there exists no such possibility on version 2004 so that used to be a "disaster of cataclysmic proportion" for some people with certain laptops. What the registry setting does is it disables Modern Standby on systems that support Modern Standby, at least if we can assume that the BIOS isn't force-enabling it, in which case you could still force-disable it by using a bootloader as a workaround the major downside of which is you'd have to sacrifice Secure Boot for that to work... lucky for me my BIOS knows how to behave itself because I had decided to use my brain─like always─and get it from the local grocery store (and I didn't buy my laptop until AFTER Windows 10 version 20H2 came out so no problemo in THAT department, either... ).
      My Computers



  7. Posts : 1,657
    Windows 10 Pro 21H1 19043.928
       #7

    hdmi said:
    No, the registry setting gets ignored by Windows 10 if the system hardware cannot support "Standby (S0 Low Power Idle)"─also known as Modern Standby. In addition to this, the registry setting only applies to Windows 10 version 20H2 or later. A different registry setting that has the same effect as this one can be used on Windows 10 versions older than 2004, but there exists no such possibility on version 2004 so that used to be a "disaster of cataclysmic proportion" for some people with certain laptops. What the registry setting does is it disables Modern Standby on systems that support Modern Standby, at least if we can assume that the BIOS isn't force-enabling it, in which case you could still force-disable it by using a bootloader as a workaround the major downside of which is you'd have to sacrifice Secure Boot for that to work... lucky for me my BIOS knows how to behave itself because I had decided to use my brain─like always─and get it from the local grocery store (and I didn't buy my laptop until AFTER Windows 10 version 20H2 came out so no problemo in THAT department, either... ).

    Thanks for the detailed response.

    My important take-away from this information is that 2004 may not be correctable, unless my early version 2004 image functions properly. Also, any laptop that does not support S0 can't be fixed without rolling back the OS to the first 2004 or 1909 and earlier.

    I've read about this tweak that requires sacrificing Secure Boot, I wouldn't have accepted that option even if it was available for this PC/OS etc. I do know that immediately after my upgrade to 2004, the S3 Sleep function still worked correctly on this PC and did not consume excessive battery SOC until one of the updates killed S3.

    Once I can determine which update killed S3, I can work around that and share the info for others caught by this horrible destruction.

    I've intended to prove this by restoring an OS image I created immediately after the 2004 update, however; numerous family obligations have monopolized my time for the past 3.5 months. Thanks again.
      My Computer

  8. hdmi's Avatar
    Posts : 561
    10 Home (21H1)
    Thread Starter
       #8

    W10 Tweaker said:
    Also, any laptop that does not support S0 can't be fixed without rolling back the OS to the first 2004 or 1909 and earlier.
    To my best knowledge, any laptop that does not support the S0 Low Power Idle powerstate and that isn't extremely old or exotic should already support S3 right out of the box so then there will be no need to fix it anyway in the first place.
    I've read about this tweak that requires sacrificing Secure Boot, I wouldn't have accepted that option even if it was available for this PC/OS etc. I do know that immediately after my upgrade to 2004, the S3 Sleep function still worked correctly on this PC and did not consume excessive battery SOC until one of the updates killed S3.
    With S3, the power consumption during sleep shouldn't change all by itself. If it does, usually it's a defective battery or the laptop is waking up in the middle of the night to install Windows updates before automagically going back to sleep like nothing happened. Some updates (including some driver updates) may alter the power settings on certain hardware. Check your power plan's advanced settings and go through your list of hardware components in Device Manager to see if anything had changed on any of the components' Power tab. The "Allow this device to wake the computer" checkbox of the network adapter(s) is what typically has to be kept disabled in order to cure common sleepwalking behaviors.
      My Computers


  9. Posts : 1,657
    Windows 10 Pro 21H1 19043.928
       #9

    W10 Tweaker said:
    My important take-away from this information is that 2004 may not be correctable, unless my early version 2004 image functions properly.

    Also, any laptop that does not support S0 can't be fixed without rolling back the OS to the first 2004 or 1909 and earlier.

    hdmi said:
    To my best knowledge, any laptop that does not support the S0 Low Power Idle powerstate and that isn't extremely old or exotic should already support S3 right out of the box so then there will be no need to fix it anyway in the first place.

    My comments above were with respect to fixing S3 to work correctly on a laptop while using winver 2004 or later. When Micro$oft altered the behavior of S3 Sleep (early 2021), it was to prevent true sleep & to keep the device ready for immediate updates & rapid starts, a hybrid Sleep/Standby condition.

    I agree about your comment on S3 being available for many devices, 'out of the box'. The important detail is that S3 post winver 2004 is not the same as it was. As a result, we can't simply refer to this as [S3 Sleep] because it is not the same feature as S3 has been for ages.


    hdmi said:
    With S3, the power consumption during sleep shouldn't change all by itself. If it does, usually it's a defective battery or the laptop is waking up in the middle of the night to install Windows updates before automagically going back to sleep like nothing happened. Some updates (including some driver updates) may alter the power settings on certain hardware. Check your power plan's advanced settings and go through your list of hardware components in Device Manager to see if anything had changed on any of the components' Power tab. The "Allow this device to wake the computer" checkbox of the network adapter(s) is what typically has to be kept disabled in order to cure common sleepwalking behaviors.
    At least S3 Sleep used to behave that way, however; that suddenly changed early this year when M$ killed S3 and also altered the GUI based 'shutdown state'. I've reviewed battery reports using powercfg and tested battery SOC decay during S3 Sleep, a full shutdown and a full shutdown using Command Line (shutdown /s /f /t 0).

    I just checked my records from last May, a GUI based full shutdown lost 40% SOC in 11.3 hours.
    The next day a Command Line shutdown (shutdown /l /s) consumed 2% SOC in 8 hours.

    Do you have a laptop using winver 2004 or later that does not consume battery SOC while in S3 Sleep? I'd be interested to learn how this is possible & which changes I require on my PC to duplicate this behavior. Before the change to S3, earlier this year, Sleep on this PC used only a small amount of energy, a slight bit more than a complete shutdown (before the changes). That is no longer the case on my PC and from what I've been reading online, many other users are experiencing the same.

    This Standby condition or new S3 behavior is not the same as the old version of Sleep, it consumes battery state of charge (SOC) at a much faster rate. I have been keeping a log file that consistently demonstrates a steady decay in the battery's SOC charge at a rate of approximately 2%/hour.

    This change is relatively consistent & linear over any time period. And yes, I have verified that no devices are 'wake armed'. I've also experimented with disabling the network adapter and other potential power consuming items that show no large improvement in the rate of change on the battery's SOC.


    Window keeps waking up laptop from Modern Standby-image.png

    I've read about this tweak that requires sacrificing Secure Boot, I wouldn't have accepted that option even if it was available for this PC/OS etc. I do know that immediately after my upgrade to 2004 (~Dec 2020), the S3 Sleep function still worked correctly and did not consume excessive battery SOC until one of the updates soon after, killed S3.

    Once I can determine which update killed S3, I can work around that and share the info for others caught by this horrible destruction.

    I've intended to prove this by restoring an OS image I created immediately after the 2004 update, however; numerous family obligations have monopolized my time for the past 3.5 months. Thanks again.
      My Computer

  10. hdmi's Avatar
    Posts : 561
    10 Home (21H1)
    Thread Starter
       #10

    @W10 Tweaker

    My laptop is on AC power a lot, but I'm pretty sure it doesn't drain the battery that fast during S3 sleep. Either way, I'll check again soon enough and report back. Thanks for letting me know.
      My Computers


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:26.
Find Us




Windows 10 Forums