I'm not sure if this belongs here or in another forum, but I ran into an issue the other night with my laptop acting as a remote PC. This might help others have run into this issue.
The other night, I suddenly couldn't get into my laptop remotely from my office desktop machine. Since it's cold out, I wasn't too eager to run outside over and over again to ensure that everything was working. Since I was sending the images to my One Drive account so I could download them on the fly, as it were, I was at least assured that the computer was still up. However, it was disappointing to find, when I went outside, that I lost about 25 minutes of light because my mount drifted slightly without my knowledge and the target was out of center between visits to the telescope.
The symptoms of not being to get into the laptop remotely were either a black screen in the remote session, the screen saver being displayed with no interaction with the power button, or the user name spinner being stuck.
I went through the possible causes. I had just installed a WiFi extension, an additional Google WiFi node, to improve the signal to the driveway. I also suspected that the laptop processor was maxed out, although that seemed unlikely, as it worked well before and it was behaving normally when I went outside. Similarly, I thought the hard drive (SSD) had gotten to a critical storage state, affecting the Windows swap files - nope.
I did a lot of research, and there was nothing on the Windows forums I could find. Tonight, I retyped the Bing search and got the answer. I'm sorry that I can't recall the exact phrase I used, but it appears that it's related to the latest Windows 11 cumulative update released last week, version 24H2 OS Build 26100.2033, Experience Windows Feature Experience Pack 100.26100.23.0.
In the link below, Alexander R Grosstephan has a work around posted on 2/7/25 that's easy to apply. Essentially, when you change the Group Policy on the remote PC to allow only one login via TCP, Remote Desktop allows you to log in. I've tested it and it seems to work fine. The only issue is that if you login into the remote PC, forcing a disconnect on the machine that was remoted to it, you have to close the RDP session on that machine - my guess is that the remote PC sees this as multiple logins otherwise. EDIT To add: this last doesn't seem to be consistently true. I suspect it might be related to how long the remote computer waits on the connection status.
I don't know if anyone else has run into this issue, but if it helps anyone, I'm glad.
EDIT to add: I forgot to mention that this occurred both with the original "Remote Desktop Connection," which is my preferred remote tool, and "Remote Connection" from the Microsoft Store.
Here's the link: https://answers.micr...6876dc9a?page=1
Bob
Edited by UP4014Fan, 10 February 2025 - 12:29 AM.