Bitdefender Antivirus Breaks RDP (Remote Desktop) on Windows

Updated Posted by Arnon Erba in News on .

Bitdefender Antivirus — the free edition, at least — appears to be interfering with Remote Desktop Protocol (RDP) connections on Windows. Affected users may receive the following error when they try to log on to a remote PC or server with Network Level Authentication (NLA) enabled:

An authentication error has occurred.

The Local Security Authority cannot be contacted.

This could be due to an expired password.

While an expired password or a server-side misconfiguration can cause this error, it may also indicate a client-side issue. In this case, the error appears to be caused by Bitdefender Antivirus replacing the remote computer’s certificate in order to inspect encrypted RDP traffic. This process breaks Network Level Authentication and causes the connection to fail.

One workaround is to add file-level exclusions in Bitdefender for both the 64-bit and 32-bit versions of the Windows RDP client:

  • C:\Windows\system32\mstsc.exe
  • C:\Windows\syswow64\mstsc.exe

This is not an ideal solution, but the free version of Bitdefender Antivirus has a limited control panel and does not provide alternative workarounds.


11 responses to “Bitdefender Antivirus Breaks RDP (Remote Desktop) on Windows”

  1. Scott says:

    I have literally been going crazy with this problem for months. Thank you so much for this article. I can return to my therapist with my other issues now.

    1. Anonymous says:

      same here but only for a weeek

  2. Arnon Erba says:

    Hi Everyone,

    I have opened a ticket with Bitdefender about this issue via their contact form here: I will update this post if I hear back from them.

  3. Anonymous says:

    Thank you! Thank you!! This was killing me to try to find the issue! This worked!

  4. Bear says:

    Thank you so much. You're a Godsend!

  5. Rob says:

    Wish I would have found this a few clumps of hair ago.

    Dropped the two files in the exceptions on free edition, problem solved.

  6. Alfonz says:

    Thank you very much. This issue made me pull my hair and accusing my sons returning from Uni to be the root cause!

  7. Jason T. says:

    Thanks for this info. I spent a good amount of time tracing down an issue with a client that could not connect to a remote server. Unfortunately the client was not using NLA, so the main symptom was to just close after the server certificate acceptance process. Furthermore, there was no errors logged in the system or the remote system either. I was finally able to trace this down by connecting to another server that did use NLA and get the error above.

    1. Arnon Erba says:

      Hi Jason,

      Thanks for the comment. It's interesting to hear about the different behavior with NLA disabled. That sounds like even more of a nightmare to troubleshoot.

  8. Will says:

    Thanks Arnon. This fixed my problem and exactly described what was happening.

  9. Richard Judd says:

    I noticed this symptom on my PC last year, in the end I had to uninstall Bitdefender Free version because as you pointed out in the article, there isn't much that can be changed on the Free version and at that time, I didn't know why.

    I originally just uninstalled Bitdefender and continued with Windows Defender, but having installed Bitdefender recently in the hope that Remote Desktop issue wouldn't occur, I was pleased to find your blog stating the reason and at least a way to mitigate the issue, even though the only choice is an exclusion!

    So, thank you for the article.

Leave a Reply

Your email address will not be published.