Solved Windows 11 stalls upon waking from "modern standby" (S0)

I have a new PC with Windows 11 Pro. It doesn't have standard "sleep" (S3) mode available. Like many new PCs, it only supports "modern standby" (S0) or hibernate. I don't want to wait for hibernate to recover, so I am using modern standby (S0). If I leave my PC, it goes into this standby mode according to the Power/Sleep settings in Windows. But what I have found is that when I wake the PC, the screen immediately turns on and the desktop is displayed, but the first few attempts to click on a shortcut are not recognized. If I wait about 10 seconds, then my clicks are recognized. Has anyone seen this delay recognizing input after waking from moderns standby before? As mentioned, the display comes back immediately -- it's only the mouse-clicking to open an app that doesn't respond. I can move the mouse cursor just fine, so the mouse device and Windows are communicating and responding immediately upon wake. But starting an app by double-clicking a desktop shortcut seems to have some type of delay.

What are the apps you are trying to run? If the app you are trying to run is a browser app or the app requires data from the Internet, you would be experiencing the speed of the Internet. In that case there will always be an Internet lag.

Usually I open Thunderbird mail as soon as I wake the PC from sleep/standby. But on my previous PC which had regular S3 sleep, this never happened. Waking the PC and double-clicking an icon to start Thunderbird always worked the first time. Now it consistently ignores my actions for about 10 seconds. The internet connection to both PCs was the same (wired ethernet to the same router). My other to devices (Windows 11 laptop don't experience this issue), so it's definitely something specific to the new PC. If the problem were that the app itself was waiting for the internet, the app would actually start, then pause while waiting for the connection. In this case, the app doesn't even open on the first double-click -- even if I wait for it after double-clicking on it, it never opens. I have to wait the 10 seconds or so, then double-click the icon to open it for it to even open.

Since you have other computers where this doesn't happen, something specific to your new PC is apparently not working right. Maybe someone else reading this can help.

I can tell you that I have no problem with S0 Modern Standby on either of my current computers listed below. I do make certain to power my computer(s) down before placing them in my backpack where they would undoubtedly overheat. Dell cautions me about that.

Your symptoms make me think you need to check for a Bios update & reinstall your display driver [even if the latest available driver is the same version as the one you have now].
It might be another driver but the display driver seems, to me, to be the most likely culprit.


Best of luck,
Denis

If this is a PC and you are running the latest bios, you MAY can enable s3 sleep if the manufacturer permits it. Some, like Dell, allow it on their tower PCs. I know nothing about Beelink though.
It would be worth a try.

Sorry, my PC specs changed but I hadn't updated my profile. The Beelink had S3 sleep and worked fine in this regard. I've updated my PC specs for the new PC that causes the issue. I did check for and installed the newest firmware (a minor version increase) when first setting up the PC, but the problem exists after doing so. The newest firmware still doesn't support S3 standby according to powercfg. I had updated the video drivers from the vendor's site shortly after setting up the PC so I don't think they're the cause, but I guess I could try uninstalling and re-installing them.

Update: This issue is being discussed at length in another thread: