Jump to content

tend2it

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tend2it

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Why can U edit posts? Should read ... doing normal activities (web browsing, YouTube, gaming, Discord, etc.) with NO freezes nor performance issues.
  2. So far, so good running the 1.0.527 BETA build on 2x Win7 machines (Enterprise and Pro) for about 48 hours now ... doing normal activities (web browsing, YouTube, gaming, Discord, etc.) with freezes nor performance issues ... Auto Updates is turned on ... This is looking like a winner !
  3. This banner can also be used as a News feed on status/fix confirmation/etc. ... but wouldn't be helpful for us who rolled back to a previous version ... unless you also push an updated version of that older version with this update feature.
  4. Perhaps the best way to directly contact users is a software update that pushes a warning Malwarebytes Main Graphical User Interface (that displays options to run) which can display a Big Red Banner (at startup or Notification if system is not restarted) clearly stating the Issue that may affect certain computers running Win7 and current workaround info link.
  5. Glad battle.net updater was repeatable on your internal test environment ... hopefully, you can get to the bottom of this very soon. I actually rolled back my son's system to August 2018 using SW to backup/restore because of the random freezes. He had to re-install/update everything past Aug to bring the system up to present. However, since MB was not known to be the cause, Its auto-update component was still active and installed the latest updates. This of course made it appear that the backup was also freezing. Very misleading issue indeed, as I was thinking perhaps a HW component
  6. When did the freeze first start occurring? Towards the End of Nov/Beginning of Dec. They were random ranging from 1-2 times a week (at start) to once a day (middle Dec) to multiple times a day (end Dec/beginning Jan) What were you doing on the computer immediately prior to the latest freeze? Trying to run Blizzard's battle.net updater (see below). Did you notice anything significant occur around the time of the latest freeze (e.g. AV notification, application crash, etc)? No system/application MB related logs before/after system freeze, no blue screen crash log. Keyb
  7. My son's computer has been experiencing random freezes since Dec ... Tried a troubleshooting option with MBs. -> Created exceptions for web access applications for both the battle.net exe and launcher and also the Overwatch exe and launcher to test if this would make a difference The Overwatch updates still froze. Once uninstalled MBs, updates succeeded. Reinstalled MB, ran Overwatch, it froze in the loading screen. Random freezes did happen (observed by son): * as MB does the rootkit scan just after the windows login screen starts the login process * while
  8. Yes, Battle.net updater (specifically Overwatch) will repeatedly reproduce the crash on my system ... if MB wants a test case to use. I posted some info to Blizzard Technical Support forum after I discovered the bleeping computer article ... https://us.battle.net/forums/en/bnet/topic/20770537321#post-11
  9. I've been troubleshooting this issue since Dec on my son's z800 workstation. Random freezing/crashes and more frequent ones of late especially when running battle.net to update Overwatch (which resulted in an instant repeatable freeze). Was worried I had some hardware failing with no clue on what it may be. Since MB had that infamous Jan 2018 system killer update, any system related crashes put MB on the possible cause radar. As soon as I clean uninstalled MB, the freezes went away. Forced to do Hard Resets is not good for the HDD. After much googling, I found a topic that pointed b
  10. Same here on multiple machines. Version 3.4.5 ... Maintenance mode shouldn't break it ... they should send out a general message the application can display then if that is the cause.
  11. All 5x computers back up and running. The problem is related to MWBs taking 99% of Physical Memory, which essentially prevents you and your computer from doing anything, appearing to freeze or lock it up. Real-Time protection OFF (without ability to turn back on) and sometimes internet connectivity lock-out preventing License checking are indicators as well. This is what I did to get things working again: 1) Reboot (via Windows Restart) or Hard Reboot (if system is non-responsive, hold down power button for a few seconds) to get back into the logon screen. 2) As soon as th
  12. I had that problem along with the Mem leak after the update ... quitting MWBs and restarting fixed it.
  13. Thanks ... but it is already disabled to off as part of the license access problem. One laptop somehow got updated ... I Checked For Updates several times via the MWB System Icon, the last time at 99% Physical Memory lockout, let the system hang for 10-15 minutes while the 1% allowed the update to possibly work, then mysteriously, on the next reboot, MWB was updated to the patch and the problem was fixed. Why is there no physical Check For Updates button in the GUI?
  14. Have a major problem with two of my older Win7 laptops: On bootup, I immediately get to the system tray Malwarebytes icon and click check for updates, and bring up the Status Panel to look at the current update installed. The computer gets to 99% Physical Memory usage before performing the update and completely locks up the computer. I've tried on startup, starting a scan that automatically checks for updates from status panel or turning off all protection features, forcing check for updates via system tray icon, and several hard reboots to no solution. 99% Physical Memory kills any pr
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.