mkaz

Thx!

I received Component Package Version 1.0.519 1-2 days ago. Can someone shed some light into the changes made from 1.0.508 to 1.0.519? Thanks.

And to the fanboi club, no more "practice patience" postings please. Enough is enough.

Just let everyone know regardless of OS, but state what OS's are known to be impacted. Don't limit the communication - it is information of value. We are all just desperate to get communication out in the first place in a timely manner. This has been a case study of what NOT to do.

Meant to state Battle.net updater not Blizzard.net as tend2it cited.

Has Blizzard.net reported by @tend2it been tested on your test system? It is one of the few I read where the work "repeatedly" was used. His posting cites https://us.battle.net/forums/en/bnet/topic/20770537321#post-11 where turning off web protection resolved the freeze issue.

I have no doubt that you and the rest of the staff are working this issue hard. But I do have to ask how your telemetry will pick up users with freezes in this scenario: User A has freeze issues and uses Malwarebytes User A does not know how to troubleshoot this User A does not know the impact from Malwarebytes (or other interaction) User A has not input a ticket with Malwarebytes for the issue because he has not troubleshot this down to Malwarebytes yet nor found or visited the forum User A has performed force shutdowns numerous times User B is part of a company whose IT staff adjusted or removed Malwarebytes and did not communicate this to your company. Freezes and force shutdowns led up to this decision. There are plenty more scenarios of this kind that one can think of You telemetry picks up all the force shutdowns around the world???

@Lava, curious whether your OS updates include the new Jan. updates now coming out..... Today, @JasonGillman posted: Today's Microsoft update seems to have fixed the problem and I have been up for several hours without lock up and web protection ON.

@torus_ot, thx. I've been following this forum and commenting on it since Dec. 19th and know very well of the reporting you cited. My comments were simply in support of Malwarebyte users that have no clue of this forum, do not know how to troubleshoot it, have been battling the freeze issue, may have spent countless hours of time and frustration and perhaps even reloading the Windows OS only to have the issue come back if they re-install Malwarebytes. It seems to me that regardless what the culprit is, an automated downgrade of Malwarebytes would have resolved a lot of frustration and may still resolve a lot of frustration given this is going on for a month or so now. This does not stop Malwarebytes for moving forward with identification of a solution.

Is there a technical reason why Malwarebytes never considered pushing clients back to the previous version that did not experience the freeze issue until troubleshooting and a solution is identified? I can't imagine the troubleshooting and frustration that effected users are going through, especially those without the technical skills to know where to begin, what to test, and where to look for help. Until a toggle or turning off Malwarebytes completely is performed, Malwarebytes may be one of the last things that your clients are looking at. I appreciate the consistent communication from Malwarebytes now in the forum. Thank you.

Great question @loco! I can't tell you how many forums I review where this is a pact response, "only less than 1%".... @dcollins, I do appreciate your involvement now and hope you will keep us updated on a frequent basis. There are too many threads open, so perhaps you can create one pinned location and direct us all there. I'll see what I logs I can get to you, but the fact you are requesting logs at this time, as weeks have gone by now with complaints, is disappointing. Is the team struggling trying to find a solution?

@loco, thanks for your perspective. Is this case, my clients are running anything from MSE, Norton, ESET, Avast, and others so I do not believe it was an AV conflict, this time around. Regardless who has developed what, isn't it the responsibility of Malwarebytes to FULLY test the integration of the modules thoroughly before release? No excuse not to have a ton of various VM platforms with the appropriate test methods implemented over days, weeks, etc. Would you agree?

I am very disappointed that Malwarebytes is not owning this from a communication standpoint and that it takes forum members to keep each other updated. Thank goodness for forum member support! I expected at a minimum that Malwarebytes would would be pinned something acknowledging that there is an issue, they are working on a solution, etc.. There is nothing here: https://forums.malwarebytes.com/forum/41-malwarebytes-3-support-forum/ It is as if there is an internal policy that they can never let the public know they messed up. I for one appreciate honesty and can be accepting of some rare issues as long as I see the ownership and the communication is out quickly. I can't imagine how many individuals without knowledge of this forum have spent countless hours trying to identify the source of the issue, lost documents they were working on, re-installed the OS only to see the issue re-occur, etc. There are Norton haters out there and I am not promoting Norton, but at least they will own an issue. They will pin the issue here, in the case of Norton Security: https://community.norton.com/en/forums/norton-security And an example of a thread with clear involvement from Staff supporting identification of issues leading towards resolution: https://community.norton.com/en/forums/hot-issues-and-fixes This may be the 2nd or 3rd major issue I've witnessed with Malwarebytes and I can't think of a time where they owned the communication letting users know of the issue, that they are working on a fix, and finally that the fix was out. If I am incorrect, feel free to point out an example I may have missed where they communicated quickly from beginning to end.

I am very disappointed that Malwarebytes is not owning this from a communication standpoint and that it takes forum members to keep each other updated. Thank goodness for forum member support! I expected at a minimum that Malwarebytes would would be pinned something acknowledging that there is an issue, they are working on a solution, etc.. There is nothing here: https://forums.malwarebytes.com/forum/41-malwarebytes-3-support-forum/ It is as if there is an internal policy that they can never let the public know they messed up. I for one appreciate honesty and can be accepting of some rare issues as long as I see the ownership and the communication is out quickly. I can't imagine how many individuals without knowledge of this forum have spent countless hours trying to identify the source of the issue, lost documents they were working on, re-installed the OS only to see the issue re-occur, etc. There are Norton haters out there and I am not promoting Norton, but at least they will own an issue. They will pin the issue here, in the case of Norton Security: https://community.norton.com/en/forums/norton-security And an example of a thread with clear involvement from Staff supporting identification of issues leading towards resolution: https://community.norton.com/en/forums/hot-issues-and-fixes This may be the 2nd or 3rd major issue I've witnessed with Malwarebytes and I can't think of a time where they owned the communication letting users know of the issue, that they are working on a fix, and finally that the fix was out. If I am incorrect, feel free to point out an example I may have missed where they communicated quickly from beginning to end.

I am very disappointed that Malwarebytes is not owning this from a communication standpoint and that it takes forum members to keep each other updated. Thank goodness for forum member support! I expected at a minimum that Malwarebytes would would be pinned something acknowledging that there is an issue, they are working on a solution, etc.. There is nothing here: https://forums.malwarebytes.com/forum/41-malwarebytes-3-support-forum/ It is as if there is an internal policy that they can never let the public know they messed up. I for one appreciate honesty and can be accepting of some rare issues as long as I see the ownership and the communication is out quickly. I can't imagine how many individuals without knowledge of this forum have spent countless hours trying to identify the source of the issue, lost documents they were working on, re-installed the OS only to see the issue re-occur, etc. There are Norton haters out there and I am not promoting Norton, but at least they will own an issue. They will pin the issue here, in the case of Norton Security: https://community.norton.com/en/forums/norton-security And an example of a thread with clear involvement from Staff supporting identification of issues leading towards resolution: https://community.norton.com/en/forums/hot-issues-and-fixes This may be the 2nd or 3rd major issue I've witnessed with Malwarebytes and I can't think of a time where they owned the communication letting users know of the issue, that they are working on a fix, and finally that the fix was out. If I am incorrect, feel free to point out an example I may have missed where they communicated quickly from beginning to end.