Sign in
 

none
Remote Desktop Authentication Error Has Occurred. The function requested is not supported.

 > 

    Question

  • Question
    Sign in to vote
    22
    Sign in to vote

    Since the Microsoft Security Patch on Tuesday, we've received many reports of users having connection problems like this:

    An authentication error has occurred.
The function requested is not supported

Remote computer: <computer name="">
This could be due to CredSSP encryption oracle remediation.
For more information, see https:/go.microsoft.com/fwlink/?linkid=866660

    The error impacts:

    • Remote Desktop Connection
    • Remote Desktop Connecting to Azure VMs
    • VPN Network Connections (before one can even try to use Remote Desktop)

    This is quite a mess and seems to be related to the security patch increasing security requirements, but not implementing the change to give the machine the increased security levels. The latter doesn't seem to occur if the machine has automated Windows Updates turned off.

    Unfortunately, Windows Update can't be automated in many environments such as development, build, test, staging and production without creating other problems.

    Wrote a blog post about our findings so far with a workaround on how to reduce Remote Desktop security settings to get around this problem. It doesn't require touching registry settings or other complicated steps:

    Remote Desktop Authentication Error Has Occurred. The function requested is not supported. CredSSP

    Would appreciate any insight on handling this across an enterprise without manually modifying the connecting and host machines.

    A common scenario is a person working from home not being able to connect to their own computer in the office or a VM.

    Thanks.

    Luke Chung
    Microsoft MVP
    President of FMS, Inc.
    Blog Facebook Twitter


    Friday, May 11, 2018 12:50 PM
    |

