Replies: 3 comments
-
|
Repeated twice, same result
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
test6 and test7 changed to no dictation
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
test 6 detected in version1.421.1222.0
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
More and more lately, SeleniumVBA has been flagged with antivirus false positives. This is not surprising given the complexity and functional breadth of our code. Multiple times in the past I've experimented by randomly removing/changing various code blocks, but it has been difficult to isolate the problem(s) on a one-off basis. Additionally, it seems that satisfying Window's Defender heuristics is a moving target, as there are times when the EXACT same code is fine one day, and then flagged on another, and then back to being ok later. Additionally, the MS Excel version of SeleniumVBA can be flagged, but the EXACT same code in MS Access is ok.
I think it's time to try a more structured longer-term approach. From v6.2 onward, we will test av false positives in this GitHub folder. There I have created several functionally "reduced" test versions of SeleniumVBA.xlsm. To start with, I've removed/replaced some functionality that I know MalwareBytes real-time protection does not like but will test other code changes in the future as well.
The table below summarizes the functionality removed from each test:
Below is a table for tracking false-positives over time - I will update this table with hopefully help from some of you going forward:
If you have issues downloading and/or using the latest release version, then please try one of the test versions, and then report your experience in this discussion thread so that we can track and hopefully determine a strategy that reduces the number of false positives in the future.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions