Jump to content

Search the Community

Showing results for tags 'ram usage'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Malwarebytes News
    • Beta Testing Program
  • Malware Removal Help
    • Windows Malware Removal Help & Support
    • Mac Malware Removal Help & Support
    • Mobile Malware Removal Help & Support
    • Malware Removal Self-Help Guides
  • Malwarebytes for Home Support
    • Malwarebytes 3 Support Forum
    • Malwarebytes for Mac Support Forum
    • Malwarebytes for Android Support Forum
    • Malwarebytes for iOS Support
    • False Positives
    • Translator Lounge
    • Comments and Suggestions
  • Malwarebytes for Business Support
    • Malwarebytes Endpoint Protection
    • Malwarebytes Incident Response (includes Breach Remediation)
    • Malwarebytes Endpoint Security
    • Malwarebytes Business Products Comments and Suggestions
  • Malwarebytes Tools and Other Products
    • Malwarebytes AdwCleaner
    • Malwarebytes Junkware Removal Tool Support
    • Malwarebytes Anti-Rootkit BETA Support
    • Malwarebytes Techbench USB (Legacy)
    • Malwarebytes Secure Backup discontinued
    • Other Tools
    • Malwarebytes Tools Comments and Suggestions
  • General Computer Help and Security Updates
    • BSOD, Crashes, Kernel Debugging
    • General Windows PC Help
  • Research Center
    • Newest Rogue-Ransomware Threats
    • Newest Malware Threats
    • Newest Mobile Threats
    • Newest IP or URL Threats
    • Newest Mac Threats
    • Report Scam Phone Numbers
  • General
    • General Chat
    • Forums Announcements & Feedback

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Location


Interests

