Jump to content

Telos

Honorary Members
  • Posts

    806
  • Joined

  • Last visited

Everything posted by Telos

  1. What if you're infected already... second opinion scanner match-up.
  2. Prove this. There's no video documentation that MBAM protects against zero-day nor ransomware.
  3. Maybe it's just me, but v3 is worse than any experience I could have in its absence. And I'm going on faith here that it actually protects me as there has been no video documentation that v3 protects against ransomware.
  4. Major suck here. Finally, back up to post. Such incompetence is beyond words. Do you never test any of your updates, or do you just throw them out knowing you are perfect.
  5. You missed my point. What I was trying to say is that as a standalone program, the antiransomware element offered quite limited ramsomware protection. So yes it "exists" but would quickly be relegated to the dustbin if forced to stand alone.
  6. When the ransomware element was first developed as a standalone entity, it was always a weak sieve and could never exist as a standalone product. When it was rolled into v3 its weakness was shored-up by the remaining elements.
  7. This may be resolved simply by reinstalling the latest version over your current installation. Download here: https://downloads.malwarebytes.com/file/mb3 If that doesn't help please read and follow the instructions below and post back your log and we'll take a look and see what's going on.
  8. No. Only if you buy them separately. If you buy them as a package the clock starts for both with the initial activation.
  9. Can you share a screen print. This is not MBAM.
  10. You can block domains through your HOSTS file, or OpenDNS free account, and of course, MBAM will flag interceptions it finds dodgy.
  11. That is reported here: https://www.safer-networking.org/faq/bitdefender-threat-scanner-dmp/ That site seems to be down for me today (was open yesterday).
  12. That seems to rule out MBAM. This is a Bitdefender issue and appears on their support pages. You should take this Bitdefender. It seems your uninstall was not done cleanly. However... if your Webroot AV uses Bitdefender as a scan engine, then start your quest there.
  13. I would reinstall on top of your current setup with the latest version here: https://downloads.malwarebytes.com/file/mb3/ Does that help?
  14. Current 3.3 installer is here: https://downloads.malwarebytes.com/file/mb3/
  15. Sometimes a reinstall over your existing installation can fix things up. The latest installer is here: https://downloads.malwarebytes.com/file/mb3/
  16. If you do, check again later that it hasn't returned. If it does, that's indicative of a compromise elsewhere in your system.
  17. This may be resolved simply by reinstalling the latest version over your current installation. Download here: https://downloads.malwarebytes.com/file/mb3 If that doesn't help please read and follow the instructions below and post back your log and we'll take a look and see what's going on.
  18. Update to v3.3. Download and install over your current installation https://downloads.malwarebytes.com/file/mb3/ Does that help?
  19. MBAM is compatible with AV products, including ESET. If interoperability issues exist, they can easily be remedied by adding to MBAM's (and.or ESET's) exclusions.
  20. This was not MB support. Hopefully, you did not follow their advice not let them take control of your computer. If so, another clean install might be necessary It seems you did not deactivate your MBAM key between clean installs and have overrun your alotted installation allowance. As it is now the weekend, staff support is sparse, so please wait patiently until Monday for someone to help you with a key reset. Tagging @AdvancedSetup and @nikhils for support.
  21. First, this may be resolved simply by reinstalling the latest version over your current installation. Download here: https://downloads.malwarebytes.com/file/mb3 If that doesn't help please read and follow the instructions below and post back your log and we'll take a look and see what's going on.
  22. It will scan once daily at 60-day intervals. What you proposed isn't correct. Why would one stop scanning after "x" days? The Frequency and Settings section allows you to define the timeframe (Schedule Frequency) that a task will be executed, and how often (Recurrence). For scans, this translates to: Frequency = Hourly, recurrence in range of 1-48 hours Frequency = Daily, recurrence in range of 1-60 days Frequency = Weekly, recurrence in range of 1-8 weeks Frequency = Monthly, fixed setting Frequency = Once, fixed Frequency = On Reboot, fixed I agree. The wording is poor/confusing. The term "frequency" only states the units of recurrence. So by "daily" the scan will be once daily at the frequency you select. And a frequency of "hourly" only means at what hourly recurrence that you select... for example every 16 hours. (recurrence).
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.