Jump to content

bdubrow

Staff
  • Content Count

    888
  • Joined

  • Last visited

Everything posted by bdubrow

  1. bdubrow

    v4

    Hi Nazareno-- Thank you for your interest in our future product releases! We don't currently have a set release date for the next major version of Malwarebytes, but the first step before it's released will be to run a beta. We are hoping that the beta program for Malwarebytes 4 will be much longer than our normal betas, so there should be plenty of time to check it out and provide feedback. You're in the right place to find announcements of new betas, so I'd suggest signing up to "watch" this forum, if you haven't already. To do this, just go to the main beta forum page https://forums.malwarebytes.com/forum/146-malwarebytes-3x-beta/ and click the Follow button in the top right. Again, the timing is not definite, but I hopefully later this summer we'll have more info for you.
  2. Hi again-- Note that we've now got a newer version going out: 1.0.563
  3. We have another new Beta update for 3.7.1, Component update 1.0.563, that we've just started sending out. The only change between this package and 1.0.562 is a fix for a defect around the false positive prevention logic.
  4. Thanks, Firefox! The correct version is 1.0.562. I’ve fixed the typo in the other post.
  5. As I mentioned both options will be dropped into the trial upon install, assuming they have not used their trial yet. We fully understand that not all users are going to buy. There will always be free users. We are trying to find the best way to communicate with the people who are interested in our business products. These flows, as well as others, are also subject to change as we test and optimize. But bottom line is that it’s the same product installed either way and the malware scanning and remediation is exactly the same.
  6. Thanks for the great feedback, Lava! We've been monitoring the response and the comments on this thread are helpful. The team is already working on a revised experience here and will certainly take all the feedback into account. The terms of your subscription dictate the terms of your renewal. We would not automatically switch you to a completely different product out of the blue, nor would that be possible legally. But more importantly, that is not who we're about as a company -- we'd just never operate that way. We try our best to be transparent so folks trust us. Here are the list of current differences if you choose "Work": You'll see a different dashboard status message when you're running the Free version of Malwarebytes 3. This dashboard just lets you know that we have a full line of corporate / enterprise products that may be a better fit for you. The Windows title bar in Free mode says "Malwarebytes Business 3.1.7" (or applicable version number) The title of the program in blue header at top of main dashboard says "Malwarebytes Business" instead of "Malwarebytes Premium". Currently upon install you are not automatically dropped into a Trial like you would be if you chose Home. But that will be changing shortly so behavior is consistent again between the two options. If you upgrade from any of the Upgrade Now links in the Free or Trial version, you will be presented with our business products for purchase. There is decreased promotional messaging in this version currently, as that is primarily directed at home users (e.g. special offers for Black Friday, etc.). Which Enterprise version do you have? Our Enterprise products include Endpoint Protection, Endpoint Security or Endpoint Protection and Response. None of those products will even see this screen. This screen is only seen in the installer used for our Personal and Teams products. See #6 above. Right now you'd actually see LESS of this type of marketing if you chose Work Computer. We are trying to better tailor the experience to who's actually using the product. We know that businesses use our home product and we also know that many of them don't even realize we have business products available. So we're looking at different ways to provide the best experience based on how and where you're using the product AND to make sure you have the best product to fit your needs.
  7. Thanks for asking, OrangeSour! This is a new screen added to the installer that some users have been seeing since our 3.6.1 release. Now we're rolling it out to all existing users as part of the 3.7.1 upgrade. It's pretty self-explanatory. Let us know where you're using Malwarebytes -- either on a personal or home computer or on a work computer / in a business environment. There are no major differences in underlying functionality at all. The only difference is if you choose Work computer you'll see information about some of our available business products that may be a better fit for you. That's the extent of it.
  8. Thanks for confirming! This is good news.
  9. We've just posted a test preview build that we believe should prevent the freeze from occurring. We are still testing this internally, but wanted to make the build available to those who are comfortable with testing a pre-beta build. Please see the post in our beta forum here.
  10. We've just posted a test preview build that we believe should prevent the freeze from occurring. We are still testing this internally, but wanted to make the build available to those who are comfortable with testing. Please see the post in our beta forum here.
  11. Hello! If you are experiencing the Windows 7 freeze issue we have a new test preview build for Malwarebytes 3. This test build incorporates an updated component package intended to resolve the freezing. We are still in the process of working through our internal testing and regression on the component package, but because we have had good feedback from testers and because this is a priority issue, we wanted to make this build available for those comfortable working with a pre-beta test build. If you prefer not to work with this test version, then we hope we can offer further solutions for you some time next week. You may download the test build, with new component package 1.0.527, from this link on Box: https://malwarebytes.app.box.com/s/5ov6t2yx366cjgdsv6hgrtshbvlbybnj Please let us know whether this resolves the issue for you.
  12. Hi all— I wanted to share some promising news! We’ve now been able to consistently reproduce the freeze in house on more systems and we believe we have narrowed the problem to multi-processor synchronization issues with our Web Protection code on Windows 7. We have an updated version of Malwarebytes that we’re currently testing, so far with encouraging results. I want to make this update available just as soon as possible, but we want to be sure we aren’t introducing any additional issues, so further testing is still required. Assuming all goes well, I’m hoping we’ll have more good news for you next week. We appreciate everyone who’s been working with us to help resolve this problem, even behind the scenes. Your assistance has been invaluable!
  13. Hi all— I wanted to share some promising news! We’ve now been able to consistently reproduce the freeze in house on more systems and we believe we have narrowed the problem to multi-processor synchronization issues with our Web Protection code on Windows 7. We have an updated version of Malwarebytes that we’re currently testing, so far with encouraging results. I want to make this update available just as soon as possible, but we want to be sure we aren’t introducing any additional issues, so further testing is still required. Assuming all goes well, I’m hoping we’ll have more good news for you next week. We appreciate everyone who’s been working with us to help resolve this problem, even behind the scenes. Your assistance has been invaluable!
  14. Great question! As soon as a solution is available, either as part of a new component package update or a new version upgrade, we will post both a general announcement of the release here in this forum (as we do with all new versions) and we will post a reply to the pinned topic on the Windows 7 freeze issue. In addition, we'll post another reply to this thread confirming the issue's been resolved and including all the relevant version info and instructions on how to obtain it. And if the fix involves a full version upgrade, you're correct that you'll see a notification alerting you that a new version is available.
  15. This involved testing with many, many different Windows 7 systems and hardware configurations in an attempt to get as many commonalities as possible with systems reporting this based on logs provided. We are not able to replicate on demand. With our internal systems there is still an aspect of timing with this, i.e. we need to let a system run for some time before we see the freeze. No, we are still investigating. But right now we are concentrating our efforts on the Web Protection module moreso than Ransomware.
  16. Thank you all for your feedback and continued help in troubleshooting this issue. We totally understand the urgency around this and have had teams working through the weekend to resolve. We have finally procured a system that is able to reproduce the freeze and now we’re analyzing why it is occurring. It’s been extraordinarily frustrating for us to not have been able to reproduce this while seeing the reports from the field continue to come in, mainly because we know how frustrated you all are. The fact that this problem only impacts a relatively small number of systems doesn’t help if you have one of those systems or if you're dealing with customers who have this problem. Rolling back to previous version (as outlined in pinned topic in this forum) continues to be the best option as a work-around for now. While suggesting that we just push an update to all users (even those not affected by this freeze) to roll back to the earlier version may seem simple, it’s more complicated than you might think. There were other critical fixes in the 1.0.508 update that would impact other users seriously (such as BSOD fixes, etc.). And any update out to the user base has to go through another full round of testing, which takes time and which would be more complex since the update would be have to support being applied over 1.0.508 as well as earlier component packages. So we are discussing all options, but will move forward with the best one. We also have another release already planned and in the works, so initially we had been hoping to include the fix as part of that upgrade. Now that we are able to reproduce the issue we are much closer to a fix and determining the best steps forward. To everyone helping with logs and system info to try and narrow the cases, we truly appreciate it! To everyone eagerly awaiting resolution, we are treating this as highest priority and we will continue to keep you posted.
  17. That's great to here! I appreciate your checking in here to let us know.
  18. That is definitely not supposed to happen, so I certainly apologize for that. We had already suspended this message earlier, so hopefully you won't see any further instances. We are investigating.
  19. Thanks for the feedback, everyone! The intention of the message was more for education and to provide awareness around our mobile line of products (which offer completely free versions as well). But I can totally understand how this could be seen as promotional and unwanted. We are working on providing an option to allow opt out of promotional messages, so hope to have that available soon. And these sorts of messages should definitely not steal focus, so we'll get that fixed as well. This message only went to a subset of users and is only set to display one time, so if you've already seen it you shouldn't see it again. Your quick feedback on these issues definitely helps, so it is very much appreciated!
  20. Hi @AlanChippy Sorry for any confusion here! Our component update packages are always released initially as independent updates, separate from our full installers. These are metered out to our user base over time rather than sent to everyone all at once. Since these are applied automatically and silently in Malwarebytes, most users don't even realize they've received an updates. But as khanmein pointed out, you can always manually force the update if you don't want to wait to receive it through the automated process. Then, typically on the day following the roll-out of the new component package, an updated Malwarebytes full installer with the latest component package already integrated is posted to our website. So by later this afternoon all the website download links should be updated with new installer that includes 1.0.482. Hope this helps clarify.
  21. Actually, yes, this would probably help as well. Please let us know if you try it and it doesn't.
  22. Hi TempLost-- Thanks for providing the logs! The problem looks to be related to Windows 7 and could occur on any older or slower system. We have some ideas how to prevent this from happening in the future, but unfortunately the changes won't make it into this update. The work-around you performed is exactly what should fix things.
  23. Thanks for the reply. Malwarebytes does attempt to send that required client data, so it would definitely show as connection attempt and Pi.hole would block (or allow) according to your settings. And yes, on "optional" I was referring primarily to Website and Dialogue section and also as noted in the Directly paragraph in How do we collect your information?: "Some information you provide to us directly. For example, when you post comments, ask questions in our blog, fill out a user profile or voluntarily decide to grant us remote access to provide you with technical support." Glad you're happy continuing with Malwarebytes! Hopefully it'll continue working okay for you with everything blocked.
  24. Hi @Wutai-- The telemetry opt out setting "Usage and Threat Statistics" in Application Settings allows you to opt out of sending malware and scan event detail, as well as information about how you're using Malwarebytes. Certainly it's up to you if you choose to provide this data or not. It is used to help understand the types of threats actively circulating within our community and for other general cyber security research purposes with the end goal of providing better protection for all. We use the usage data to optimize product features and user experience. However, even if you've opted out of that setting there is certain key information that will always be sent regardless of the setting. This data is required and considered integral for normal and proper program functionality. The information sent includes data such as the program's license state, specific build (in case where there may be custom functionality), the operating system and other basic system info (file system, architecture), specific program version in use (including component and database packages) and other general program settings like language and real-time protection modules enabled. This is required so we know what updates and versions of the product to send you, and perhaps even more important so as to avoid any potential conflict, which to not send. You posted the link to our Privacy Policy as I was writing this up, and that's exactly where I was going to direct you for more information, so glad you found it. ? I'm not going to debate our entire privacy policy here, but I will mention that others have actually complimented us before on how easy it was for them to understand vs pages of legalese that you'll find at a lot of other companies. Your statements above leave out a few key points where we specifically state that providing information to us, like your email or phone number, is completely optional or voluntary in order for us to communicate with you at your request. For example, you voluntarily created a forum account here to ask a question. Lastly, I'll point out that the Other Privacy Considerations section explains the opt out procedure for all products. The remaining data sent is required for us to serve you correctly. We recently, along with pretty much all other companies doing business in Europe, went through an exhaustive audit of all data and privacy collection practices at Malwarebytes to ensure we were compliant with all the new GDPR regulations. If you are still uncomfortable, then it is of course your option to not use Malwarebytes. We try to be as transparent as possible with our disclosures.
  25. Hi Petera3js6igq33hM-- Thank you for your feedback! Typically we certainly aim to have new version roll-outs timed to coordinate with all website updates. But occasionally there are times where the web team's production release schedule is off-sync with ours. When faced with a choice to delay a new version of Malwarebytes or release as soon as possible knowing the web updates will follow shortly after, we tend to favor releasing sooner. This gets new detection techniques, urgent defect fixes and other enhancements in the hands of our users more quickly. Just like yesterday, if this ever happens, we'll always have an announcement here in the forum so there's some "official" notice of the new version. The website Release History should be updated shortly.
×
×
  • 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.