Ransomware Remediation Missed, Disappeared or is a Glitch??
i'm new on this forum and surprisely the new build of Bitdefender 22.214.171.124 has missed the Ransomware remediation on the protection tab or is a glitch (moved in the right causing impossible to disable or adding/managing exclusions and also enabled the feature)
Note: the image is for the spanish version of Bitdefender because in the spanish forum only have Business topics for endpoint versions. And also i'm not talking so much english but using the translator for english->spanish.
17 minutes ago, Sinus said:
Doing a clean install (removing BD Total Security and then installing it again) should fix the problem.
Might not fix the problem with clean install, it is a problem with language version of bitdefender (spanish version), also if i clean install the program, the exceptions will delete after clean install and the ransomware remediation is disabled and probably still the same image after clean install.0
how to contact with technical support. Using with the program or what?
Photo example (spanish version):0
Anyway, I'm sending technical support (in Spanish) about the problem and waiting for my ticket number to be resolved.
I am also waiting if other users have the same problem because of the failure (or BUG). The English version appears normally, but some versions in other languages (some spanish or non english users) that are not in English are also causing problems when configuring the ransomware remediation (activated and not activated) and that I hope you can solve in the next build version of Bitdefender (Antivirus Plus, Internet and Total Security)0
Issue has been identified and will be solved during the next product updates. The situation occurs only if you install the software in Spanish or Czech. English is unaffected.0
2 hours ago, Marius G. said:
Issue has been identified and will be solved during the next product updates. The situation occurs only if you install the software in Spanish or Czech. English is unaffected.
Thanks. I will wait in the next update.0
Issue fixed in build 126.96.36.199. Build is present on both reinstall and update (update is not released to 100% of the market yet).0