![]() Lack of RAM or disk space on the RDSH server.An issue with a user profile or profsvc service.An error in the operation of the Remote Desktop Services.The error may appear for a number of reasons as given below: Sometimes users cannot connect to RDS Windows Server using the built-in RDP client (mstsc.exe) with the following error: What causes the error remote desktop services is currently busy? Let us today discuss the possible causes and fixes for this error. I deleted all non Windows standard fonts (my company had a policy to add some corporate fonts) from registry hive "HKLM\software\microsoft\windows nt\currentversion\fonts" and it started working inmediately.Įven if the cause of registry corruption may be different for different users, procmon showed me what was wrong.Users often receive the error message “remote desktop services is currently busy” while connecting to a Windows server using RDP.Īs a part of our Server Management Services, we help our Customers with Windows related errors regularly. So I've examined a server with process monitor (procmon.exe) and noticed a lot of overflow errors related to registry "HKLM\software\microsoft\windows nt\currentversion\fonts". Only chance to get them back to normal was to overwrite the C:\WINDOWS\SYSTEM32\CONFIG\SOFTWARE registry from backup C:\WINDOWS\SYSTEM32\CONFIG\REGBACK\SOFTWARE (server has to be powered off), but that not always worked. Server works OK, services run normally and can connect remotely with powershell and WindowsAdminCentre and my usual remote tools. ![]() No way to get into safe mode: always black. VMware console is black, RDP connection is black and it even happened with a physical server (but only domain joined servers). I had a similar problem with Windows Servers (a mix from 2012 to 2019):
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |