Now we can connect by opening Anydesk program. If the service status shows as Stopped, click the Start button below.Īfter this process, the service status will be seen as running.Select the startup type Automatically and click the Apply button.AnyDesk Service Properties will open on the screen that appears.On the services screen that opens, we find the AnyDesk Service service and double-click it.
In the Start search screen, type Services and open it. In order to solve the Anydesk white screen problem, we need to start the service called AnyDesk Service, as we said above. In order to fix such errors, we will need to start the service called Anydesk Service. The general reason for this error is the AnyDesk Service, which is in the services of the Anydesk program, due to the stopping of the services service. Why Am I Getting Anydesk White Screen Issue?Īs we saw above, after opening the Anydesk program, we encounter a gray or white screen problem. You can change this setting at anytime if youd like the black screen to. If you are encountering such an error, we will learn why we encountered the white screen problem in the following article and how to get rid of this error. You can connect your phone to your computer and control it remotely, wire free. The white screen problem encountered by users using the Anydesk application when opening the application does not react in any way and does not show the main menu. 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.Nomber_key:001014 Hello, Im fairly new to the Linux scene and having an issue where after trying to install Teamviewer on RHEL7 Workstation, Im now left with a mouse cursor. 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 kommentar(er)
