Has anybody been able to fix the RDP authentication error 0x800706be in Windows 11 after upgrading from Windows 10?

I upgraded to Windows 11 pro from a fresh install of Windows 10 Pro (unknown which version) the week that 11 came out. Since then, I am not able to connect to ANY Remote Desktop server. I get an authentication failure message with the error code 0x800706be. A cursory search on google indicates that this seems to only crop up when doing an upgrade vs a fresh install.

I’ve tried sfc and it did find and fix at least one corrupted file but I still can’t use Remote Desktop unless I use the windows store app, which is not great for my use case. I was hoping that I’d see a fix come in on patch Tuesday but I still haven’t.

Here’s an example of the problem:

I solved my issue in a radical way, maybe this will help to find a bugfix:

Because it was a new PC with a fresh Win10 installation from Sunday (honestly an old version from 09.2017 which I upgraded to latest possible, in my case 20H2).

Everything was fine, RDP made a good job with the latest Win10 20H2 version.

Two days later I made the Win11 upgrade on Tuesday and the reported error appeared. I just installed a few programms on my Win10: LibreOffice, Tracker PDFeditor and old versions of OneNote (Desktop) and Adobe CS.

Because I found no bugfixes online, I decided to waste no time and go ahead with new installation:

First try: Win11 repair with keeping all personal data > no effect, problem was still the same.

Second try: Complete fresh Win11 installation with formating the HDD > After that and also after installing the same programs, the mstsc.exe RDP programm worked without any problem. EDIT: I forgot, I installed 7zip on Win10 but not after the fresh Win11 installation.

Obviously it a problem with the Update and not with the mstsc.exe or with the account in general. The MS Store RDP client (which is really bad) worked. But this is not really a solution for a full dialy use and if the fullscreen without the task bar of the local system is needed. Hopefully this will not happen again with a later Win11 update.

2 Reset to default

Know someone who can answer? Share a link to this question via email, Twitter, or Facebook.

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like