Answers

  • Question
    Sign in to vote
    133
    Sign in to vote

    Here is the FIX for this issue ..

    --> Change the Group Policy on your local client to use the vulnerable setting 

    Run:  gpedit.msc

    Go to à Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Encryption Oracle Remediation

    Open - Encryption Oracle Remediation à  choose Enable  à change protection level àVulnerable à Apply

    Thanks and Regards,

    Regu

    • Proposed as answer by vor0nwe Wednesday, May 16, 2018 10:22 AM
    • Marked as answer by LukeChungMVP Thursday, May 24, 2018 6:29 PM
    Monday, May 14, 2018 1:40 PM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you!!!
    Friday, May 11, 2018 8:25 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    You're welcome. What was your situation?

    Luke Chung
    Microsoft MVP
    President of FMS, Inc.
    Blog Facebook Twitter

    • Proposed as answer by kk92009 Tuesday, May 15, 2018 2:37 AM
    Saturday, May 12, 2018 12:21 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote
    Good information, but unfortunately my home PC is running the HOME version of Windows 10 and the RDP settings window does not offer the options shown in the workaround link.
    Sunday, May 13, 2018 2:23 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you for sharing.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, May 14, 2018 5:41 AM
    |
  • Question
    Sign in to vote
    20
    Sign in to vote

    Have this issue as well in our environment.  Typical untested patch that makes a headache for large groups of people.  Very irresponsible of the patch team.

    Remove the tick from the "Allow connections only from computers running Remote Desktop with Network Level Authentication" got us working again

    Windows Desktop Client to Server 2012 R2

    • Proposed as answer by thomfl Wednesday, May 30, 2018 4:23 PM
    Monday, May 14, 2018 7:13 AM
    |
  • Question
    Sign in to vote
    2
    Sign in to vote

    Or you can just uninstall update KB4103725 
    https://support.microsoft.com/bg-bg/help/4103725/windows-81-update-kb4103725

    worked for me

    Monday, May 14, 2018 9:43 AM
    |
  • Question
    Sign in to vote
    2
    Sign in to vote

    Thanks for sharing..

    it works with me after following this instruction https://blogs.technet.microsoft.com/mckittrick/unable-to-rdp-to-virtual-machine-credssp-encryption-oracle-remediation/

    we have big headache after KB4103725 patched get installed on clients win8. so should i update the kb4103725 on RDP host server 2012 r2 as well or wait for any further security kb? 

    Monday, May 14, 2018 12:06 PM
    |
  • Question
    Sign in to vote
    133
    Sign in to vote

    Here is the FIX for this issue ..

    --> Change the Group Policy on your local client to use the vulnerable setting 

    Run:  gpedit.msc

    Go to à Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Encryption Oracle Remediation

    Open - Encryption Oracle Remediation à  choose Enable  à change protection level àVulnerable à Apply

    Thanks and Regards,

    Regu

    • Proposed as answer by vor0nwe Wednesday, May 16, 2018 10:22 AM
    • Marked as answer by LukeChungMVP Thursday, May 24, 2018 6:29 PM
    Monday, May 14, 2018 1:40 PM
    |
  • Question
    Sign in to vote
    5
    Sign in to vote

    Here is the FIX for this issue ..

    --> Change the Group Policy on your local client to use the vulnerable setting 

    Run:  gpedit.msc

    Go to à Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Encryption Oracle Remediation

    Open - Encryption Oracle Remediation à  choose Enable  à change protection level àVulnerable àApply

    Thanks and Regards,

    Regu



    • Proposed as answer by RedITAdmin Friday, May 18, 2018 2:47 PM
    Monday, May 14, 2018 1:41 PM
    |
  • Question
    Sign in to vote
    4
    Sign in to vote

    Here is the FIX for this issue ..

    --> Change the Group Policy on your local client to use the vulnerable setting 

    Run:  gpedit.msc

    Go to à Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Encryption Oracle Remediation

    Open - Encryption Oracle Remediation à  choose Enable  à change protection level àVulnerable à Apply

    Thanks and Regards,

    Regu

    This fixed it for me, thank you!

    Windows 10 Pro --> Logging into a Windows server 2012 R2 on a domain

    Monday, May 14, 2018 2:21 PM
    |
  • Question
    Sign in to vote
    9
    Sign in to vote

    Is this the same as the user changing their Remote Desktop setting from the dialog box that we suggested?

    Going into gpedit.msc is much more intimidating, and I don't think end users are allowed to do that.

    Luke Chung
    Microsoft MVP
    President of FMS, Inc.
    Blog Facebook Twitter

    • Proposed as answer by techguest Tuesday, September 4, 2018 4:34 PM
    Monday, May 14, 2018 2:34 PM
    |
  • Question
    Sign in to vote
    6
    Sign in to vote

    You need to make sure both your workstations and servers are patched with the March CredSSP patch.  On May Patch Tuesday, Microsoft released a patch that basically enforces the March patch, so if your workstation got the May patch but you're trying to connect to servers that haven't received the March patch, you'll get this error.

    As a workaround, you can push a Group Policy out or edit a registry key locally, but neither one of those is considered a long-term permanent solution.

    You can read - How to Fix Authentication Error Function Not Supported CredSSP Error RDP for more information on the Group Policy and registry key.

    For the Group Policy, you'll need the ADMX files from a patched server.  In the article above, there's a link to those files from a patched Windows 2012 R2 server which should work.

    Policy path: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation Setting name: Encryption Oracle Remediation 

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters]
    "AllowEncryptionOracle"=dword:00000002

    • Proposed as answer by Waterman981 Monday, May 14, 2018 9:12 PM
    Monday, May 14, 2018 4:37 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Are those instructions for end users or administrators?

    Most users can't change registry settings on their own, much less the HKLM hive.

    They can change the check box on the Remote Desktop dialog.

    If it's a setting on the network that's changed, will that support people's home PCs and devices they use to remote into their office PC?

    Luke Chung
    Microsoft MVP
    President of FMS, Inc.
    Blog Facebook Twitter



    Monday, May 14, 2018 4:39 PM
    |
  • Question
    Sign in to vote
    4
    Sign in to vote

    Hi and thanks for your observations.

    Don't you think its ironic that the security patch enforced on us poor sods forces one to operate in a less secure manner and the eta of the patch for the patch is unknown. Thanks again Microsoft, you bunch of gimps.

    KillerWombat

    Monday, May 14, 2018 10:36 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote
    its worked for me Thanks 
    Tuesday, May 15, 2018 9:29 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    This worked for me. Thanks!
    Tuesday, May 15, 2018 10:30 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks! Worked for me.
    Tuesday, May 15, 2018 4:21 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks . Worked for me. I am using Azure. Worked on both WIndows 10 and WIndows 7 devices.
    Tuesday, May 15, 2018 7:01 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Luke,

    Regu Sankar's solution using gpedit.msc is not the same as your solution for the following reason:

    I was able to use gpedit.msc on my local client (which fixed the issue), whereas I was NOT able to open the system properties on the server, because that's a VM running in Azure.

    To change the server's system properties, I would need to connect to that machine via Remote Desktop. See the problem?


    • Edited by vor0nwe Wednesday, May 16, 2018 10:35 AM
    Wednesday, May 16, 2018 10:34 AM
    |
  • Question
    Sign in to vote
    2
    Sign in to vote

    Thank you for this article, Luke.

    In my user's case, the issue was resolved by updating Windows 10 to the most current version (16299.431 as of today, May 16th, 2018). The machine was missing 2018-05 Cumulative Security Update 1709 - KB4103727. My own Windows 10 box was able to connect to the RDP computer without issue, which helped to lead me in the direction of checking revisions. Being more current, my machine had no problem connecting to the RDP machine. I did not want to reduce the security by unchecking the box for Network Level Authentication, so I was glad that Windows updates fixed this.

    Best regards,

    Philip Schember
    Senior IT Technician
    University of Tennessee

    Wednesday, May 16, 2018 2:44 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    excellent...working properly
    Thursday, May 17, 2018 8:34 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    I see all of the solutions only if you able to access windows server. RDP access was the only way I could manage the server. What should I do now, I am getting this message and cannot access the server any advice ?
    Thursday, May 17, 2018 3:29 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    This worked for me.  

    I installed the Windows 10 "Upgrade" to the latest version, which shows to be Version 1709, build 16299.431.  After that update completed, I received this authentication error.  Using the Fix first posted by Regu Sankar, it worked immediately.  

    So thank you, Regu!

    Thursday, May 17, 2018 4:17 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    I just provisioned a Windows Server 2012 R2 server in Azure. Everything has installed properly. I can see the boot screen. I cannot RDP to the newly provisioned server from a Windows 7 Enterprise RDP Client. 

    It is not showing the CredSSP part of the message.

    Thanks,

    Ken

    Thursday, May 17, 2018 6:52 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    My ability to remote in stopped this week when the update caused the error you mentioned in the original post. My Remote settings were actually already set the way that you suggested - I checked that first per your suggestion.

    I wanted you to know that the fix that worked for me was going into gpedit.msc as suggested by Regu. I was one of those employees/end users who needed to remote in from home, and as you mentioned, I wasn't sure I'd have the permissions to go in there, but it turns out that I did.  

    Thank you for starting this discussion because in it I found a solution to my issue. I hope my feedback helps you or someone else.

    Friday, May 18, 2018 2:53 AM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    It works for me.

    Windows 7 connecting to Windows Server 2016 error.

    Solution:

    In the server you are connecting(in my case winserver 2016) uncheck the "Allow Connections only from computers running Remote Desktop with Network level Authentication(recommended)".

    <img alt="System Properies -> Remote tab -> Uncheck" src="http://blog.fmsinc.com/wp-content/uploads/2018/05/remote-windows10.png" />

    Friday, May 18, 2018 6:34 AM
    |
  • Question
    Sign in to vote
    2
    Sign in to vote
    OK!
    I think I have fixed the issue for me, so let me tell you what I did as it may help others.

    Seeing that 'windows update KB4103725' was a bad release and it was released on the 5/8/18. None of the advice I found worked.

    1) Change:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters]
    "AllowEncryptionOracle"=dword:00000002
    (isn't there in windows 7)

    2) Remove:

    Remove the tick from the "Allow connections only from computers running Remote Desktop with Network Level Authentication"
    (isn't there in windows 7)

    3) Delete:

    Delete windows update 'KB4103725'
    (isn't there in windows 7)

    4) Click the tick:

    Click the tick from the "Allow connections from computers running any version of Remote Desktop"
    (as shown at:
    http://blog.fmsinc.com/remote-desktop-authentication-error-function-requested-is-not-supported-credssp/
    ,but isn't there on my windows 7)


    Finally I saw a windows update 'KB4103718' which was installed on my computer on 5/9/18. As it looked similar to 'KB4103725', I deleted it and restarted my computer. I could then connect!
    Friday, May 18, 2018 6:47 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks!
    Friday, May 18, 2018 7:09 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

     This Fix worked for me. Thank you.

      

    Friday, May 18, 2018 10:01 AM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote
    This worked for me! Thanks so much! .....now back to work!
    Friday, May 18, 2018 2:48 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Regu, this fixed it for me.
    Friday, May 18, 2018 5:33 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Do you know if it applies to Windows Server 2016 and / or Windows Server 2012R2?

    For your  help and time, thanks.

    Friday, May 18, 2018 6:57 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Similar circumstances in my workplace following the Tuesday updates.  Post any attempts at resolution to this.  
    Friday, May 18, 2018 8:08 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    Here is the FIX for this issue ..

    --> Change the Group Policy on your local client to use the vulnerable setting 

    Run:  gpedit.msc

    Go to à Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Encryption Oracle Remediation

    Open - Encryption Oracle Remediation à  choose Enable  à change protection level àVulnerable à Apply

    Thanks and Regards,

    Regu

    This one fixed my problem. Thanks.
    Friday, May 18, 2018 10:56 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks, fixed my problem
    Sunday, May 20, 2018 9:36 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    This worked for me (Windows 10 Pro).

    Thanks a lot "Ragu Sankar".


    Sunday, May 20, 2018 8:00 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you, this fix for me.

    Alin Lam

    Monday, May 21, 2018 6:01 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    I've updated my blog post with the information shared here about editing Group Policy and setting it to Vulnerable. It's an option if you can't modify the target PC/VM, and have administrator rights to your PC.

    The update includes screenshots and step-by-step instructions for doing so: 

    Remote Desktop Authentication Error Has Occurred. The function requested is not supported. CredSSP Workaround

    Sorry to see there are still so many people suffering from this problem in the second week. Hope it helps. 

    Luke Chung
    Microsoft MVP
    President of FMS, Inc.
    Blog Facebook Twitter



    Monday, May 21, 2018 4:17 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks

    This worked for me..

    "

    Here is the FIX for this issue ..

    --> Change the Group Policy on your local client to use the vulnerable setting 

    Run:  gpedit.msc

    Go to à Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Encryption Oracle Remediation

    Open - Encryption Oracle Remediation à  choose Enable  à change protection levelàVulnerable à Apply

    Thanks and Regards,

    Regu"

    • Edited by VaGangal Monday, May 21, 2018 6:45 PM
    Monday, May 21, 2018 6:44 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote
    Thank you!
    Monday, May 21, 2018 8:57 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Not a fix if you're running Windows 10 Home.
    Tuesday, May 22, 2018 4:39 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    I think the this is the best solution since you don't need to reboot your desktop. Thank you Regu!
    Tuesday, May 22, 2018 10:13 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote
    This Fixed the issue for me too... 
    Super thanks!!!
    Thursday, May 24, 2018 11:35 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Worked great thanks.
    Thursday, May 24, 2018 5:29 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    I was locked out of one VM Host machine and one VM on another host, Regu's fix worked for me. Thank you!

    I did remove the KB4103718, but it had no effect.

    Thursday, May 24, 2018 6:28 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2018-0886

    Depend on which operating system you have.

    Friday, May 25, 2018 12:08 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hiu Guys.

    Thanks you for share this info.

    It worked for me.

    Client Win7/10 to connect Win Srv 2012/2012R2.

    Have a Niece Day.

    "Here is the FIX for this issue ..

    --> Change the Group Policy on your local client to use the vulnerable setting 

    Run:  gpedit.msc

    Go to à Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Encryption Oracle Remediation

    Open - Encryption Oracle Remediation à  choose Enable  à change protection levelàVulnerable à Apply "

    • Edited by carlyML587 Friday, May 25, 2018 9:21 PM
    Friday, May 25, 2018 9:19 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    thanks 

    Saturday, May 26, 2018 10:04 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Guys, when specifying fixes, please clearly state if the specific fixes/workarounds pertain to the client or the server.   My understanding is that unchecking NLA pertains to the server, not the client.

    I'm assuming that the 5/16 update pertains to the client, since it was mentioned to be a Win10 patch, not the server, correct?

    A consultant can't RDP into our servers which may be behind in patches, but have NLA disabled throgh local GPO.
    I am unable to reproduce the problem but my personal Win10 desktop is fully patched and on build 1803.
    My laptop was on build 1709 and not yet having patches from 5/8 but after fully patching it, it will be on build 1803.   Our corporate Win10 workstations are managed by SCCM.  I suspect they are still on build 1709 and have received the 8/5 patch, so my tests are probably not exact to reproduce the problem.

    But with all these discussions/comments, many are lacking Win10 builds involved and if the recommended changes are to be applied to client or server.

    Sunday, May 27, 2018 5:38 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you!
    Monday, May 28, 2018 3:45 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks a lot Philip Schember.

    It works for me (and for my team).

    Monday, May 28, 2018 9:53 AM
    |
  • Question
    Sign in to vote
    2
    Sign in to vote

    Have this issue as well in our environment.  Typical untested patch that makes a headache for large groups of people.  Very irresponsible of the patch team.

    Remove the tick from the "Allow connections only from computers running Remote Desktop with Network Level Authentication" got us working again

    Windows Desktop Client to Server 2012 R2

    Yep sadly this level of garbage QA is typical of Microsoft in Win10. For Enterprise, Microsoft's current testing regime is a disaster. Visual Studio, Windows, Teams, Office all buggy, full of regressions. New Remote Desktop app is absolutely abysmal over another RDP. It's atrociously laggy - unusable. Plain vanilla upgrades of apps is a minefield. Stuff just doesn't work.
    • Edited by MRR111 Tuesday, May 29, 2018 3:07 AM
    Tuesday, May 29, 2018 3:03 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Regu, that solved the problem for me.
    Tuesday, May 29, 2018 4:08 PM
    |
  • Question
    Sign in to vote
    6
    Sign in to vote

    use this link:

    https://gallery.technet.microsoft.com/Remote-desktop-authenticati-a9f4b9f8

    • Proposed as answer by NICOLA FER Thursday, June 7, 2018 1:05 AM
    Wednesday, May 30, 2018 3:21 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you. This solution worked for me. Hopefully, Microsoft will fix this patch soon. 
    • Proposed as answer by ALICE FONTINE Saturday, June 9, 2018 4:45 AM
    Wednesday, May 30, 2018 9:35 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks... :)
    Thursday, May 31, 2018 8:45 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks, That helped me.... Nice one
    Friday, June 1, 2018 2:37 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    This worked for me.

    Thank you

    Saturday, June 2, 2018 6:24 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Protection level Vulnerable didn't work, changing it to Mitigated worked for me
    • Edited by Sujan00 Saturday, June 2, 2018 2:53 PM
    Saturday, June 2, 2018 2:53 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Or you can just uninstall update KB4103725 
    https://support.microsoft.com/bg-bg/help/4103725/windows-81-update-kb4103725

    worked for me


    This is the best and safest fix suggested so far, not compromising security like the other suggestions.

    And it works.

    Thank you.

    Tuesday, June 5, 2018 8:52 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi and thanks for your observations.

    Don't you think its ironic that the security patch enforced on us poor sods forces one to operate in a less secure manner and the eta of the patch for the patch is unknown. Thanks again Microsoft, you bunch of gimps.

    KillerWombat

    Patch for the fix is KB4103725 as suggested above by Kristina Chitalovska
    Tuesday, June 5, 2018 8:55 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Awesome!!! Worked for me!!! Don't know what caused the error thought, but I'm able to Remote in without any issues.

    Cesar Vazquez

    Tuesday, June 5, 2018 8:19 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks, this worked for me! 
    Wednesday, June 6, 2018 2:40 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    use this link:

    https://gallery.technet.microsoft.com/Remote-desktop-authenticati-a9f4b9f8

    Thank you. This solution worked for me
    Saturday, June 9, 2018 8:07 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Here is the FIX for this issue ..

    --> Change the Group Policy on your local client to use the vulnerable setting 

    Run:  gpedit.msc

    Go to à Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Encryption Oracle Remediation

    Open - Encryption Oracle Remediation à  choose Enable  à change protection level àVulnerable à Apply

    Thanks and Regards,

    Regu

    Thank you very much for the solution!
    Monday, June 11, 2018 4:59 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you for the solution
    Monday, June 11, 2018 7:42 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Huge thanks for this - saved me lots of time and aggravation!

    Sarah.

    Wednesday, June 13, 2018 8:53 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    You dont necessarily have to RDP to remote machine when you can manage it using other methods (Powershell/Remote registry) to name a few.

    reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters" /f /v AllowEncryptionOracle /t REG_DWORD /d 2


    Wednesday, June 13, 2018 11:50 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks
    Wednesday, June 13, 2018 11:52 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Tnx ! its work !! 
    Thursday, June 14, 2018 7:13 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    It worked for me.

    Thank You !

    Raghvendra

    Friday, June 15, 2018 6:51 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks. works perfectly
    Thursday, June 21, 2018 7:27 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    You should take into account that by applying your workaround, you're putting at risk the source and destination computer for the RDP connection.

    Microsoft suggests applying the pertinent Security Patch in both ends.

    There's an article from Microsoft for all the scenarios:

    CredSSP encryption oracle remediation

    Regards.


    • Edited by fedayn2 Thursday, June 21, 2018 9:56 AM
    Thursday, June 21, 2018 8:14 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for sharing.

    It worked on Windows 8.1 64 bit

    Cheers

    Thursday, June 21, 2018 1:03 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    its worked for me Thanks 
    Monday, June 25, 2018 1:01 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    instal in the server the respective KB

    2008 R2-> http://www.catalog.update.microsoft.com/Search.aspx?q=KB4103718
    2012 R2-> http://www.catalog.update.microsoft.com/Search.aspx?q=KB4103725

    Wednesday, June 27, 2018 2:37 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    This worked....!! thanks
    Friday, June 29, 2018 6:17 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Legend! Thank you!
    Friday, June 29, 2018 10:21 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    thanks ...
    Monday, July 2, 2018 5:53 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Great, this worked perfectly for me
    Wednesday, July 4, 2018 9:42 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks, It works

    Thursday, July 5, 2018 12:11 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you very much , this did the trick

    Sdc

    Thursday, July 5, 2018 2:12 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    This began happening after I upgraded my workstation to 1803.  After verifying the server(s) were updated (several were not), I was able to remote connect!

    Tim ...

    Thursday, July 5, 2018 5:14 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Amazing! Thank you
    Friday, July 6, 2018 11:32 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Regu

    Thanks a lot , your guidance fixed it my problem

    Friday, July 6, 2018 11:43 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    I don't see "Encryption Oracle Remediation" in Windows 10.
    Wednesday, July 11, 2018 9:55 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    I don't see "Encryption Oracle Remediation" option in my in Windows 7 gp.
    Thursday, July 12, 2018 6:02 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Dude you saved my life. Microsoft support team is useless...
    Saturday, July 14, 2018 2:09 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks. It's worked to me.

    Monday, July 16, 2018 11:55 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Worked perfectly. Thank you.
    Monday, July 16, 2018 5:46 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you so much!! this was driving me crazy for a while now!!
    Monday, July 16, 2018 8:51 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks. Worked like a charm!!
    Tuesday, July 17, 2018 7:18 AM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote
    Thanks!  This worked a treat.  
    Wednesday, July 18, 2018 10:14 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    This solution fixed my issue. Thanks you so much. 
    Thursday, July 19, 2018 3:20 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Worked perfectly, THANKS!!!
    Thursday, July 19, 2018 5:56 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you so much.

    this method is working with windows server 2012 R2 also.

    thanks a lot

    T.A.

    sign.

    Friday, July 20, 2018 10:37 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Which method are you referring to?

    Updating Windows Server with patches or doing the workaround?

    (I have too many servers and VMs to do the workaround on all of them.)

    Friday, July 20, 2018 5:52 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    I ended up going in and running the Security Only updates for all of my Server 2012 R2 hosts and VMs.

    Now RDP from my Windows 7 Pro PC is connecting to them all normally without any workarounds or decreased security.

    The weird thing to me is that this started happening outside of any Windows Updates. In fact, it was almost dead in the middle of my standard patch cycle. So I don't even know if it started with something about my Windows 7 install or something about the Server 2012 R2 installs. I'm guessing it's the Windows 7 installs because I hadn't patched the servers in a while because of fear of this exact thing happening.

    Tuesday, July 24, 2018 4:03 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks!! This fixed some access errors from my Win7 Pro SP1 workstation. 
    Monday, July 30, 2018 1:25 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Appreciated 
    Tuesday, July 31, 2018 9:50 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank You, it's worked :) 
    Wednesday, August 1, 2018 7:24 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Nice My problem solved.
    Thursday, August 9, 2018 4:16 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks so much, The issue had been solved. 

    Sunday, August 12, 2018 8:55 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    its working thank you
    Monday, August 13, 2018 6:14 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank You so very much !!! :)
    Wednesday, August 15, 2018 8:34 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks to my brother this saved me some headaches with windows server 2016 Essentials.

    Could no access The Dashboard in 2016 essentials or used Remote Desk connections.

    After unchecked the checkbox, both options started working.

    thanks again.

    SAEdwards

    Friday, August 17, 2018 12:02 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you it works :)
    Sunday, August 26, 2018 8:26 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for this.

    As always Microsoft screws up, and it's up to users to solve their mess.

    Tuesday, August 28, 2018 10:20 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    perfect answer!
    Tuesday, September 4, 2018 4:34 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank You!
    Monday, September 10, 2018 7:55 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you so much. It worked!
    Tuesday, September 11, 2018 9:21 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    tanx

    Friday, September 14, 2018 7:49 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    In my opinion, Microsoft fixed something that wasn't working before. In many environments, you don't want anyone to be able to remote into a server without network authentication, even if they don't have domain admin security permissions on the server. A simple check mark in remote settings on servers that are going to be accessed by non domain admins seems much better to me than anyone able to remote into one of the companies critical servers. 
    Friday, September 21, 2018 8:35 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Worked for me. Thanks a lot. 
    Saturday, September 22, 2018 4:49 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks 
    Tuesday, September 25, 2018 4:56 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    THANK YOU!  This was making me CRAZY!

    shane

    Sunday, September 30, 2018 6:25 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Worked like a charm for me as well. Many thanks!!
    Thursday, October 4, 2018 2:00 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    It worked, thank you.
    Tuesday, October 16, 2018 6:22 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Is this safe?

    LM

    Tuesday, October 16, 2018 7:07 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Regu. It did help me alot.

    How can we see sites in a Server that have SSL based service (HTTPS).

    Thanks.

    Thursday, November 1, 2018 4:23 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Windows 7  to Server 2012

    I Remove the tick from the "Allow connections only from computers running Remote Desktop with Network Level Authentication"

    It worked for me.

    Thanks
    Tuesday, November 13, 2018 12:23 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    This worked for me, thank you.
    Tuesday, November 20, 2018 7:20 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    After changing group policy, you need to reset the client one time or two.

    Actually it didn't work for me even after the first reset. But the second did the work.

    Maybe you had the same situation

    Thursday, December 27, 2018 6:26 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    After changing group policy, you need to reset the client one time or two.

    Actually it didn't work for me even after the first reset. But the second one did the work.

    Thursday, December 27, 2018 6:27 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks, it's Working.

    Thursday, December 27, 2018 3:16 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    This works perfectly for me I am working on Windows 10 computer and taking remote desktop connection of Windows Server 2016.

    These setting worked perfectly on Windows Server 2016.

    Thanks,

    Chandrashekhar 

    MCSA, MCTS, MCITP & CCNA, CCNP (R&S)

    Saturday, December 29, 2018 4:18 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Its worked!!!!!

    Thanks

    Friday, January 18, 2019 2:48 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Done.

    Thank you...

    Wednesday, January 23, 2019 9:46 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    This worked for me on my home network! Thanks!
    Thursday, January 24, 2019 3:46 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Have this issue as well in our environment.  Typical untested patch that makes a headache for large groups of people.  Very irresponsible of the patch team.

    Remove the tick from the "Allow connections only from computers running Remote Desktop with Network Level Authentication" got us working again

    Windows Desktop Client to Server 2012 R2


    Thank you. Such an easy fix, but worked for me.
    Thursday, February 21, 2019 6:35 PM
    |