There’s a weird obscure bug in M$ Remote Desktop in Windows 11 Pro I spent entirely too much time trying to track down, as a user. (Yes, the first mistake was ever getting near Windows, but anyway.)
It looks like there is some kind of counter that now exists in number of logged in sessions, and each RDP session counts as a one-time-use session. The local user does too.
If you log in locally on first boot, there’s a 25% chance you’ll be able to log in remotely from one machine once or twice.
If you log in as a remote user from boot, you’re more free to log in remotely, possibly from two different machines about 75% of the time, but if you just use one other machine, pretty much forever.
Rebooting always solves the login issues, so much so that a terrible terrible workaround was employed. Enable OpenSSH server (now included in Windows) on Windows, to SSH into the box (which, reliably works every time no matter what) and reboot it.
So many Internets on the topics, including using their old RDP driver, that the new driver may be cranky, that the host graphics drivers may have an impact, that the BIOS OOB management may have an effect. Nothing ever fixed it consistently.
Thankfully, my life means too much to me to go further down the rabbit hole and I don’t have to use Windows as much anymore, and hopefully soon never, but…its like they took a whole team of engineers to break something that has worked amazing since the early aughts and just firehosed pigeon turds all over it.
They obviously care enough to keep it working as they renamed the RDP app to “Windows App” in the last year, but don’t care enough to make it work correctly?
Hm sounds like the bug is in the code that handles the “one session only” rule
Per Microshits T&Cs you can only have 1 session of any kind at a time unless you get the super special business multi seat RDP license (because ofc)
I actually have a Powershell script I found awhile back that patches the RDP DLL so it stops caring about multiple sessions
I spent entirely too much time trying to track down
Been there, if you have the audacity to force your way into the WindowsApps folder you’ll bork the permissions systems so bad that every single post about how to fix it ends in “just reinstall” me being me that was an unacceptable answer.
Took me a week to fix it so the MS store would launch again. On the flip side, I have a whole new understanding of the permissions system on windows. Heh
There’s a weird obscure bug in M$ Remote Desktop in Windows 11 Pro I spent entirely too much time trying to track down, as a user. (Yes, the first mistake was ever getting near Windows, but anyway.)
It looks like there is some kind of counter that now exists in number of logged in sessions, and each RDP session counts as a one-time-use session. The local user does too.
Thankfully, my life means too much to me to go further down the rabbit hole and I don’t have to use Windows as much anymore, and hopefully soon never, but…its like they took a whole team of engineers to break something that has worked amazing since the early aughts and just firehosed pigeon turds all over it.
They obviously care enough to keep it working as they renamed the RDP app to “Windows App” in the last year, but don’t care enough to make it work correctly?
Hm sounds like the bug is in the code that handles the “one session only” rule
Per Microshits T&Cs you can only have 1 session of any kind at a time unless you get the super special business multi seat RDP license (because ofc)
I actually have a Powershell script I found awhile back that patches the RDP DLL so it stops caring about multiple sessions
Been there, if you have the audacity to force your way into the WindowsApps folder you’ll bork the permissions systems so bad that every single post about how to fix it ends in “just reinstall” me being me that was an unacceptable answer.
Took me a week to fix it so the MS store would launch again. On the flip side, I have a whole new understanding of the permissions system on windows. Heh