I have a support ticket # OZG-211-85755 in regarding this issue for over a week now with no response, so I figured I'd post this here.
Avast has all of the sudden report jsbvt220.dll as malware and moves it to the chest, the problem is, this is NOT malware, it is part of the software we run to operate our entire business. I have report this as a false positive at least a dozen times but nothing has changed.
I now have a "workaround" for this issue, but still need help in resolving the issue.
Out of the 20 or so computers we have here, most peoples worked by just setting up a global exclusion to stop the dll file from being scanned, but randomly in the morning when a few (2-3) people come into work in the morning and open the program, avast blocks the dll file and I have to restore it and reboot their machine for the global exclusion to work again, even though it shows up in the exclusions list, and this is a daily occurrence for at least one person, even though all of the computers are managed under the SOA client running on the server and they are all connected and all the settings are updated instantly when I change them around.
Just to give you an idea of what all I have setup just to get this program to function again:
I have jsbvt220.dll and jsbterm.exe setup in exclusions & in global exclusions, jsbterm.exe is the program executing the dll file, so I figured I'd exclude both of them.
In the filesystem shield I have the scan DLL files when loading option turned off, and I have the jsbvt220.dll & jsbterm.exe in the filesystem shield exclusions as well, I have all of the actions for Virus, Pup, and suspicious set to ask instead of move to chest.
As of this morning, with all of the settings above in place, the program seems to be working for everybody, but I feel like all of these settings are creating a security risk, is there anyway to figure out and fix this issue, as jsvbt220.dll is not a malicious file, at least not with the software we are using.
