Ah security, the balance between not allowing access at all and allowing too much access.
In Windows 10 Microsoft changed RDP’s defaults. They modified the default for “SecurityLayer” from 0 to 2. Even if you go into the user interface and disable: “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” Still doesn’t change that value to a 2.
- Open RegEdit
- Navigate to this Key:
- Change “SecurityLayer” to a zero
- Reboot and done!
18 Replies to “Fix | Windows 10, “the connection cannot proceed because authentication is not enabled””
Has there been a Microsoft kb update for this yet for windows 10?
not that I am aware of sorry.
Well, that’s obscure. Thanks for sharing!
worked like a charm! thanks!
No reboot was necessary (at least in my case)
Works great! Hope they fix this in the next Windows 10 role-out.
awesome!that worked ..Is there any way to follow or Do you have a blog?
Thanks for this fix! Now able to login to a windows 10 desktop!
No reboot neccesary, and at least in my case I only had to change it to 1. Not sure what the different levels mean but 1 sounds better than 0.
0 sets it to RDP Security Layer
1 sets it to Negotiate
2 sets it to SSL (TLS 1.0)
I believe (but haven’t tried) that it can also be set using group policy at Computer Configuration -> Policies -> Administrative templates -> Windows Components -> Terminal Services -> Terminal Server -> Security
Probably can be set is Remote Desktop Services Configuration on a server.
This fix also works with Windows Server 2016, thanks for sharing.
Amateur here….I got all the way to the security, but don’t see what I’m suppose to change to 2?
Right click on Security Layer listing in the right window pane and edit/modify
Thank you!!!!! I could RDP in our office but not through our Remote Access using a Barracuda appliance. This solved the issue!
Brilliant works like a charm !
thank a lot, save me from horizon View 5 issues
Not working for Windows 7 Embedded Standard 32-bit