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

Contents

    Error:

    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

     

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

     

    The error impacts:

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

    Fix: 

    1. On your Local Computer
    2. Open up RUN
    3. Type in: 
      gpedit.msc

    4. Navigate to the following Computer Configuration.Computer Configuration / Administrative Templates / System / Credentials Delegation
    5. Double click on Encryption Oracle Remediation– 1 Enable Encryption Oracle Remediation
      – 2 Change Protection level to: Vulnerable

     

    Any issues – please post in the comments below.

    Updated on June 6, 2018
    Was this article helpful?

    Related Articles

    24 responses to “Remote Desktop Authentication Error Has Occurred. The function requested is not supported”

    1. Scott Avatar
      Scott

      A useful reminder that small wording clues can point to a larger configuration problem. What diagnostic step would you try next?

      Reply
    2. Fadhil Alkhouri Avatar
      Fadhil Alkhouri

      The steps here make a complicated authentication issue much easier to follow. Which part would you test first in a production environment?

      Reply
    3. Eli Avatar
      Eli

      A focused troubleshooting checklist is useful when the error text is vague. Which part of the process helped you narrow down the cause?

      Reply
    4. Raylan Avatar
      Raylan

      The troubleshooting notes are useful and easy to follow. Which step should be revisited if the connection still fails after the initial fix?

      Reply
    5. Joe Miller Avatar
      Joe Miller

      This article makes the failure mode much less mysterious. What is your preferred first test when a session suddenly refuses authentication?

      Reply
    6. Kerri Avatar
      Kerri

      A thoughtful overview of a frustrating issue. Did the recommended fix behave consistently on both older and newer clients?

      Reply
    7. Joe Miller Avatar
      Joe Miller

      The checklist gives a helpful path through a tricky error. Has anyone found a reliable way to confirm the change without restarting the whole workstation?

      Reply
    8. Nora Avatar
      Nora

      The guide turns a confusing authentication error into a manageable checklist. Which step should be repeated if the first attempt does not work?

      Reply
    9. Joe Miller Avatar
      Joe Miller

      The explanation is clear and refreshingly practical. Which symptom tells you that the authentication setting is the real culprit?

      Reply
    10. Joe Miller Avatar
      Joe Miller

      The troubleshooting flow is nicely structured. Has anyone compared these steps with a fresh client setup to isolate the cause?

      Reply
    11. Joe Miller Avatar
      Joe Miller

      I appreciate the practical focus of this guide. Which verification step gives you the most confidence that the authentication problem is resolved?

      Reply
    12. Joe Miller Avatar
      Joe Miller

      This is a useful reminder that small policy details can block a connection. What would you check first when the same message appears again?

      Reply
    13. Joe Miller Avatar
      Joe Miller

      The sequence of checks is especially helpful here. Has anyone found a quick way to spot this configuration issue before it causes a failed session?

      Reply
    14. Joe Miller Avatar
      Joe Miller

      A concise troubleshooting guide like this is easy to revisit. Which step would you recommend checking before making any broader changes?

      Reply
    15. Joe Miller Avatar
      Joe Miller

      This walkthrough highlights an easy-to-miss configuration detail. What is the safest way to verify the fix before reconnecting?

      Reply
    16. Brenda Avatar
      Brenda

      A clear example of the issue and its fix. Has anyone noticed whether this problem returns after a system update?

      Reply
    17. Den Avatar
      Den

      The article explains the underlying problem in a straightforward way. What quick check confirms that the client is ready to reconnect?

      Reply
    18. Jefferey Galgano Avatar
      Jefferey Galgano

      A practical walkthrough like this can save a lot of troubleshooting time. Which diagnostic check should be tried first when the error appears?

      Reply
    19. Leo Avatar
      Leo

      The error message points to a subtle compatibility issue. Has anyone tested this fix across multiple Remote Desktop clients?

      Reply
    20. Maya Avatar
      Maya

      This article offers a useful starting point. Has anyone confirmed which authentication setting matters most in practice?

      Reply
    21. Kelly Avatar
      Kelly

      This guide makes the cause much easier to understand. Did a reboot alone help, or was an additional policy change needed?

      Reply
    22. Frank Avatar
      Frank

      The authentication failure can be confusing at first. Which step made the biggest difference for you when testing the connection?

      Reply
    23. Ryan Avatar
      Ryan

      I followed the troubleshooting steps and found the explanation clear. Has anyone tried the same fix on a recently updated client?

      Reply
    24. panadia Avatar
      panadia

      Has anyone else found a reliable way to resolve this Remote Desktop authentication error? The troubleshooting steps here are a helpful starting point.

      Reply

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    Contents