I just downloaded Malwarebytes Anti-Malware on my system for the first time and was surprised by by Norton product (NIS 2010). It didn't know what it was and asked me what I wanted to do. It said that I was the very first Norton User to download that kind of file. I told it to Run the program since I knew what it was.
Very strange considering NIS 2010 has been out for a while...
It sounds like the average Norton user doesn't know about some of the third party malware detecting software utilities out there.
Where did you download the file? From http://www.malwarebytes.org/?
hi !
i once tested Fortinet, it warned me about WinPatrol, told me it was suspicious...
I downloaded Malwarebytes from their website (Malwarebytes). I use that on all my client's computers when they complain of slowness and etc. and it does a pretty good job at detecting malware. I used Malwarebytes when KIS 2010 was letting in large amounts of malware without my knowledge. When I downloaded a 90-trial of Norton IS 2010, Norton's virus scanner found quite a few hidden Trojan droppers and etc. I was not happy after that scan.
Many in the Norton community use Malwarebytes.
If you still have the downloaded file, right click it and choose 'Norton File Insight'. How many now does it say have used this file?
Norton may not have been able to contact their servers when you downloaded the file.
File: mbam-setup-1.46.exe
Now Norton is saying different than it did yesterday. It is saying now that Hundreds of Thousands of users in the Norton community have used this file.
It's also saying that it's Norton Trusted.
I never thought of it not being able to contact their servers to see if the download was safe. Even though my wireless was up and running, their servers could have been down. Very true!
You may like to read this- it provides good insight into how Norton Insight works.
Norton Insight: A solution to performance improvem... - Norton Community
It has happened to me once or twice with Download Insight but straight away I used File Insight and it was able to reach the servers.
It could be caused by Norton servers being down (unlikely, in my opinion), weak internet connection (possible in my case), Norton not being able to detect proxy settings in that split second (if any), a bug in Norton.
Quote