Microsoft Windows 10 May 2018 Update caused Remote Desktop not saving credentials.

Stop users from installing chrome extensions
October 8, 2019
Remote Desktop Server – License Setup
February 6, 2020

Microsoft Windows 10 May 2018 Update caused Remote Desktop not saving credentials.

Hello,

after recent Microsoft Update (which may be related to this: httpss://support.microsoft.com/en-us/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018 ) users in my network reported me that any Remote Desktop credentials were erased.

Even when you configure and save it to a desktop it requires to input login and password every time you try to log in. I’m not sure if this happens to anyone else, however I found a solution / workaround to this problem – I’ll post it below – it might help someone. It requires to edit gpedit.msc configuration as Administrator. 

  1. Click Start and type “GPEDIT.MSC” to search for the shortcut to the Windows Group Policy Editor.
  2. Right-click the gpedit.msc shortcut and click run as Administrator.
    (Ignore any popups about errors if you get any when the Group Policy Editor console opens up).
  3. Browse to Local Computer Policy > Computer Configuration > Administrative Temples > System > Credentials Delegation
Image
  1. Double click the setting called “Allow delegating default credentials with NTLM-only server authentication” to edit it.
  2. Change the setting to “Enabled” and then click the “Show…” button in the “Options:” window where it says “Add servers to the list:”.
Image

  1. Double click the field below “Value” (with the black arrow to the left) and type in “TERMSRV/*” (without the double quotes).
Image

  1. Click Ok and then Ok again to close both popups, so that you only see the list of settings again.
  2. Now just repeat the exact same for these three policies as well:
    Allow delegating default credentials
    Allow delegating saved credentials
    Allow delegating saved credentials with NTLM-only server authentication
  3. Close the Local Group Policy Editor and RDP should now work as expected again!