Microsoft's Security Patch on Tuesday is causing the problems for machines that don't have automatic Windows Updates. The function requested is not supported. In the article above, there's a link to those files from a patched Windows 2012 R2 server which should work. That's why the first thing you would do would be either changing the group policy or the registry in order to workaround the issue and proceed with your operations. I have lower the security of my station just to connect to that server. Solution 1: Install updates on the target computer The first and the most recommended solution to this issue is to update the target computer on which you are trying to connect remotely.
How can I regain access to my server? Solution 3: Using Registry Editor The same thing can be achieved through Windows Registry. If you aren't comfortable using the command line to install updates, you can simply edit the local group policy on your computer until the updates can be deployed. Microsoft security policies are geared towards maximum security of data transmissions assuming they cross the insecure public internet so they necessarily must configure for every possible known security vulnerability. You should patch the server or ask the server's administrator to patch it. If so, then the threat is at which level? In my user's case, the issue was resolved by updating Windows 10 to the most current version 16299. The server is running Windows Server 2012 R2 Standard, the client is running Windows 10 Pro. Once you have access you should apply the solution below and remove the workaround.
Windows Server 2016: I strongly suggest not to compromise the server-side security, but mitigate it from client Windows temporarily. I've updated my blog post with the information shared here about editing Group Policy and setting it to Vulnerable. Remote Desktop Connection An authentication error has occurred. By default, after this update is installed, patched clients cannot communicate with unpatched servers. The Group Policy setting you need is Encryption Oracle Remediation. However, your way of thinking about it is very brilliant for Workgroup computers.
I have windows 7 installed on the remote pc. Go to and check for updates. I am new to my position and after attempting your fix I found that my server has not been updated since May 2016 and that I don't even have that Group Policy setting available. Issue does not affect those using remote desktop services to access servers on 2016. Developer environment is always as per the projects requirement. In my case for workarounds I suggested to rdp to an un-patched client that was offline and use it as a jumpbox to rdp to the un-patched hosts, lucky that in my case the hosts to patch were really infinitely small percentage.
An authentication error has occurred. To add to what Chdwck wrote, you will probably need to login to those remote servers to get the update installed. Else, here are the steps to do the same thing below : 1. Now I'm fine as your solution fix the issue. Can you help me with that so that I can resume my work? Is there a patch being worked on? Based on other conversations this has happened in the past. You can read - for more information on the Group Policy and registry key.
In Windows 7, this option is called differently. I think I have fixed the issue for me, so let me tell you what I did as it may help others. You should patch the server-side or ask server administrator to patch it. If both systems were patched then this error would not occur. For more information, see the Microsoft article.
An unfortunate Windows10 update issue yet again. Changing the setting to Vulnerable will allow you to connect to unpatched servers. This issue is only affecting those on Windows Version 1803. All the databases were running fine and we could use them. Currently, Windows 10 doesn't support. Note This setting should not be deployed until all remote hosts support the newest version.
Machine has to be rebuilt as per the allocated projects development environment which consumes time for both person waiting to get started for that project and support person who ensures system readiness. I am using Windows 7 Ultimate and Windows 10 Pro. Hi Luke, It seems your correct. For more information, see An authentication error has occurred. Solution 1: Apply Patch Patch the Remote Desktop gateway and host servers themselves and performing a reboot. However, there are many situations such as development, testing, build, staging, and deployment environments which require a stable environment that would be destroyed by automatic Windows updates. If both server and client are patched, nothing is needed.
I had the same issue. When trying to connect to a server or machine via Remote Desktop Connection you will get the below error which is strange as one would normally connect without any issues. A user allocated to the project can immediately continue with his work. This error could be caused by the user account used in publish profile with could have sysadmin privileges. Removing these updates and rebooting will restore functionality, but is not recommended. Thanks for the informative post. They can change the check box on the Remote Desktop dialog.
Reproduction without explicit permission is prohibited. I don't know if a patched client is allowed to connect to an unpatched server or not. Very irresponsible of the patch team. This security update breaks Remote Desktop connections to Server 2016 and 2012R2 when using the Remote Desktop Gateway role. The function requested is not supported I tried several things I found by googling, for example adding extra SecurityPackages values to the registry as described here: but that didn't work. Since the Microsoft Security Patch on Tuesday, we've received many reports of users having connection problems like this: An authentication error has occurred.