Jump to content

AnotherConcernedCitizen

Members
  • Content Count

    72
  • Joined

About AnotherConcernedCitizen

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. I appreciate your hesitation, but would never have considered posting either had I detected anything untoward. Sorry, I probably should have obscured them somehow.(insert code?). The upshot was that these are common javascript 'toys', not malware. The forum post suggested 'disabling a screensaver', but it could just as easily have been something in the browser cache.
  2. Is this what you are seeing? auz.github.io/Bug/ I found this discussion via websearch: https://www.bleepingcomputer.com/forums/t/620622/insect-on-screen-malware/
  3. 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.
  4. 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.
  5. 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).
  6. 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.
  7. Correction... the offending string is 'amp;' sans '&', but you probably knew that.
  8. 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.
  9. 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.
  10. 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^).
  11. 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.
  12. 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
  13. https://forums.malwarebytes.com/topic/241223-malwarebytes-for-windows-and-windows-7-freezelock-up/
  14. 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?
×
×
  • 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.