Server 2022 RDS - Disconnected User reconnect to BlackScreen

Mark Lacey 26

Hello,

We are currently having an issue with an RDS 2022 Server.

Users log into a blackscreen after reconnecting to a disconnected session.

You are unable to log these users off without terminating LogonUI.exe, additionally if a user is idle on the blackscreen you can manually terminate LogonUI.exe and the users remote session will load up like normal.

Any support would be appreciated.

Thanks

Tim Collier 1 Reputation point

2022-12-08T03:03:32.877+00:00

I have built a number of RDS environments on RDS 2022 running on Hyper-v 2019.

I have this same issue where it always logs in fine but if the session goes idle and they return to it the get the black screen and you have to kill their processes and log them out and they log in and its ok again.

They also use FSlogix profile containers.

Importantly this happens about 1 in 20 times they return from an idle session and from a variety of clients, users and host servers. Logs show nothing unusual when it occurs.
Teun 0 Reputation points

2023-02-04T08:34:11.0933333+00:00

I am having the same issues, brand new Server 2022 installation in VM-Ware with just basic settings. Not using FSLogix or any profile redirections.

The issue appears to be more frequent when I set an idle time limit in the RDP Gateway policies however even without setting any limits users are reporting issues when they try to reconnect a disconnected session.

Only fix when this happens is to kill the Windows logon user interface host process in task manager for the specific user. Sometimes even twice.

If I set an idle time limit I sometimes get the message "Please wait" when the the limit is reached. Nothing will happen you can wait for hours.

Also, when I have a RDP session open full screen it will usually stay on for quite some time without issues but if I minimize the RDP window within 5 minutes the session will crash into black screen or "Please wait" bluescreen.

These issues are causing a lot of headaches I have spent hours trying to troubleshoot this. Can't even find any usefull entries in the event log...

After spending another day trying to resolve this (even removing our managed services N-able and SentinelOne antivirus without any luck) I am now installing Server 2019 next to the 2022 server in the same domain to check if the issue is the same.
Thomas Billen 5 Reputation points

2023-02-17T18:01:57.83+00:00

We have the exact same thing as Teun discribes, black screen hanging sessions, search and taskmanager are suspended. We can only kill the session by killing user interface host. It pops up randomly, we even had it on a FS with an admin account and no fslogix or other trickery. It seems to be a straight up windows 2022 bug as we are currently having this issue with 3 of our customers all on 2022. The sad this is that I have been searching for a solution for our customers for days, looking into all sorts of logs, trying all things. But I cannot find a trace or log why it happens. Tho I highly suspect the “app readiness” service to have something to do with it. Disabling it causes some

problems like start menu, search and outlook do not work properly. As for now, no patch seems to have fixed it and no reason or solution to be found :( if anyone has the key to solving this..
Ben Jones 0 Reputation points

2023-03-10T15:38:41.3266667+00:00
I am having this same issue for a new Windows Server 2022 Standard (10.0.20348 Build 20348) that has Remote Desktop Services configured. When a user reconnects to a disconnected RDP session they get a black screen that doesn't respond to anything. This happens even if I logon to a new RDP session, disconnect, and immediately try to reconnect. The only way to fix this session is to end the task for that user for "Windows Logon User Interface Host" and then they can get back in. I don't even have to sign off the user and if they are connected and looking at the blank screen when I end that task then it clears up while they are still connected. I confirmed that if they sign out properly this isn't an issue.

I have tried snoozing my Managed AV

I have tried removing N-Able Take Control

I have tried multiple users from multiple devices
Peter 0 Reputation points

2023-05-23T11:56:10.4233333+00:00

Same issue here. The only thing is that I don't know which LogonUI.exe that's associated with which user? The LogonUI.exe runs as SYSTEM (and I have around 10 of them).How do I connect "Windows Logon User Interface Host" to a specific user?
Teun Pleunis 0 Reputation points

2023-06-22T06:11:16.0566667+00:00

I just wanted to add that since I reinstalled Server 2019 (after my last post Feb 4, 2023) I had zero issues with this server. So it is 100% a server 2022 issue. I see some posts that it is resolved after removing N-able but for me this was not the case. Shocking to see there are recent posts showing this has still not been fixed.
Neil D 0 Reputation points

2023-12-06T01:08:22.12+00:00

I am having the same issue. RDP to a remote pc via Remote desktop Gateway which is a 2019 datacenter server. When diconnecting/logoff from the remote machine, the RDP client goes to a black screen and will not disconnect or close. when checking the remote machine and the RDG server the sessions have been ended. so it appears that when the user logs off the remote machine the RD client doesnt disconnect properly and hangs with a black screen. Tried building a brand new server using 2019 datacenter but the same issue. Tried Remote Desktop client from multiple machines, same issue. RD Client on Win10, Win11, Server2016, Server2019 all the same. Tried multiple devices to RDP into as well.

10 answers

Limitless Technology 39,351 Reputation points

2022-10-07T14:40:07.757+00:00

Hello there,

A few things I would suggest you try first:

-Does the user just have a bad session on the RDS server? If so, try to force log off the user on the RDS server and have them retry RDP. They could just be disconnecting and reconnecting to the same bad session.
-Can this user use another machine and RDP to the RDS server okay? This will help narrow down if it is the user account or the Windows 10 machine that is the issue. I have run into weird issues with user accounts in the past that had loop-back GPOs applied to their account that messed up RDS sessions.
-If you log into that Windows machine with a different user, can that different user on that same Windows machine RDP just fine? That will help narrow down if it is just the user profile on the Windows machine that is the issue or the entire Windows machine.

Try turning off Fast Startup
-This feature only works when you do a shutdown and then Boot. It doesn't effect a restart.
-Go to the Control panel, Power Options, and select Choose What the Power Buttons Do on the left.
-Then select Change Settings That are Currently Unavailable near the top center of the screen.
-Lower down on the window, and uncheck Fast Startup.

---------------------------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept it as an answer–
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
William Magargle 1 Reputation point

2022-10-30T14:16:45.913+00:00

Hi, we are seeing the same behavior with a 2022 RDS server and have not found a solution. Have you been able to resolve this?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Paul van Dijk 1 Reputation point

2022-12-01T06:39:34.593+00:00

Hi,

I've experienced the same issue. The annoying part is also when you want to log off a user, you first have to end tasks in the users' container.
The only thing I've configured before this happened is a GPO to log off disconnected users after 30 minutes.

Currently I've turned this GPO off and waiting for the effects. Will let you know.
Please sign in to rate this answer.
Tim Collier 1 Reputation point

2022-12-08T03:04:28.67+00:00

Paul i commented earlier but my solutions are doing the exact same behavior. Any luck as yet?
Sign in to comment
Karel van der Linden 1 Reputation point

2022-12-08T10:31:08.61+00:00

Hi,

We have experienced the same issue. I recreated some server with the latest ISO from eopen but still no luck.
Someone found a solutions ?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Thomas HUBERT 0 Reputation points

2023-02-21T12:53:21.5233333+00:00

Same problem here !
Fresh new 2022 VMs, all have the same issue...
Some users are even more affected than others.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment