![]() ![]() Also, I feel like after a restart, it connects just fine the first time around - the second time, it fails to connect with 0x10b with the exact symptoms youre describing. I can connect to my remote session fine (Windows 10, still on 1803 due to corporate antivirus). 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. connecting from a Mac via MS Remote Desktop client. I just upgraded to the new Microsoft Remote Desktop 10.4.0 (1811) that came out a few days ago. If I try remoting into this machine, it connects to a black screen, sits there for 2-3 seconds and then promptly disconnects. Yesterday I noticed one of the servers was having an issue with its remote desktop connection. 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". These servers are used for testing, and are members of a domain which has two DCs, each of which are running DNS Server. 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. The office desktop screen now also 'refreshes' or flickers every 10 seconds. Just the other day, I try to RDP and I am presented with a black screen, and then am disconnected after a very short while. Server works OK, services run normally and can connect remotely with powershell and WindowsAdminCentre and my usual remote tools. I have been using RDP from home to access my office desktop computer for many months. 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). When you take a screenshot and want to paste this you only see a black screen. Then enable Use the hardware default graphics adapter for all Remote Desktop Services sessions. Microsoft Remote Desktop version Version 10.7.1 (1942). I had a similar problem with Windows Servers (a mix from 2012 to 2019): Local Computer Polic圜omputer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostRemote Session Environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |