Unable to RDP to Virtual Machine: CredSSP Encryption Oracle Remediation

This blog is being migrated to www.solveazure.com and will be decommissioned once the content has been moved. ETA 2/28/2019

Please use www.solveazure.com for updated and continuous content. 


This specific post has moved to https://solveazure.com/2018/05/11/unable-to-rdp-to-virtual-machine-credssp-encryption-oracle-remediation/ 


Comments (22)
  1. Ryan S says:

    Just to state the obvious, this can affect a physical server as well! This doesn’t only affect a Virtual Machine (Yes, I understand this Azure VM blog). But this also was top hit on the good ole “Bing/Googlizer” searching for CredSSP RDP error.

  2. No tengo esa opción en Windows 10 HOME (I don’t have that Option In windwos 10m home to fix the problema) Not available gpedit.msc

  3. fatih says:

    hello managed to connect with your help
    could you please tell how to reverse last mitigation

  4. Ahmed Mihoub says:

    thanks for this post, it’s very helpful.

  5. LukeChung says:

    We’ve seen lots of people running into this problem where they can’t remote to their office computer or VM from home.

    We’ve found an easier workaround that doesn’t require touching the registry or setting group policies. Simply adjust the Remote Desktop settings.

    Wrote about it here: http://blog.fmsinc.com/remote-desktop-authentication-error-function-requested-is-not-supported-credssp/

    1. kiamoyman says:

      LukeChung suggestion worked for me! :) Thanks sir!

  6. ECarbone says:

    In my scenario, users are getting this message when they attempt to remote into their office workstations from home. So in this case there is no ‘server’. Does this same solution apply to home workstation to office workstation remote sessions? Does this mean the issue will be resolved if both ends (the home pc and the office pc) install the update?

  7. Siva1979 says:

    Thanks for the article. It helped me.

  8. UniMatrix says:

    Also the VM connections from Hyper-V manager are disabled. Luckily the Group Policy / registry key workaround is client based, otherwise an updated client would lose all console acces to our yet unpatched servers… Bit unnerving if you ask me.

  9. UniMatrix says:

    After some more testing it is becoming clear that when a server VM is patched, it IS possible to RDP to the server, but the VM connection from hyper-v manager is still NOT working.

  10. Devil-AP says:

    This happened to me where I work (a school) and as my Network Manager brought this problem to my attention – it seems as if the registry fix helps us remote back into the servers we couldn’t access.

    Download this batch script I made – it uses Mitigation 2 but people may find a use for the script.


  11. \ /v AllowEncryptionOracle /t REG_DWORD /d 2

    Means: Add new REG_DWORD; then Modify it to set the type from Hexadecimal to Decimal with the value from 0 to 2

  12. very helpful. thank you very much

  13. Naeem Jamil says:

    thanks Mitigation 1 works for me

  14. BolvuaM says:

    In gpedit Editor change on Encryption Oracle Remediation > Vulnerable didn’t nothing.. Even it is accessible.
    But REG ADD helped… Thank you a lot!!!! :)))

  15. Nop Siri says:

    Solved. Mitigation 2 works with my Windows 10 Home 64 bit. Thanks.

  16. iru17 says:

    Thanks for this post, it’s very helpful.
    It helped me fixing the issue.

  17. MaxPax80 says:

    Mitigation 2 solved the problem for me. Thanks for sharing the trick!

  18. It works, thank you


  19. kccrga says:


    I have windows server 2016. I can’t see Encryption for Oracle remediation. Any other fix?

  20. Bindu_P says:

    Hi, I am unable to connect to RDP in windows 10 home edition. Any solutions please.
    I have read it does not support is there a workaround?

Comments are closed.

Skip to main content