Editing the registry incorrectly can cause serious problems that may require you to reinstall your operating system.Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Be sure to back up the registry before you edit it.Once the settings are saved, subsequent user logins will not need the elevated privilege to see the BGInfo background.Bg Info can help anyone who needs to keep track of a lot of systems -- physical or virtual.The server did restart with the Windows update cycle a couple of days ago.
When you execute BGInfo for the first time, it displays the window that Figure 1 shows.On a more in-depth level, I am curious if anyone knows why BGInfo must open the "default desktop registry key" and what it is updating in the "logon desktop settings" (phrase in quotes taken from the original error message)? This seemed to then allow me to apply the settings without the Default Desktop registry key error.BGInfo needs to update the registry to set a default login desktop for all RDP users.BGI configuration file (versus reading settings from the Registry).Thoughts on why the error happens for user other than the Administrator? Go to Compatibility tab and check the Run this program as an administrator.It's unlikely that the attribute is not updated, there might be a name resolution conflict for example, and one server does have uptime over 250 days, and those servers you test are unreachable by RPC.