RDP Black Screen Windows Server 2016 to Windows Server 2022

Question

I'm using a Windows Server 2016 to RDP to a Remote Server that is using Windows Server 2022.

Randomly, after numerous session to the remote server, the RDP session goes to a black screen.

Crtl =+ alt + end, doesn't work.

I have a GPO applied that limits the quantity of sessions to 1 and to limit the idle time to 1 minute. I have checked this in CMD to make sure the sessions are closing correctly and they are.

I have tried restarting both host and remote servers Remote Desktop Services and the session still goes to a black screen.

I have applied a GPO that only allows TCP connection for RDP sessions.

I have disable Bitmap Caching and fast startup.

I have ran a constant ping whilst opening and closing RDP sessions to the point of failure to see if there is a network issue and there isn't.

The screen resolutions are fixed and can not be changed.

A reboot of the remote server cures the issue, however this is not practical.

Any help would be appreciated.

Thanks,

Ollie

Answer 1

Hello,

There can be many different reasons for a black screen, we first need to check in the event viewer to narrow down some possibilities. Review the event logs on both the client (Server 2016) and the remote server (Server 2022) for any errors or warnings that might indicate what's causing the black screen. Pay particular attention to the System and Application logs.

Some examples are:

• Winlogon terminating -> Look for error event ID 4005 on "Application" event log (from source event log "Microsoft-Windows-Winlogon")
• Explorer crashing -> Look for error event ID 1000 in the "Application" event log

Try using a different RDP client, such as the Microsoft Remote Desktop app for Windows, to see if the issue persists. This can help determine if the problem is specific to the built-in RDP client.

I hope this information helps.

Best regards,

Karlie Weng

Answer 2

Hello,

Thank you for the above. I have tried the following on both local and remote:

• Winlogon terminating -> Look for error event ID 4005 on "Application" event log (from source event log "Microsoft-Windows-Winlogon")
• Explorer crashing -> Look for error event ID 1000 in the "Application" event log

Neither servers show any event to suggest that Explorer or Winlogon crashed or terminated.

Unfortunately I am strictly to use the built in RDP as per customer requirements.

If you have any more suggestion or areas for me to look into, it would be greatly appreciated.

Thanks,

Ollie.

Answer 3

Hello,

Are there any other crash logs in Event Viewer, especially under the Application and System logs during the time the issue occurred?