Suggestion For Problem Report/fix List

alternety

Hi, I just joined because I just bought BD 2012 based on various reviews of its' efficacy. It was highly rated for finding and fixing things. And then I started reading this forum. OMG! Will I never learn to read user forums before buying something? Current equivalent error is Acronis 2012. Seems like a bad year for software.

From what I have read, there is no way I am going to install this application until a myriad of problems are resolved. It is possible it will do everything from simply not doing what it says it should to trashing my computer. Now the problem with this statement is "how do I know when it is OK to go back into the water?" Going through the forum, reading each thread, following links to other threads, hoping for a solution, and comparing reported issues with fixes is not effective, or in my mind, practical. Certainly not an acceptable requirement before purchasing new software. The number and severity of reported problems is simply not worth the risk.

Solution for informing users and potential installers.

There needs to be a topic on the forum that covers all reported problems. This topic needs to have limited update access and maintained by Biitdefender staff or approved volunteers. The topic needs to have threads whose titles are a clear, but short, description of the reported problem. It would be best if the title included an indication of resolution. For example; open, resolved, determined to be a false problem, etc. Update version if it is fixed in a release.

In each thread, there should be a clear description of the reported problem and the release identifier in which the problem was found (e.g., BDH.2012.rel#). It should be assigned a problem number by staff. Releases acquired through automatic or manual means need to have an identifier, and an about on the installed product needs to display major and minor release designators. The title should preferable identify the release number in which the problem was fixed. the process for obtaining updates to the software needs to identify the releases available in the same consistent structure (e.g. BDH {Bitdefender home}.2012.xx).

Then, when a solution has been found, there should be a clear description of the solution. This could be a link to another thread, but really should be a cut-and-past of the solution. When the resolution is available in an update, the update release needs to be identified. It must be clear from the thread if the problem has or has not been resolved. When an intermediate software release is made, the documentation on the web site should list what problem numbers have been resolved in this release.

I spent some time looking through the web site and most of this is not happening as far as I can see. I believe it is the responsibility of the vendor to maintain this sort of information to provide acceptable customer support.

rootkit

Hi

Your feedback is appreciated, and will be directed to the appropriate team for review, to enable us to improve our support and services.

Thank you for taking the time and please do not hesitate to contact us if you need further details from us.

Take care.