Jump to content

KJ73

Members
  • Content Count

    8
  • Joined

  • Last visited

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 up to 72 hours with no issues on component package 1.0.527.
  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 report: https://www.reddit.com/r/networking/comments/aeb4gx/dont_install_cisco_ftd_6238_p1_file_policy_bug/ On Jan 10, 2019, patch 6.2.3.9 was released with the fix. On Jan 14, 2019, a proactive notification went out to anyone who had downloaded 6.2.3.8 advising them of the defect: While this notice wouldn't necessarily go to everyone impacted - only the person who downloaded the code would receive it, and that person might not even work for the affected customer - word of the defect spread quickly among people who needed to know about it. This was for a "Severity: 1 Catastrophic" problem affecting a small portion of the userbase. MBAM's customer base is different and communication techniques must necessarily be different, but the key difference here is ownership of the problem and a timely effort at customer notification. In Cisco's case, no automatic update would have pushed 6.2.3.8, so admins were generally aware that they applied an update and afterwards there were problems - which is what makes the problematic MBAM 1.0.508 automatic update so insidious. One day things are working, and the next day they aren't. Nothing on the affected machines even remotely hinted at an MBAM update being the problem. Only trial and error troubleshooting, or some lucky google searches, pointed most of us to this forum. If you want to erode trust in your product by your userbase, this was a great way to do it. Many of us are influencers - people who convince our customers, colleagues, relatives, and friends to buy your software. Consider how many are reevaluating this decision. It's not a good look.
  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? I have not noticed this either way How often does the computer freeze? I can't run more than an hour or two without a freeze. Sometimes it happens within minutes of booting up. Are you able to reproduce the freeze on-demand? If the answer is yes, what are the steps? No How old is the computer? Approximately 5 years, custom built business desktop Was the computer upgraded from XP/Vista to Windows 7? It was a fresh build on Windows 7 64 bit when PC was new. There have been no hardware changes. Is the computer fully up-to-date with Windows Updates? Which updates have been installed after the first freeze occurred? Yes, fully updated automatically from Windows Update Does the computer have multiple network adapters? If it does, what happens when you disable the adapter currently in use and switch to a different adapter? Single embedded motherboard adapter. "Realtek PCIe GBE Family Controller"
  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.
×
×
  • 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.