Irresponsible Behavior

I would like to know how to stop this or see this issue fixed. I am getting to the point of asking for a full refund of my subscription because of these problems. Every time BitDefender deletes or quarantines a file, I am unable to write anything to a file of the exact same path name after telling BitDefender to unblock it. It's bad enough the product will quarantine a program with almost no code, but to block further writes to that file is ridiculous If I recover a file, the BitDefender should not continue to block writes it, which is an especially obvious bug or irresponsible coding on the engineers' or director's part who designed the recovery system.

I've attach the source to a program compiled with Visual C++ 2015 that BitDefernder blocked. A program that does not read or write any data to disk, or send or receive any data from the network. This has become a joke of an A/V for these kinds of problems.

playground.cpp

Find more posts tagged with

Comments

Sorin G.

Hello,

Please open a case with our support team using bitsy@bitdefender.com

Please also attach the sample file and ensure it is archived with a password.

Thank you for understanding

6XGate

Pursuant to getting this resolved, I have built an EXE from the aforementioned C++ source file and sent it to the support staff via the indicated e-mail address. I have also linked to this form thread for further reference.

6XGate

This is getting ridiculous;

Support has not help with dealing this other than to tell me a sample of one small test-bed program I compiled was sent for analysis. The problem with software still remains.

I have updated to AVPlus 2017... the latest.
The product still detect recently compiled simple C++ programs as malicious, regardless of behavior. This is a bit ridiculous, but not an issue; the directory can be excluded.
The Recover option from the Real-Time engine seems to work now. But I've only seen this options appear once.
Allow and Monitor is still irresponsibly broken, I'll explain:
- Write a small C++ application using simple console I/O or file I/O behaviors.
- First compilation of the .EXE is detection by the Active Threat feature.
- I click Allow and Monitor, the file is restored.
- Then, a notification from the Real-Time engine appears stating it has detected and quarantined the file.
- I click Recover, the file is restored again. Still haven't been able to return the Visual Studio Code to write anything more yet.
- Finally, I change the program, for fixes or additions, and compile it again.
- The Active Thread feature detects it again; deleting it, WITH NO OPTION TO RECOVER OR ALLOW!!!
  - ALSO, the file is NOT in quarantine, meaning the file has been permanently deleted. I'm glad this wasn't some import document I was working or photo I just made from the system in running the software.

This user experience is unacceptable, it appears as though this product is broken. Until this is fixed, I will not recommend BitDefender to any other friend or family. Especially software engineers or hobbyist programmers.

6XGate

OH!!! And the exclusion system DOES NOT WORK! I've excluded the folder containing the project (including the compiled EXE. The product still performs the same behavior regardless of whether the folder is excluded. So that requires being fixed as well. Do your engineers actually perform regressions testing on this product?

Arbiter Odie

Wait, so you're saying that it's deleting the programs you're writing in C++? :huh: That's all kinds of unhelpful.

6XGate

Yeah, I've posted code to one that was compiled with Visual C++ 2015 (14.0) from Visual Studio Code. This other one was with Visual C++ 2013 (12.0), also from VSCode. But this has happened from Visual Studio proper (Profession edition specifically, though I imagine that does not matter). I also found out that exclusions DO NOT WORK UNTIL you reboot it seems. But the other recover/allow functions just don't appear to work at all. There is just no rhyme or reason to the Active Thread detection, other than it's only happens with really simple and small programs.

Arbiter Odie

On 12/16/2016 at 8:48 AM, 6XGate said:

Arbiter Odie

Ack. I couldn't figure out how to remove the quote box, I clicked it by accident, and it was persistent in between log-out log-in. Sorry.

So basically you have to reboot your computer every time you compile a smallish program. That's not so helpful. I wonder if there's a faster way to get feedback to the team? I know the Apple support forums don't seem to be the right place to report problems either. I'll look around BDs website later, and see if I can find a problem submission form or something.