Anti-Virus/Malware/Security Software and “False Positives”
Please note that our software here at FoolishIT.com (as well as software from other reputable vendors such as Nirsoft.net) will trigger a certain amount of ‘false positive’ alerts with various anti-virus or anti-malware software. This is to be expected depending on the nature of the product, and tends to happen with software vendors that create powerful tools (like some of ours which are used by PC technicians in the repair industry.)
This causes major headaches especially for small developers like ourselves (terminology borrowed from Nir Sofer’s blog post from 2009) who do not have the notoriety, influence, or gangs of attorneys waiting and working to ensure our reputation isn’t damaged by careless Anti-Virus/Anti-Malware software vendors. Often aggressive heuristics and even definition releases flag our PC technician software in particular, which is very powerful with many capabilities and features that do access and alter Windows files and configurations but of course only for repair (and tweak) purposes.
Scroll to the bottom of the page for external links and resources!!!
The first type: “Infected”
Often these ‘false positives’ directly state the file is infected, typically with something ‘generic’ in the name. Many times this is due to the software compression applied to the executable (program) file, in order to reduce file size and perhaps to help make the software “portable” (meaning it doesn’t require ‘installation’ on a PC, but can run from wherever you downloaded it to.)
Tools used to compress executable files (aka ‘exe packers’ or similar) can greatly reduce file size, saving space but also internet bandwidth in distribution efforts, ultimately reducing overhead costs. They can also obscure source code that is visible (using the right tools) inside the program, providing protection against decompilation and other techniques of ‘reverse-engineering’ the software, which software crackers would use in theft of the product, such as ‘piracy’ (through usage and/or distribution) but also with theft of the intellectual property itself by direct source code reproduction.
Of course, the above also makes it more difficult for an Anti-whatever vendor to make a determination about the software’s intent – more often than not they don’t care to properly unpack and examine the executable, but rather mark it as malicious simply because that type of compression is detected.
The second type: “Potentially Unwanted” (or similar)
Another ‘false positive’ is what the Anti-Virus or Anti-Malware vendors DO NOT consider a ‘false positive’ but rather an intentional but ‘potentially unwanted’ program (or using similar terminology) while the text DOES NOT mention an ‘infection’ in any way. The alert box presented to the user also generally appears as if it were an infection however, using the same BOLD/RED text or other scheme as they do with real infections.
The problem is that some software, while NOT being used maliciously, COULD be used maliciously, depending on the user of such software… The Anti-whatever software doesn’t know that YOU are trying to USE it, it just knows that it could be used by an attacker maliciously and without your knowledge.
Almost always Anti-whatever vendors will make the default (or ‘recommended’) action to stop/block/quarantine/remove the software, even when it is quite harmless. This can be bad for a number of reasons, such as by letting the Anti-whatever do it’s thing to ‘protect’ you, it just might damage the legitimate installation beyond a clean removal, possibly impacting your operating system negatively in some way. Depending on the software, it may be better to uninstall it the proper way.
There are really too many variables in the determination above to explain here, so don’t take our word for it because we aren’t giving it (we don’t know what you’ve downloaded either) but we know that the Anti-whatever software isn’t taking those variables into account, in fact they ignore them completely. Only an informed ‘you’ can and should make that decision! So if you are unsure, think about it, search the web carefully for more information, and finally call a local professional for help if that doesn’t work.
Either way it is always better to pay attention to the terminology and make your own informed decisions!
If you are receiving a detection with our software:
We’re not saying our software is immune to infection, rather due to the nature of our software it is often flagged as malicious, or “potentially unwanted” programs. Rarely do security software vendors explain what they consider “potentially unwanted” to their customers, specifically not differentiating this category properly from actual threats, which can be seen in various indicators and reports from within the program’s interface. It is also inevitable that some real threats are introduced to these “potentially unwanted” categories, for one reason or another, creating further confusion.
If you believe our software is potentially infected, please visit www.VirusTotal.com and upload our software for review. Please understand however that the results are not fact, and you will likely see false positives here! VirusTotal.com (now Google owned) is a mass virus scan engine designed to use a large variety of security software scanners from various vendors, and it is the very thing we’re talking about here! As such, it is important to realize that if one should not use the results of a the scan to determine an actual infection. The results are however a good indicator, as a high number of detections from vendors may reveal an infection, whereas a low number suggests a false positive.
We also strongly encourage you to consider submitting a “false positive” report to the vendor. Typically the software allows submission of the detected samples along with gathered information for review. If this option isn’t available, please fill out a false positive submission with the vendor. You can find links to various vendors’ false positive submission forms below.
For large security software vendors, it may take many false positive submissions before they are noticed and can invest their time and resources to investigate. Additionally, new versions of the same software often trigger the same or completely new detections, so they must be submitted again in the same way that previous versions of the software were reported.
Simply put, do not assume that someone else did it. Numbers matter, so the more people who help in submitting false positives, the sooner they can get these issues resolved. Your help will always be appreciated in this effort!
Known False Positive Submission Links:
If any information in the list is incorrect, please let us know!
- Avast (email only)
- AVG (20MB file limit, else use this email and compress it with a password.)
- Avira (or this email)
- Bitdefender (also this email, and the Emsisoft forum is another option (free account/login required.)
- ClamAV (or this email; uses Immunet Protect definitions)
- Comodo (or this email)
- Emsisoft (or the Emsisoft forum)
- Kaspersky (or this email)
- McAfee (email only)
- NOD32 (email only)
- Panda (or this email)
- Sophos (or this email)
- Trend Micro
- Vipre (or this email)
- Windows Defender (or this email)
- If your product is not listed here, a more comprehensive list with links is available on techsupportalert.com.
* Please realize that any request or submission does not guarantee any vendor will fix a false positive. As an example: some of our software has the capability of retrieve the Windows product key, used to install Windows on a PC – which could be used for legitimate or illegitimate purposes. For this reason certain detections will likely never be removed, though some vendors may opt to downgrade their classification of the ‘threat’ to their ‘potentially unwanted programs’ category. Nir Sofer’s blog post from 2009 shows us this isn’t even close to being a new phenomenon, so as we constantly fight these battles with “big a/v” we’re not expecting to win the war anytime soon…
d7x and Tweaky – Set Time Zone issue with Windows 11 (UPDATED Aug 9th 2022) UPDATE: this issue has been resolved in d7x v22.8.9 and...