Lately, I've been dealing with a string of black screen issues when using Remote Desktop Protocol (RDP) on Windows 11 systems. Initially, I noticed this problem around two months ago on office computers, but I've just started experiencing it myself at home, connecting from my main system to my media server. This week, the issue has popped up on even more office systems. I was wondering if anyone else has encountered this as well.
It seems linked to stale sessions—when I force log out the user from the system I'm trying to connect to, RDP works fine again. However, this workaround isn't a scalable solution. I've tried all the usual fixes for RDP problems, such as updating drivers, adjusting resolution, disabling bitmap caching, and tweaking settings in the "experience" tab. Has anyone found a real fix for this?
3 Answers
I'm noticing this in Azure Virtual Desktop with Windows Apps, but it's only affecting a small group of users. They tend to leave their laptops without logging out or disconnecting, and then they return to a black screen. Rebooting their local systems seems to help sometimes, though, it’s a bit hit or miss.
This kind of problem typically happens when the local computer goes into sleep mode, leading to that annoying black screen on the remote side. The fix? Just disable sleep mode on your local computers, and it should prevent these issues.
I'm having that issue too! It's strange because this started out of nowhere in November. If it was a sleep issue, why didn't it happen before?
That doesn't line up with my experience either. I’ve been using RDP for years and never had to tweak anything like that.
Yeah, I've run into this several times lately! It's always on different systems, and it's definitely not a sleep mode issue since our systems only turn off the display. If they really were going to sleep, RDP wouldn't connect at all. So frustrating!
Same here, just the monitors turning off, no sleep mode. Really odd!
Sounds similar to what I see! In our case, this is purely workstation to workstation. A reboot on the local end doesn't help. It's really only an issue when trying to reconnect to a logged-in user’s session.