Windows 11 Modern Standby Suppresses Remote Desktop Connection Input

Question

Windows 11 Modern Standby Suppresses Remote Desktop Connection Input

Mike Pryor 10

Modern Standby does not work well on some systems. On my ASUS FX707VI running Windows 11 Professional, Microsoft's Remote Desktop Connection fails after the interval provided for the screen to turn off in power management settings. It does not fail fully, but input is inhibited by the power management service, so keyboard/mouse input stops responding while the display continues to update. I have tracked this down through Event Viewer logs and found that the system is entering modern standby even when I have the system set up to never sleep when plugged in.

I tested several scenarios with different power options for when the screen is set to turn off. As soon as the Remote Desktop session reaches that time limit, the system inhibits input.

Power Manager has requested suppression of all input (INPUT_SUPPRESS_REQUEST=1)

Interestingly, if I set the time to a time in the past, e.g. change it from 30 minutes to 1 minute and 1 minute has elapsed in my session, Power Manager immediately suppresses input.

For the time being, I am setting both settings for the screen turning off and system sleeping to Never when I want to start a Remote Desktop Connection session. I do not want to disable Modern Standby on the system; that feels like an extreme workaround that should not be necessary. I would like Microsoft to find a better solution instead of both workarounds. Modern Standby should not activate during remote desktop sessions.

Anonymous

2025-02-14T06:58:59.1733333+00:00

Hello,

You can try it if you have a jump server.

I used to try to record video from remote desktop, but it will sleep after some time.

But when I rdp from A to a jump server B, then I create a new rdp session from B to the terminal side C, video recording never end.

If the Answer is helpful, please click "Accept Answer" and upvote it.
Leandro Lopes 0 Reputation points

2025-08-04T16:57:53.1833333+00:00

I've been having the same issue for a few months now. Searching for "RDP input stops working" somehow never returns anything. I had to setup an SSH connection to the remote host so I could reboot it every time the issue happened. After enough times i realized it didn't take long right after the reboot for input to be lost, and timing it to when my monitor sleeps was a perfect match and I managed to find this post.

The workaround is really not acceptable as the monitor needs to power down to save both power and the monitor itself.
Omer Barak 10 Reputation points

2025-09-17T16:45:48.4933333+00:00

@Leandro Lopes @Mike Pryor note this is a bug which has been acknowledged by Microsoft, currently only fixed in a preview release:

https://learn.microsoft.com/en-us/windows/release-health/resolved-issues-windows-11-24h2#remote-desktop-might-freeze-after-installing-the-january-2025-preview-update
Shaddy Baddah 5 Reputation points

2025-10-31T00:17:00.62+00:00

Can I first start by heaping praise on you. From what I can tell, you are one of the few people, at least that findable via search engine, to have conducted the same investigation I did and come to the same conclusion.

This is certainly an annoying situation. I do have a workaround, but it is far from ideal. It may help the anonymous poster, who submitted an answer.

You can install tigervnc, register the VNC server, and connect a concurrent (to RDP) VNC client connection. When the RDP session stops taking inputs, you can "wake" it up by moving the mouse in the VNC client which is connected to the console/login screen.

This is a workaround, rather than an answer. I am irked enough by the incredulity of this situation to keep exploring potential "fixes".
Shaddy Baddah 5 Reputation points

2025-11-05T08:03:55.4033333+00:00

I should expand... I don't know if it was the (unbeknownst to me) pending firmware upgrade I applied, or something else... but thankfully, I am no longer experiencing this issue at all.

I remain skeptical that this is permanently resolved, but I am a lot happier.

1 answer

Your answer

Anonymous

2025-02-14T06:58:59.1733333+00:00

Hello,

You can try it if you have a jump server.

I used to try to record video from remote desktop, but it will sleep after some time.

But when I rdp from A to a jump server B, then I create a new rdp session from B to the terminal side C, video recording never end.

