I saw the same article for Windows 11, however I experience this problem on Windows 10. What did I do install Azure Remote Desktop on my Windows 10 machine (latest update) logged into my company workspace using my company MS account tried to login to my remote VM I get an error message - An authentication error has occurred (Code: 0x800706be) cherry on top, this is my personal notebook. On my office computer I can access the VM just fine. Same installation of Windows and Azure Remote Desktop what can be wrong?

Had this happen to me and its easy to overlook. Make sure you don't have a cached account name in the account box. In my case somehow and oldcomputername\account (or olddomain\account) was in the rdp cached credential box and it was giving this error. Instead of using command line to login, used the ui, click on show options and changed username to .\account and was immediately prompted for the password and was able to login. Hope this helps.

The simple fix is to head to C:\Program Files\CSR\CSR Harmony Wireless Software Stack rename BLEtokenCredentialProvider.dll to BLEtokenCredentialProvider.dll.BAK

Error "An authentication error has occurred (Code: 0x800706be)" when trying to use Remote Desktop to connect in Windows 10

Hruby, Jan 1

I saw the same article for Windows 11, however I experience this problem on Windows 10. What did I do

install Azure Remote Desktop on my Windows 10 machine (latest update)
logged into my company workspace using my company MS account
tried to login to my remote VM
I get an error message - An authentication error has occurred (Code: 0x800706be)
cherry on top, this is my personal notebook. On my office computer I can access the VM just fine. Same installation of Windows and Azure Remote Desktop

what can be wrong?

Sean Huggans 6 Reputation points

2023-05-01T02:32:45.7066667+00:00

This issue occurs when running Remote Desktop elevated as a different user, and that different user account has never logged in to the workstation (no complete local profile). I've submitted a bug report to Microsoft, please help me get some traction on it with an upvote! https://aka.ms/AAkm0o2
Hruby, Jan 1 Reputation point

2023-05-09T07:10:55.5833333+00:00

thanks for answer, but I do not run Remote Desktop elevated, the process runs under my user. I am logging in with company account and login works from other machines, not just from this particular one
Rodrigo de Medeiros Silva 0 Reputation points

2024-02-28T14:38:48.5533333+00:00

Log into your administrator account on Windows, then log out and test again.
Work to me

9 answers

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
1 deleted comment

Comments have been turned off. Learn more
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Baba 5 Reputation points

2023-11-10T15:38:12.6633333+00:00

Had this happen to me and its easy to overlook. Make sure you don't have a cached account name in the account box. In my case somehow and oldcomputername\account (or olddomain\account) was in the rdp cached credential box and it was giving this error. Instead of using command line to login, used the ui, click on show options and changed username to .\account and was immediately prompted for the password and was able to login.

Hope this helps.
Please sign in to rate this answer.

1 person found this answer helpful.
Sabrina MacDonald 0 Reputation points

2024-01-10T17:56:42.4466667+00:00

Thanks for this. I ended up having a cached credential in credential manager; once i removed, connected to rds server with no issues.
Sign in to comment
VINCENZO MOIOLI 30 Reputation points

2023-05-21T12:46:51.88+00:00

The simple fix is to head to C:\Program Files\CSR\CSR Harmony Wireless Software Stack

rename

BLEtokenCredentialProvider.dll to

BLEtokenCredentialProvider.dll.BAK
Please sign in to rate this answer.

6 people found this answer helpful.
Ribu Xavior 5 Reputation points

2023-08-22T04:27:56.02+00:00

This is worked for me

KD 0 Reputation points

2023-09-12T17:03:18.8266667+00:00

You have saved a mystery that had plagued a computer of ours for a year and a half. Good on you. This fixed it for me as well.

WikiJM 0 Reputation points

2023-10-09T05:51:26.09+00:00

Works like a charm, thanks!

Edwin Velasco 0 Reputation points

2023-10-19T04:04:14.2333333+00:00

Excelente aporte solucionó mi problema. Muchas gracias

vithaya southammavong 0 Reputation points

2023-11-08T04:19:58.4833333+00:00

I cannot believe this solution works. I have never known the problem relates to bluetooth. Thank you so much.

Hruby, Jan 1 Reputation point

2023-11-13T08:35:54.5633333+00:00

can't wait to test it, but my laptop where this problem was happening is currently in maintenance
Sign in to comment