| |ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| |_________________________________________________________________| |
| | | |
| | MDGx MAX Speed WinDOwS İTricks · Secrets · Bugs · Fixes | |
| | | |
| ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ |
| http://www.mdgx.com/ |
... Serving strictly the best tweaks to millions of readers since 1993
This web site is (a)live for > 25 years and counting... ;-/
[ http://www.google.com/search?q=false+positive+cybersecurity ]
Greetings, Fellow Computer User,
This text file is also available online:
and also as plain text/ASCII file:
Thanks a lot for your concern, I do appreciate your time.
If you're reading this, it is probably because a file at my site may have triggered a false/fake positive
Those are but false positives, same as many others of their kind.
Here is some publicly available literature on the subject from trustworthy developers, entities and vendors
you may have heard of:
- NirSoft: Antivirus "False Positive" Problems:
- NirSoft: Antivirus companies cause a big headache to small developers:
- Malwarebytes Labs: Explained: False positives:
- Sophos: How to investigate and resolve a potential false positive or incorrect detection:
- Panda Security: False positives - What are they?:
- Virus Bulletin: The false positive disaster: Anti-Virus vs Winrar & Co:
- McAfee: How to "White List" False Positives Manually?:
- VirusTotal: A first shot at false positives:
- AV-Comparatives: Spotlight on security: The problem with false alarms:
- ResearchGate: Antivirus False Positives alerts, Evading Malware Detection and Cyber-Security issues:
- ResearchGate: Finding and Solving Contradictions of False Positives in Virus Scanning:
- Infocyte: Cybersecurity 101: What You Need To Know About False Positives and False Negatives:
- LifeHacker: How Do You Know If Your Download Really Has a Virus?:
- HelloTech: Not a Virus: How to Verify a False Positive Detection:
- Wikipedia: Problems caused by false positives:
- Gizmo's Freeware: What Is A False Positive Antivirus Detection?
- Gizmo's Freeware: How to report false positives to multiple anti-virus vendors:
- Rick Strahl's Weblog: Dealing with Anti-Virus False Positives:
- Software Engineering: How to prevent my executable being treated from AV like bad or virus?
- Stack Overflow: Antivirus False positive in my executable:
This is the original (classic) standard verification designed by the anti-virus pioneers (McAfee) using a
harmless fake virus [EICAR], which mimics virus code without any of its ill effects, just by using a
particular combination of ASCII/plain text characters, which sets off the anti-virus software by detecting
a fake (false positive) malware code/file signature:
To my knowledge the files at my site are harmless, some are 10-15 years old or even older, eventually part
of executable (.exe) or Windows Dynamic Link Library (DLL) Portable Executable (PE) compiler routines used
back in those days by old operating systems (OSes) like MS-DOS, Windows 3.x, Windows 9x, NT4, 2000, XP, and
NirSoft, for example, is one of the software developers who still uses such techniques for their programs
even today, without any known harm.
Some of these executables/files constitute or are part of ancient programs containing very old DOS/MS-DOS,
Win31 or Win95 style 16-bit or 32-bit code, and do not infect anything, only mimic by accident or by
coincidence the structure of some old/obsolete/outdated viruses/trojans found in some ancient databases.
Many such old programs contain similar harmless code, but somehow, even today, they still appear as
malware/trojans/viruses (rogue code) when scanned.
Many developers/businesses/providers/vendors/entities have eventually updated their databases to recognize
such false positives (white listings), but unfortunately some have not (yet), and some still refuse to add
such old/obsolete programs to their lists of false positives, mostly because they are afraid of losing
business, popularity, fame and/or being sued in a court of law for liability. ;-(
Microsoft Windows users:
In case you have any concerns, please submit respective executable(s)/file(s)/archive(s) to Microsoft
Windows Defender Security Intelligence (WDSI) for analysis, just to be safe:
and also to any other trustworthy entity, because you should have them scanned by at least 2
That's why VirusTotal, for example,
uses more than 60 [!] such entities/providers/vendors.
I usually ask the gracious contributors who send/recommend me files for public "consumption" to check them
for all possible "infections", and so do I before installing/sharing/testing/uploading/testing/using them.
I do upload and post all the files at my site only after successful anti-virus scans from multiple
Here are the safety reports for my entire web site [mdgx.com] from trustworthy/accredited entitites:
Many such files are meant to be used with older/obsolete Operating Systems (OSes) and Environments like
DOS/MS-DOS, Windows 3.x, Windows 95/95 OSR2/98/98 SE/Millennium Edition (ME)/2000/XP/2003, OS/2, Linux and
reside at my site for longer than 10-15 years without causing any harm, devoid of complaints as far as I'm
aware, and downloaded & used daily by many people all over the world.
Also, everything at my site is scanned on a daily basis using updated malware/virus databases by my root
domain web site host provider,
one of the best in the business.
GreenGeeks safety reviews [one reviewer rated it no. 5 in its category]:
Just in case you don't feel comfortable using something/anything originated from my site, please
delete/uninstall it/them completely from all your computers/devices/storage units.
Many thanks for taking the time to read this boring tirade in its entirety.
[formerly known as AXCEL216]
owner, webmaster + editor of