Discussion in 'other anti-malware software' started by puff-m-d, Nov 14, 2016.
Got it! Thanks as always @1PW .
You're welcome my friend. Stay safe!
Malwarebytes for Windows v220.127.116.11 - CU 1.0.1173 BETA is being pushed out.
The Threat Scan takes few minutes (Objects Scanned: 278.078 / Time Elapsed: 2 min, 3 sec)
but the time needed for a Custom (Full ) Scan (Objects Scanned: 484.847 / Time Elapsed: 3 hr, 50 min, 22 sec)
Perhaps you can please reply with answers to the following two questions.
Q1 - Did the above Custom Scan have Rootkits enabled?
Q2 - Did the above Threat Scan have Rootkits disabled?
In normal everyday operation, Malwarebytes recommends the manual Custom Scan only be run very infrequently, whereas the default scheduled Threat Scan is sufficient for most Consumer users. Malwarebytes does not recommend scheduling Custom Scans.
Q1 - Yes
Q2 - Yes
I know, that's why it was just an infrequent Custom Scan.
What surprises me it's the huge time difference between the two scans (with and without rootkits) = 3 hr, 50 min, 22 sec / 35 min, 20 sec
With Avira AV scans, the above mentioned difference is very small.
For testing purposes here is a Custom scan with Rootkits disabled =
I see where you've accomplished a significant cleanup that favorably improved the most recent Custom Scan's time to completion.
For the benefit of others, invoking MB4's baked-in rootkit module during any scan has always added overhead because of its thoroughness. Because of it effectiveness, Malwarebytes has also had the free standalone utility called Malwarebytes Anti-Rootkit Beta (MBAR) for those who do not wish to use Malwarebytes for Windows.
Both MB4 and MBAR have their own, separate, rootkit database files. MB4's default Threat Scan is optimized to scan where malware is known to exist compared to Custom Scan's much wider scans.
Again as mentioned above, enabling the rootkit module will always add an additional level of thoroughness.
Malwarebytes for Windows v18.104.22.168 - CU 1.0.1173 has been released.
Malwarebytes 22.214.171.124 (offline installer)
Malwarebytes for Windows v126.96.36.199 - CU 1.0.1191 BETA is being pushed out.
Malwarebytes for Windows v188.8.131.52 - CU 1.0.1212 BETA is being pushed out.
Note: The MB4 release version is still v184.108.40.206 - CU 1.0.1173
I can't update definitions, the program and I'm getting a message that MB can't access the licensing server x 2 machines (one with Norton, the other with Kaspersky).
I just ran a definition update, it downloaded & installed without error. I suspect they are staging and controlling who gets the new program changes and definitions to avoid overloading their servers.
After investigating this issue I found that my ISP is blocking MB IPv6 IP address. I don't know why and their level one techs couldn't tell me either. After I disable IPv6 on my machines, or in this case, use my Netgear modem / router which has IPv6 disabled, I have no problem.
I am on British Telecom, My router is their BTHH5 which doesn't fully support IPV6, it translates it down to an IPV4 address. They've started using IPV6 fully in their latest flavour router, which they won't upgrade for us as it still works. I guess I'll have to wait till it breaks, and then they'll replace it with the new one. () I hope 'the dog did it' works. "Knocked it right off the shelf she can't get to. looks almost like she hit it with a sledgehammer.". Could happen any day now. I am occasionally precognitive.
Noticed that your UPDATES last updated 2 months into the future??
It seems I'm not alone:
Malwarebytes for Windows v220.127.116.11 - CU 1.0.1217 BETA is being pushed out.
Malwarebytes for Windows v18.104.22.168 - CU 1.0.1217
Malwarebytes for Windows 4.3.0 Release Notes
Thanks @anon !
Malwarebytes is using ALL my RAM (16GB+)
Malwarebytes for Windows v22.214.171.124 - CU 1.0.1236 BETA is being pushed.
Spoiler: component package 1.0.1236
What’s New in 1.0.1236:
30 day Security Summary
Additional Enhanced Compatibility for Web Protection
Improved detection and remediation
Improved Updating functionality
Dashboard sign in forgot password (additional corner cases)
Some Issues now addressed:
Fixed: MBAM consumes all RAM if a scan scheduled to time of DST adjusting
Fixed: MWAC BSOD with Pulse Secure VPN
Fixed: Websites are still blocked using excluded browser when Barracuda Content Shield is installed
Fixed: Scheduled scan changes are not read correctly by Narrator until UI restart
Fixed: Can not set password with backslash (\) or double quotes (") in Forgot Password Wizard
Fixed: Several Upgrade Issues that occur under certain circumstances
Fixed: Several minor UI issues
FP on an old file adwcleaner.exe version 126.96.36.199 from years ago.
Yes, it is old. Nevertheless, isn't AdwCleaner now part of Malwarbytes? Don't they check their old files?
Components Version: 1.0.1130
Update Package Version: 1.0.38745
The file AdwCleaner\Version 3_0_2_3\adwcleaner.exe has the following Checksum(s)
MD5 - 04B47DEEB298AE90A0C42DEAED71F8BA
SHA-160 - 04C656F5CB00708B093B050DFCBB0D3F34E4A56A
SHA-256 - 450DE13F98DC79C3E6359CB244FAC2A6F23F848F531F5C5A3EC3B9C2AF365714
The file has been checked at VT.
None of those 7 ones I trust on this.
Separate names with a comma.