Jump to content

AnotherConcernedCitizen

Honorary Members
  • Posts

    95
  • Joined

Everything posted by AnotherConcernedCitizen

  1. I've run into this before. The problem (in my case) is that once you've provided admin credentials to perform the uninstall/repair operation, things that are configured to run after a reboot apply to the admin account. After reboot, if you auto-login, or log into to user account, those things don't happen. Log out & log back in as admin and the re-installation will execute. Give that a try.
  2. As a counterpoint, I'm running Win 7 Ultimate SP1 x64 / Avast Premier (latest/fully armed) / MBAM (latest/fully armed), with no signs of conflict. On average, both MBAMService / AvastSVC typically using < 1% CPU each, according to Process Explorer. I've been watching closely since the CU 1.0.527 was installed.
  3. I started out running an early release of 1.0.527 last night with all Avast Premier shields disabled. Re-enabled this morning. No problems either way. This freeze has never been a conflict between MBAM & [any A/V Product]. The freeze happened without Avast installed (tested/verified ~Dec. 8 for Devin).
  4. While I agree with the concept of some sort of alert system, and that the 'machinery', in part, might already be in place, I also anticipate the flood of users slamming this forum/MBAM support to determine if an alert is real, or some sort of 'attack'. I hope they can ultimately arrive at a solution acceptable to all parties involved, although I doubt it'll be as straight forward as most propose.
  5. Correction... the offending string is 'amp;' sans '&', but you probably knew that.
  6. I suspected that was possible, but these are the only such HTML > text emails I receive that pose an issue so I figured I'd follow the 'contact us' instruction. Guess I'll live with it. Thanks for the response.
  7. Sorry to offend guys... not my intent. I'm sorry. I 1st reported this on ~Dec 7... 2nd such thread IIRC, where I determined (& shared) that disabling Web Protection mitigated the issue. I have been following all subsequent threads closely since. Even when there are multiple discussions on the same subject, most don't take time to read/understand what's going on. Many just go straight to the end & post to vent when a simple '+1' might suffice. It doesn't help. The MBAM folks are aware & have asked for input from all who are willing. If you want the problem fixed, putting your effort there would be more constructive.
  8. Maintain perspective. I'm referring to the scope of their deployment, not either of ours. If the problem were as widespread as you make it seem, this forum/reddit/et al, would be melting down. AND it would have been fixed by now. In either case, it's not... but I trust they are working hard. (God, I sound like some of the fanbois on other boards... kill me now! B^).
  9. The problem is: - only a TINY percentage of the user base are having the problem. - so far, they have been unable to reproduce it in their labs... the 1st step in solving a problem is to understand it. I'm reasonably confident that they are doing a great deal behind the scenes to get this resolved. They've offered 2 options to mitigate the issue until then. Choose one & be patient.
  10. It's an old post, but bad links in notification emails have been bugging me & this offered no resolution. I read mail in plain text, rather than HTML (old school-ish quirk?) & when I use the provided link, I get: Sorry, there is a problem We could not locate the item you are trying to view. Error code: 2S136/C By comparing the email with the 'copy link location' from the actual post, I see that '&amp;' appears in the former, but not the latter. By stripping it from URL from the page above, the intended post loads. https://forums.malwarebytes.com/topic/240530-another-windows-7-x64-freeze-after-the-10508-update/?do=findComment&amp;comment=1292174 Short of (ugh!) conformity, is there any recommended resolution for those who eschew HTML email? TIA
  11. https://forums.malwarebytes.com/topic/241223-malwarebytes-for-windows-and-windows-7-freezelock-up/
  12. I was with you right up to the upload aspect. I can reliably repro the freeze in minutes by starting 6 WMC HD recordings from a network tuner... download only. Pretty convinced it's any ~heavy network traffic & a speed test would certainly qualify. I usually had a browser (FF) open when testing, but had been thinking it was incidental?
  13. Thanks for the additional detail. I'd had https://haveibeenpwned.com/ bookmarked since the Linked In breach. Just added https://haveibeenpwned.com/Passwords to my list. None of my current, or recent past passwds crop up. Still, it's wise to occasionally test one's exposure.
  14. Based on my own (sample-of-one B^) Windows 7 Reliability History , my bet would be on 'No', although realtime AV/AM tools historically tend to cause such issues. I've run Avast Premier/MBAM Premium side-by-each for years & with the exception of the occasional update-induced 'feud', I rarely see that sort of issue despite the amount of functional overlap between the 2. I personally subscribe to the 'layered defense' model.
  15. Not trying to hijack, just curious... what if the hacks listed don't involve any entity I've had any direct dealings with. Aside from the long ago Linked In beach, they all SEEM to be third party data collectors (in my case) & e-mail passwords are regularly changed. How would one determine what direct affiliation leaked info to the 'collectors'? Possibly an address in someone's address book/email distribution list alone led to an appearance in breach data?
  16. While user frustration is understandable, the expectations are not. Like you all, I expect this sort of software to quietly run in the background & do its job, but... - The underlying code is, no doubt, complex. - The matrix of supported OS/hardware/installed software combinations is VAST, & testing is only as good as volunteer beta testers/internal teams can manage prior to releasee. Even MS, who has used its user-base as beta testers FOR DECADES, cannot guarantee an "Aw SH*T" doesn't escape to the field... EVER. When was the last time you got an e-mail from MS about a bug in the wild? What I suggest (based on experience, including the last MBAM/Avast conflict): - Disable automatic PROGRAM updates & opt for a notification instead. - Resist the urge to immediately update... give it some time & check this forum (obvious place?) for reports of 'bad things'. - When you DO decide to install an update, you now have a specific time frame if/when said 'bad things' start happening. You will know exactly (well, almost) what caused an issue. If your PC is important to your existence, you'll only end up frustrated when something goes wrong & you've just blindly accepted changes. No [petty much anything] is perfect. Just some free, friendly advice from an old fart... take it for what it's worth. Me? Ignoring some of my own advice, I immediately jumped on this on Dec. 7 when it was released, but when things started behaving badly, I had a pretty good idea where to start looking & what to try. I LOVE a mystery! YMMV Support was on this from the start, but it wasn't widespread & clearly obscure. If support asks for input, pony up. Otherwise, just DISABLE.WEB PROTECTION & give them time. Some additional clarifications: - This lock-up happens w/ MBAM alone, for the affected users. An AV product does NOT appear to be required. - With Avast (my testing) installed, the failure profile changes... AvastSVC (et al) slowly consumes available system resources until exhausted & the system SEEMS unresponsive. Never had the patience to see if it eventually locked up before power-cycling. Similar behavior has since been reported with other AV products.
  17. I'm willing to pitch in... when the PC is not busy doing its job. Please let me know what's involved.
  18. I started the following thread on Dec. 6, predating any suspect Windows updates, so I'm pretty sure that's a red herring. https://forums.malwarebytes.com/topic/240242-component-update-10508-issue/ Win 7 Ultimate x64 SP1, recently only taking monthly 'Security Only' updates from catalog, KB4471318 NOT installed Avast Premier (current) Intel(R) 82579V Gigabit Network Connection TAP-Windows Adapter V9 VirtualBox Host-Only Ethernet Adapter As I can readily repro either issue I detail in my thread, I'm willing to collect 'PSList' info for both (later today) if you are interested.
  19. I was one of the 1st to report on this update: https://forums.malwarebytes.com/topic/240242-component-update-10508-issue/ What you suggest is consistent with my testing... with Avast installed alongside MBAM, the AvastSVC would slowly consume system resources until nothing new could launch, but the system didn't lock up. With Avast uninstalled/completely disabled, the system would lock up HARD. Others, using something other than Avast, have reported similar observations. I've been running since that thread stopped getting any updates with 'Web Protection' disabled. I haven't had any new lock ups, but I HAVE seen some odd network behavior which I was able to resolve by disabling (Intel) NIC 'green' features. Haven't tried re-enabling MBAM WP, but figured I'd mention it as a possibility since so many others are now affected & nothing new seems to be happening. Will eventually test myself.
  20. Temporarily disable web protection on the affected machines & wait for engineering to do their thing
  21. More people seem to be reporting this issue now, but I see no official responses, or requests for new data. Any status update, Devin? TIA
  22. I noticed this happening 2 updates ago. Rebooting the system cleared things up for me.
  23. This seems like what I've been experiencing. If disabling Ransomware Protection doesn't do it for you, try disabling Web Protection.
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.