This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 60%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAO%3C/text%3E%3C/svg%3E)
Problem: - Users report RDS session crashes usually but not always where the screen will go black leaving the only option to X out of the RDS banner. When trying to re-connect it will briefly allow login then immediately the session will drop and they will be back to the local desktop.
Environment:
RD Session Hosts (Windows Server 2016) x 4
RD Broker (Windows Server 2016)
Fslogix profile disks with redirected desktops (Windows Server 2022 - SSD array)
Office version - 365 MSO (Version 2206 Build 16.0.15330.20260)
Users - 60
Frequency of session crash - 1-3 per day on average. Sometimes same user is affected more than once. It occurs to people working from home and in the office.
Actions tried:
Removed Sentinel 1 EDR
Group policy for Session keep-alive
Disabled WIndows Firewall
Disabled Windows Defender
Fully Updated Hosts with Manfacturer drivers/firmware and Windows Updated
Removed RMM Remote Access Tool
Microsoft Incident - Got to requesting a clean boot on a server then stopped as that would render a production host unusable
Updated FSLogix
How long has it been happening - It has become more frequent since the profile disk was migrated servers in late April 2022 from a now redundant WS2016 server to a newer and faster WS2022 server. It had happened infrequently before then however.
I have tried investigating event logs on RD session HOst and Broker and while there are some errors such as ESENT 492, 416, 482. I haven't been able to track down the root cause. We get limite d opportunity to investigate as the users connect to the session for all their work.
Looking for further help
I asked a user with a crashed session and found these are logged in the Microsoft - Windows Terminal Services - Local Session Manager log - Operational logs
Event ID: 36
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer:
Description:
An error occurred when transitioning from DisconnectedLoggedOn in response to EvConnected. (ErrorCode 0x80070005)
Event ID: 36
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer:
Description:
An error occurred when transitioning from Disconnected in response to EvConnected. (ErrorCode 0x8000FFFF)
----
The reason code for the disconnect was as shown
Session 115 has been disconnected, reason code 5
This translates to:
Extended Reason: Your Remote Desktop Services session has ended. Another user connected to the remote computer, so your connection was lost. Try connecting again, or contact your network administrator or technical support group
Just to keep this up to date.
Since we started logging instances of crashes on 30-June it has occurred over each of the four RDS servers and affected 20 of 62 possible users on at least 43 occassions.
The errors posted on 02-Aug seem to be the most relevant when the issue occurs?
Still at a loss as to the root cause. Going to look at physical networking in the coming days to see of moving Host connections to a different switch helps.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 19%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
Can you check if you have KB5015808 installed? There are some major RDS issues with that patch: https://borncity.com/win/2022/08/17/rds-probleme-nach-windows-update-kb5015808/#:~:text=RDS%20problems%20after%20update
Thanks for the article, we're not affected by that patch but I do suspect Server 2016 has flaws. We are considering building a new 2019 server, installing apps and only letting the affected users use that server to test
Still not found a resolution to this issue.
The latest is we have built a 2019 RDS server and will expand the number of users that use it day-to-day and see if the issue persists.
We ended up building a new set of four RD Session hosts (a sysprep image of one new server and duplicated three more times) to replace the affected 2016 Servers. It's been two months since doing this and daily occurances have stopped
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 13%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKV%3C/text%3E%3C/svg%3E)
Many thanks for the feedback but reinstalling servers is not really a solution.. I'm in the same situation (RDS 2016 starting having the same error). Will tryu to find the root cause
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 52%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERC%3C/text%3E%3C/svg%3E)
Having same issue
Running FSLogix with redirected folder as well