Skip to main content
A black RDP screen can have several causes. First check whether the Windows desktop is visible through the EDBB VNC console. That helps separate a guest login/display problem from an RDP client or transport issue.

​
Start with reversible checks

  1. Record the Windows Server and RDP client versions and whether the problem affects one or all users.
  2. Disconnect and reconnect the RDP client. Signing out is different: it closes that user’s applications, so save work first.
  3. Test a current supported client and check available server disk space and Windows event logs from the console.
  4. If the console is also blank or the server is unresponsive, investigate the guest before changing the client registry.

​
Test TCP-only transport on a Windows client

This optional diagnostic applies to the Windows computer running the RDP client, not the remote server. It disables UDP for that client’s Remote Desktop connections. Record the existing value before changing it, and use an elevated terminal.
If the value already exists, save its previous type/value so you can restore it. If your organization manages this policy, consult its administrator instead of overriding it.
Close all RDP client windows and open a new connection. Check whether the symptom changes; this is not a universal black-screen fix.

​
Revert the diagnostic

Restore the previous value if one existed. If the value was absent before the test, remove only the value you added:
Reopen the client and test again. Contact support@edbb.com with your console observations and timestamps if the issue appears to involve the VPS infrastructure.