Instructions for
- configuring Windows Defender to consider a DXLab application to be safe
- directing Windows Defender to restore a DXLab application that it erroneously quarantined
- recreating a DXLab executable that Windows Defender erroneously quarantined or deleted
- disabling Windows Defender
are provided in the first section of
<>
73,
Dave, AA6YQ
As stated in Note #1 in
<>
I submitted Commander to Microsoft's "Submit a file for malware analysis" page
<>
with "Microsoft Defender Antivirus (Windows 10)" as the selected security product to scan the file.
The "Client" and "Cloud" results at the time (June 10) were both "no malware detected", but when I check the status today, the
"Client" status is still "No malware detected", but the "Cloud" status has changed to "Trohan:Win32/Azden.Blcl".
As shown in the above release note, all 80 online virus scanners accessible via the "Virus Total" and "Jotti" web sites found no
malware in Commander 14.6.2.
Windows Defender is clearly broken. If you choose to continue using it, you should expect it to quarantine your DXLab applications
from time-to-time.
Control your computing environment, or it will control you!
