MoxieMomma Posted September 22, 2015 Hello: This is a new F/P detection with your current database (the MBSB program is perfectly safe and has been on this system for years). SUPERAntiSpyware Scan Log https://www.superantispyware.com Generated 09/22/2015 at 06:39 AM Application Version : 6.0.1204 Database Version : 12077 Scan type : Quick Scan Total Scan Time : 00:00:27 Operating System Information Windows 7 Ultimate 64-bit, Service Pack 1 (Build 6.01.7601) UAC On - Administrator Memory items scanned : 689 Memory threats detected : 1 Registry items scanned : 44667 Registry threats detected : 0 File items scanned : 8135 File threats detected : 1 PUP.Mindspark/Variant C:\PROGRAM FILES (X86)\MALWAREBYTES SECURE BACKUP\NEWTONSOFT.JSON.DLL C:\PROGRAM FILES (X86)\MALWAREBYTES SECURE BACKUP\NEWTONSOFT.JSON.DLL ============ End of Log ============ Please fix. Thanks, MM Share this post Link to post Share on other sites
MoxieMomma Posted September 23, 2015 Bump. (>24 hours later, new database version, F/P still detected) Please fix. Thanks, Share this post Link to post Share on other sites
GuiltySpark Posted September 23, 2015 Hi MM Can you use the inbuilt FP reporter. Thanks Share this post Link to post Share on other sites
MoxieMomma Posted September 23, 2015 Hi MM Can you use the inbuilt FP reporter. Thanks Sorry, no idea where to find that in the GUI. EDIT: I am confused. Your forum sticky (referring to an old program version in 2012?) mentions a "report false positive" button. Your current program GUI offers a "mark this item as good" button -- this would seem to be a means of creating an exclusion/whitelist, NOT reporting a F/P? IOW "mark this item as good" does not mean the same thing as "report false positive". If, in fact, that is the "inbuild FP reporter", please clarify. Please advise. Thanks, Share this post Link to post Share on other sites
SAS_support Posted September 23, 2015 Hello MoxieMomma, Thank you for bringing this to our attention. We have disabled the offending definition, and the afternoon release today (will be version 12081) should correct this issue. Regards, SUPERAntiSpyware Customer Support Share this post Link to post Share on other sites