Jump to content

KJ73

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About KJ73

  • Rank
    New Member

Recent Profile Visitors

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

  1. I am getting this error when trying to open or reinstall MBAM 4 through an RDP session to my Windows 10 desktop. It seems the MBAM UI is choking on something when working within the RDP GDI redirector. If I work locally on this PC's console or connect remotely with AnyDesk (scraping the framebuffer from the AMD-based video chipset), the MBAM UI comes up without issue.
  2. I have been running the 1.0.527 component package for about two hours on my Windows 7 (problematic) and Windows 10 (unaffected) workstations today with all protections enabled. So far so good.
  3. I would be happy to help test the update on my affected workstation.
  4. Here is an example of handling a situation better: Cisco put out a bad Firepower patch bundle (6.2.3.8) on Jan 2, 2019 that causes Firepower to stop processing traffic after it has been up for a few hours if a specific protection (HTTP file inspection) is enabled. By Jan 8, 2019, patch 6.2.3.8 was recalled, a bug report was published with specifics of the problem, how to identify it happening, and two workarounds (disable HTTP file inspection, or roll back to the previous update). On Jan 9, 2019, there were Reddit discussions talking about the issue and referencing the bug re
  5. When did the freeze first start occurring? December 12 What were you doing on the computer immediately prior to the latest freeze? Sitting at the Windows desktop after logging in. It has also happened when working in Outlook and browsing in IE and Chrome. Did you notice anything significant occur around the time of the latest freeze (e.g. AV notification, application crash, etc)? I did not notice anything Has a freeze occurred when the computer is idle? Yes Have you noticed a correlation between high network traffic and the computer freezing?
  6. Stable here for 36+ hours with both Web and Ransomware Protection disabled.
  7. I had another lockup after a few hours with just Ransomware disabled. The affected desktop has been stable today with Web and Ransomware both disabled.
  8. I have also been experiencing this problem on a Windows 7 64 bit desktop starting on 12/12. 3.6.1.2711, 1.0.508, 1.0.8367. I have wasted days running hardware tests to try to isolate why my desktop freezes within a few minutes of booting into Windows. I finally guessed it was related to MB, turned off all realtime protections and was solid for ~12 hours, and then discovered this thread. I have since re-enabled all but the Ransomware protection and the desktop seems stable. Very disappointing that I recently upgraded to a paid account and this is what happens.
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.