Found 4 results

  1. In the early morning of Saturday, January 27, 2018, a faulty Web Protection update was released which caused a connection issue for many of our customers. As a side effect of the web protection blocks, the product also spiked memory usage and possibly caused a crash. We triaged the issue quickly and pushed a protection update on Saturday, January 27, 2018 at 10:48a PST. The affected products were Malwarebytes 3 Premium, Malwarebytes Management Console (MBMC), and Malwarebytes Endpoint Protection (aka Malwarebytes Cloud Console). Malwarebytes for Mac, Android, AdwCleaner, Incident Response and Breach Remediation were not and are not affected. For a complete description and root cause analysis please click here. Please note endpoints were not affected if they were turned off before Saturday, Jan 27, 2018 and then were not turned back on until after Saturday, Jan 27, 2018 at 11am PST. For affected endpoints, this thread is intended as recovery guidance. Guidance below applies to home users and/or Malwarebytes 3 Premium users. If you're a corporate user, click here for details on how to recover your systems. If you are not experiencing issues and/or are using Update package version 1.0.3808 or higher, you do not need to do anything. For home users and/or Malwarebytes 3 Premium users Restart PC - note it may take up to three restarts after the update to stabilize the system Verify you have Update package version 1.0.3808 or higher Open Malwarebytes Click Settings, then About tab Look for "Update package version 1.0.3808" or higher In most cases, 1-3 restarts will solve the issue. If after the restarts you're still experiencing high RAM usage and/or Web Protection is not starting, please continue below. If restarting does not solve the issues, please download and run MB-CLEAN Download MB-CLEAN Close all open applications Double-click and run mb-clean-3.1.0.1031.exe A prompt with an option to clean up the system will appear: click Yes Yes - will proceed with backing up the license key (Malwarebytes 3.x only) and initiating the cleanup process Once the cleanup process is completed, a prompt will appear: Yes - will proceed and post reboot you will be prompted to continue with the downloading, installation and activation of latest version of Malwarebytes 3 No - will exit the utility and you will not be prompted (post reboot) to download, reinstall and re-activate (not recommended) We recommend rebooting immediately. Additionally, stopping at this step is not recommended and will most likely not resolve your issue(s). Upon reboot, a prompt will appear: click Yes Yes - will download, install and activate the latest version of Malwarebytes 3 No - will exit the utility and Malwarebytes 3 will not be downloaded, reinstalled or re-activated (not recommended) Verify you have Update package version 1.0.3808 or higher Open Malwarebytes Click Settings, then About tab Look for "Update package version 1.0.3808" or higher If the above does not solve your issues and you're a home user and/or Malwarebytes 3 Premium user, please start a new topic.
  2. In the early morning of Saturday, January 27, 2018, a faulty Web Protection update was released which caused a connection issue for many of our customers. As a side effect of the web protection blocks, the product also spiked memory usage and possibly caused a crash. We triaged the issue quickly and pushed a protection update on Saturday, January 27, 2018 at 10:48a PST. The affected products were Malwarebytes 3 Premium, Malwarebytes Management Console (MBMC), and Malwarebytes Endpoint Protection (aka Malwarebytes Cloud Console). Malwarebytes for Mac, Android, AdwCleaner, Incident Response and Breach Remediation were not and are not affected. For a complete description and root cause analysis please click here. Please note endpoints were not affected if they were turned off before Saturday, Jan 27, 2018 and then were not turned back on until after Saturday, Jan 27, 2018 at 11am PST. For affected endpoints, this thread is intended as recovery guidance. Guidance below applies to corporate customers using the on-premise Malwarebytes Management Console (MBMC) as well as corporate customers using the cloud-based Malwarebytes Endpoint Protection (aka Malwarebytes Cloud Console). If you're a home user and/or Malwarebytes 3 Premium user, click here for details on how to recover your systems. For corporate customers running the on-premise Malwarebytes Management Console (MBMC) In the Malwarebytes Management Console, edit the Policy and disable real-time protection Once real-time is protection is disabled and your clients can communicate, highlight the endpoints on the Client tab and click the Update Database button at the top. This should fix it for most endpoints. If any endpoints fail to get the update, you will have to force an update. This can be done locally on the endpoint or remotely over the network. Locally on the endpoint (logged in to the machine). You can point your endpoint users to do this themselves: Download and execute MBAM Rules Offline Updater Reboot the computer Remotely over the network Make sure your machine is on a non-blocked IP (i.e. 10.x.x.x or 192.x.x.x). Blocked IP ranges are from 128.x.x.x to 191.x.x.x. *NOTE* It is recommended to not use your MBMC server for this task Download the following script and extract it to a folder on your computer Create a file named hostnames.txt in the same folder, adding one IP per line for each of your endpoint IPs. You can export a list of IPs with the faulty update from the Management Console (sort by update version, select affected ones, copy, and paste into notepad). If your internal DNS is not on a blocked IP range, you can feed hostnames.txt with hostnames instead of IPs Edit the script and type in the *LOCAL* admin username and password for endpoints (i.e. NOT the domain admin) in the first 2 lines Run the batch file, which will delete the faulty database file and schedule a reboot in 30 seconds Once all the machines are updated, turn on real-time protection in the Management Console Policy settings. If the Management Server SQL database grows heavily and takes up too much space, feel free to truncate the contents of the TBL_ClientSecurityLog and TBL_ClientSystemLog SQL tables. Detailed instructions can be found in this document. IMPORTANT: this will remove ALL detection history and is irreversible. For corporate customers running the cloud-based Malwarebytes Endpoint Protection (aka Malwarebytes Cloud Console) In the Malwarebytes Cloud Console, go to Settings -> Policy and disable Web Protection and Self-Protection (if enabled). Do this for all the Policies On the Endpoints section, choose "select all" and choose "Check for Protection Updates" from the Actions button. This should fix it for most endpoints. If any endpoints fail to get the protection updates, you will have to force an update. This can be done locally on the endpoint or remotely over the network. Locally on the endpoint (logged in to the machine). You can point your endpoint users to do this themselves: Login to the machine and start a scan by right-clicking on the Malwarebytes traybar icon. This will force an update and fix the issue. Cancel the scan and reboot the machine. This should fix the problem in most cases. If the above doesn't work or the machine is unresponsive, download mbep-fixer.exe to your Desktop. If you want to deploy this over the network using SCCM or other similar platforms, you can use instead use mbep-fixer.msi. Execute mbep-fixer.exe. You will need to execute this as admin. Reboot. Remotely over the network Make sure your machine is on a non-blocked IP (i.e. 10.x.x.x or 192.x.x.x). Blocked IP ranges are from 128.x.x.x to 191.x.x.x. Download the following script and extract it to a folder on your computer Create a file named hostnames.txt in the same folder, adding one IP per line for each of your endpoint IPs If your internal DNS is not on a blocked IP range, you can feed hostnames.txt with hostnames instead of IPs Edit the script and type in the *LOCAL* admin username and password for endpoints (i.e. NOT the domain admin) in the first 2 lines Run the batch file, which will delete the faulty database file and schedule a reboot in 30 seconds Once all machines are updated and connecting correctly, go to the Cloud Console, Settings, Policy, and enable Web Protection and Self-Protection again. If the above guidance does not help and you are a corporate customer, please contact corporate-support@malwarebytes.com for further support.
  3. Admittedly MBAM Fessed Up and got fix out fairly quickly though not quick enough to from having to pay a BoxAid.com tech $70.00 to figure it out and install the new update. And now I have 3 other machines to do the same thing myself. I don't hear anybody offering to credit us for a month's worth of usage. Oh well, my 70 bucks just grew wings. C'est la vie
  4. I've notice a few issues with MB 3.0, one is that when you open it; it does not open to the desktop? it opens to the tray and it takes about 30 seconds of clicking on it to get it to open to the desktop?? it then reports that updates are current even when they aren't? you have to click 'check for updates' and it will proceed to download updates then report they are current? so it seems it does not check the updates validity when opened and just reports its up to date.. ...now for my main concern, when scanning my SSD it uses 100% CPU and 90-99% RAM..? soon as I pause the scan the usage drops, now i can expect 100% CPU but not 100% RAM of 8GB..? that sounds like a memory leak to me? I know SSD's are fast and it was scanning at 180MB/s in some cases, but surely MB should delete the file from RAM after its been scanned and is clean? meaning the RAM usage should never be over what MBAM uses and maybe 1-3 files its scanning any advice will be gratefully appreciated thanks
×

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.