Kindly be advised we cannot cancel subscriptions or issue refunds on the forum.
You may cancel your Bitdefender subscription from Bitdefender Central or by contacting Customer Support at:

Thank you for your understanding.

Ids Causes Slowing Down Of Internet


Bitdefender intrusion detection system causes problem with internet connection if it is set to normal or higher. It causes TCP connections to remain in ESTABLISHED state forever. This causes slowing down of internet and consequently cause slowing down of system performance.

So it is recommended that IDS setting to keep in Permissive mode. <img class=" />


  • Georgia
    Georgia ✭✭✭


    By default, IDS is set to a Permissive level in The New Bitdefender.

    However, such slowdown is abnormal.

    To further investigate it, please post here a support tool log gathered while you managed to replicate this issue.

    In The New Bitdefender, the support tool executable "supporttool.exe" is found in this location:

    C:\Program Files\Bitdefender\Bitdefender

    Run "supporttool.exe" (right click on "supporttool.exe" and choose "Run as Administrator" if you have Windows Vista/7/8 ).

    Fill in the required fields, check the box "I want to reproduce the issue" (now take all the actions to replicate the encountered issue).

    When the progress bar gets to the end click "Finish". A new archive will appear on your desktop. The name starts with "BDSP_....".

    You may not be able to upload the archive here as it's too big so you can put it on or any other file hosting site and post the download link.

    I am waiting for your answer. Thank you!

  • viktik137
    edited July 2013

    Here is the file generated by the support tool.

  • viktik137
    edited July 2013

    here is the pics from process hacker showing chrome TCP connection stuck in ESTABLISHED state even after chrome has been closed.


  • Maybe this helps, seems to be an old, well known problem:

  • Just wondering if this was resolved. No moderator replied.

  • Georgia

    @ Viktik

    Please tell me if this workaround fixes the issue:

    I'm looking forward to your feedback.