01 October 2019

Microsoft Remote Desktop breaks with error 0x800706be every time you try to make an outgoing connection

I was getting the above "An authentication error has occurred (Code: 0x800706be)." every time I tried to remote out of my work PC. Couldn't figure it at all, and thought it was the machine I was trying to remote into. Turns out that the CSR Harmony Bluetooth stack (it's old, but the only way to easily get APT-X on a reasonably cheap bluetooth dongle for my Sony headphones) breaks the authentication. Wtf.

Renaming C:\Program Files\CSR\CSR Harmony Wireless Software Stack\BLEtokenCredentialProvider.dll to something else (I went with .disabled, but whatever works) instantly solves the problem, and doesn't seem to affect the bluetooth setup at all.

Mostly keeping this here for my own benefit, but hopefully it'll help those searching for an answer.

(Originally spotted via https://community.spiceworks.com/topic/1778270-rdp-from-windows-10-to-anywhere - took me ages to find the answer, over several months!)

Edit: New versions of Windows 10 don't play nice with the CSR Harmony Bluetooth stack. It should be removed. But be aware, I've seen it break the Bluetooth audio stack when doing so - to the point Skype crashes when attempting to initialise the Bluetooth microphone. Haven't found a fix yet.

Edit 2: Apparently Solarwinds RMM also causes the same problem. Guessing other third party authentication systems can cause similar problems.
Posted by at

28 comments:

  1. khelkun21 April, 2020 10:13

    dude you saved my day!

    ReplyDelete
    Replies
    1. Richard Aspden21 April, 2020 10:28

      Glad I could help, was hoping I could save someone else pulling their hair out! :-) Certainly took a bit of chasing down.

      Delete
    2. Anonymous04 October, 2021 09:24

      Fixed me! Thank you! Wow

      Delete
  2. Anonymous04 August, 2020 17:41

    Thank you thank you thank you! What a weird error! You saved me!

    ReplyDelete
  3. BangNguyen17 August, 2020 12:11

    Thank Sir, you save my week! I am being crazy with this for a week.

    ReplyDelete
  4. Anonymous24 August, 2020 16:45

    Saved my day too. Thanks!

    ReplyDelete
  5. AlbertWang07 October, 2020 06:56

    Thank you!!! I was thinking the problem is on the remote PC! You saved me!

    ReplyDelete
  6. Dave20 October, 2020 12:54

    Thanks! I had the same strange problem. My file was named: BLEtokenCredentialProvider.dll.bak
    but once I renamed that file my Microsoft RDP client worked.

    ReplyDelete
  7. Dave20 October, 2020 13:10

    Thank you for your help. I had the same problem on my Windows 10 Pro PC, no matter what computer I was trying to use Microsoft RDP to connect to, and no matter what account I was trying to sign in with. It worked fine until I installed updates from the October 2020 patch Tuesday, along with Flash Player 32.0.0.445 Plugin MSI (Upgrade) and Skype 8.650.78 (Upgrade). I don't know which of the updates caused it to break, but your solution worked perfect!

    ReplyDelete
  8. Unknown28 October, 2020 09:53

    you saved my day!

    ReplyDelete
  9. Anonymous03 November, 2020 23:14

    I've been trying to figure out this problem for 6 months... You saved me!! Thank you very much.

    ReplyDelete
  10. i am25 November, 2020 11:53

    Thank you thank you thank you.

    its work!!!

    ReplyDelete
  11. Anonymous29 November, 2020 00:13

    You totally saved my day, started getting the error trying to troubleshoot something at our hospital.

    ReplyDelete
  12. Angwstos X05 December, 2020 15:11

    It works!!! Your the best :P

    ReplyDelete
  13. Anonymous23 December, 2020 09:44

    Works! Great! Thank you so much!

    ReplyDelete
  14. Unknown27 January, 2021 19:25

    Wow that is weird. Must be some kind of collision somewhere.

    ReplyDelete
  15. Anonymous07 February, 2021 19:36

    Yes I'm in! Another one saved today, thanks a lot!

    ReplyDelete
  16. IIIXJokerXIII05 March, 2021 02:56

    I spent 6 hours trying Microsoft fixes, watching videos ect seen your post and fixed in 10 sec... OMG send me a donation link I owe you a beer IIIXJokerXIII@gmail.com

    ReplyDelete
    Replies
    1. Richard Aspden08 March, 2021 10:14

      The thought's appreciated buddy, but I really can't take credit, except for the final bit of google-fu that got me the answer. Just wanted to make it more visible to hopefully save people the sheer frustration I went through if I could!

      Delete
  17. Unknown12 March, 2021 13:08

    nice one, that helped alot

    ReplyDelete
  18. libertarianteacher17 March, 2021 19:48

    This was literally the first link I found when searching for this error, and it just HAPPENS that I have that same CSR stack installed. Yes it worked!

    ReplyDelete
  19. Unknown22 March, 2021 13:33

    Perfect one. Solved it immediately.Thanks a lot.

    ReplyDelete
  20. Unknown27 March, 2021 18:25

    Thanks Rick, that worked perfectly!

    ReplyDelete
  21. Anonymous29 March, 2021 11:02

    Excelent solution. I could not find the file but i have solved the issue when i uninstall that CSR application.

    ReplyDelete
  22. Anonymous09 July, 2021 08:17

    Rick... as everyone else said, amazing find.

    ReplyDelete
  23. Unknown16 November, 2021 01:55

    Thank you! It has solved my issue too :)

    ReplyDelete
  24. Unknown06 January, 2022 11:19

    Thank you for posting this fix. Saved so much time. Legend!

    ReplyDelete
  25. olo02 February, 2022 07:27

    Wow! Thank you.

    ReplyDelete

Subscribe to: Post Comments (Atom)