Skip to main content
Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • This worked. I also had to add my non-admin user to the group with net localgroup "Remote Desktop Users" [username] /add. Also, I had previously created a group with net localgroup "Remote Desktop Users" /add, and I was unable to login before deleting that local group. Commented Oct 3, 2016 at 0:15
  • 1
    This approach works with 2 tricks from the answer below: 1) run the registry editor with SYSTEM privileges (use PsExec.exe -s -i regedit.exe or tweak the permissions); 2) add the users to "Remote Desktop Users", which becomes available after you import the registry fragment. Commented Jan 11, 2019 at 19:33
  • 1
    tested on Windows 10 home 32 bits in a Atom [email protected] with ony 2GB of memory (Microsoft Windows [Version 10.0.17763.914])... works like a charm! THX!!! Commented Jan 7, 2020 at 20:10
  • My 2cts are... if you have already a "Remote Desktop Users" group then remove it... only then apply the above fixes... and then check if a new "Remote Desktop Users" group is created... don't forget to add the non-admin user to this group! Commented Jan 7, 2020 at 20:12