If the Answer is helpful, please click "Accept Answer" and upvote it.
Leandro Lopes 0 Reputation points

2025-08-04T16:57:53.1833333+00:00

I've been having the same issue for a few months now. Searching for "RDP input stops working" somehow never returns anything. I had to setup an SSH connection to the remote host so I could reboot it every time the issue happened. After enough times i realized it didn't take long right after the reboot for input to be lost, and timing it to when my monitor sleeps was a perfect match and I managed to find this post.

The workaround is really not acceptable as the monitor needs to power down to save both power and the monitor itself.
Omer Barak 10 Reputation points

2025-09-17T16:45:48.4933333+00:00

@Leandro Lopes @Mike Pryor note this is a bug which has been acknowledged by Microsoft, currently only fixed in a preview release:

https://learn.microsoft.com/en-us/windows/release-health/resolved-issues-windows-11-24h2#remote-desktop-might-freeze-after-installing-the-january-2025-preview-update
Shaddy Baddah 5 Reputation points

2025-10-31T00:17:00.62+00:00

Can I first start by heaping praise on you. From what I can tell, you are one of the few people, at least that findable via search engine, to have conducted the same investigation I did and come to the same conclusion.

This is certainly an annoying situation. I do have a workaround, but it is far from ideal. It may help the anonymous poster, who submitted an answer.

You can install tigervnc, register the VNC server, and connect a concurrent (to RDP) VNC client connection. When the RDP session stops taking inputs, you can "wake" it up by moving the mouse in the VNC client which is connected to the console/login screen.

This is a workaround, rather than an answer. I am irked enough by the incredulity of this situation to keep exploring potential "fixes".
Shaddy Baddah 5 Reputation points

2025-11-05T08:03:55.4033333+00:00

I should expand... I don't know if it was the (unbeknownst to me) pending firmware upgrade I applied, or something else... but thankfully, I am no longer experiencing this issue at all.

I remain skeptical that this is permanently resolved, but I am a lot happier.

Answer 1

@Omer Barak I didn't see your response before, but I don't think the KBs address the same issue.

The KB describes being able to resolve by disconnecting and then reconnecting. But this issue doesn't resolve that way.

Which is why, despite my most recent posting, this has sadly returned for some reason.

If it is of any consequence, the one unusual thing I did notice is that my first attempt to RDP in after a lid close sleep, failed with an error. The next attempt went in, but the session was already frozen.

I had to apply my trick... perhaps the "suppression of all input" is sequenced in a problematic way... so if you do not RDP soon enough after resumption from a sleep, this issues occurs.

And when you try to login, the attempt by Windows terminal service to back this out fails. And the now backgrounded user session can never prevent that "suppression".

In fact, let me see if that failed first resumption RDP attempt caused terminal server to restart...

No restart that I can see, but:

"The Windows logon process has failed to connect the user session."

<Event xmlns="__http://schemas.microsoft.com/win/2004/08/events/event__">

<System> <Provider Name="Microsoft-Windows-Winlogon" Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Winlogon" /> <EventID Qualifiers="32768">4008</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-11-07T08:34:49.7686615Z" /> <EventRecordID>7478</EventRecordID> <Correlation /> <Execution ProcessID="8864" ThreadID="0" /> <Channel>Application</Channel> <Computer>pooter-msw</Computer> <Security /> </System>

<EventData> <Binary>CA080000</Binary> </EventData> </Event>

Preceded by "PowerEvent handled successfully by the service." by igcc and DellTechHub.
That's the theory I'm going with. That connecting RDP triggers the attempt to backout of... I guess modern standby. Your user session attempts to suppress modern standby, just as it would if you'd logged in at the "console".

But that fails for some reason... but your user session is now at the ready.

In fact... if I am correct, I think logging in at the console should suppress modern standby. And I should be able to go back in via RDP and avoid the freezing.

I will do that and report.

Share via

Windows 11 Modern Standby Suppresses Remote Desktop Connection Input

1 answer

Your answer