![]() ![]() You can easily confirm this: simply create a new value in one key and you will also see it in the other. The keys HKU\.DEFAULT and HKU\S-1-5-18 are the same. The registry key HKU\.DEFAULT belongs to the Local System account (SID S-1-5-18) and points to the registry key HKU\S-1-5-18. More importantly, the path is HKU\.Default, which contains the registry settings for the Local System account (the lock screen runs under the Local System account). Now, you may wonder how it is possible that standard users are able to delete registry keys that are located in the HKEY_Users hive. In case you have separate Group Policies for administrators and users you will have to include the removal of the aforementioned registry keys in multiple Group Policies. The easiest way to make sure that the Group Policy is applied to both users and administrators is to set the scope to Authenticated Users. ![]() Therefore, this Group Policy should be applied to all logons. This applies to both standard users as well as administrators. ![]() The reason for this is that these keys are recreated at each logon. You can remove these keys using a Microsoft Group Policy Preference (or you can use Workspace Environment Manager or another product).Īs you can see in the screenshot, the keys are removed in the User Configuration section instead of Computer Configuration. I also strongly suggest that you test this solution before implementing it in production. Although I am not aware of any negative impact, removing these registry keys is at your own risk. This method is NOT supported by Microsoft. HKU\.DEFAULT\Control Panel\International\User Profile System Backup.HKU\.DEFAULT\Control Panel\International\User Profile.The workaround to solve this issue is to remove the following two registry keys: The solution (or workaround to be more precise) All I have is a workaround which seems to do the trick. I even opened a case with Microsoft concerning this issue, but so far it did not lead to any solution. This issue is reported on the Internet here and there. In the solution below we modify settings that belong to the Local System account to solve this issue. Also, the lock screen runs in the context of the Local System account (as opposed to the active session that runs in the user's own context). What is sure though is that it can only happen when multiple languages and/or language packs are in play. The exact cause for this issue is unknown to me. However, as soon as the screen is locked, the keyboard language changes to another language (for example English).The keyboard language in the active session is correct (for example German):.You start an RDP or ICA session as an administrator or user.Note: for other keyboard related issues please see the article Solving keyboard layout issues in an ICA or RDP session on this website. It may apply to other operating systems as well. This information is intended for Windows Server 2016 and RDP and ICA sessions. In this article I present a simple solution to prevent that the keyboard layout changes unexpectedly on the Windows lock screen. ![]()
0 Comments
Leave a Reply. |