Jump to content

exile360

Experts
  • Content Count

    24,403
  • Joined

  • Last visited

Everything posted by exile360

  1. Greetings, Malwarebytes scans should work fine within limited accounts because the scan and scheduler run as a service which has higher than administrative privileges and scans all user accounts on a computer, including local user folders and local user registry hives so it shouldn't be a problem in this regard. With that said, there are occasionally program updates for new product versions which need to be installed through an administrative user account because administrative privileges are required to install software, so I would recommend occasionally logging into these systems as an admin, opening Malwarebytes and navigating to Settings>Application and clicking on the Install Application Updates button to make sure that the program is fully up to date with new versions and components, restarting the system if prompted to complete the installation process. It's not unlike updating other software on the system such as browsers and plugins to help stay secure.
  2. Yes, the bug is an issue in the Web Protection component in Malwarebytes 3 which interfaces with the network stack so it can definitely cause temporary instability in other drivers that share the network stack, like some of the drivers used by Avast! so it's entirely possible for it to cause that, however now that you have the beta installed the crashes shouldn't occur any more, but please let us know if any issues do occur.
  3. Yes, it crashed because you aren't running the beta version where this issue has been fixed. To resolve the issue you would need to install the beta by opening Malwarebytes and navigating to Settings>Application and scrolling down the tab until you find the Beta Application Updates section and enable the setting beneath it, then scroll back up near the top of the tab and click on the Install Application Updates button which should download and install Component Package version: 1.0.418 which is the beta build where the BSOD issue should be resolved.
  4. Yep, like I said, it should work. Unfortunately there's a bug here that has yet to be resolved. Hopefully it will be soon after all these reports. For anyone having this problem with Malwarebytes installed in a location other than the default C:\Program Files\Malwarebytes where the component update packages fail to install properly, it might help if you tell us exactly where you have it installed (i.e. the exact path, including the drive letter etc.) and provide the following data from our Support Tool as that may speed things up for finding the cause of the issue and hopefully a fix: Download and run the Malwarebytes Support Tool Accept the EULA and click Advanced Options on the main page (not Get Started) Click the Gather Logs button, and once it completes, attach the zip file it creates on your desktop to your next reply
  5. Yes, component package version 1.0.391 is the last affected build by this BSOD issue. The beta should fix the problem. If you would like to install the beta then open Malwarebytes and go to Settings>Application and scroll down the tab until you find the option for Beta Application Updates and enable it/switch it to On, then scroll back up near the top of the same tab and click on the Install Application Updates button. That should have Malwarebytes download and install the beta for you. Once that's done you shouldn't see the BSOD any more when you run Battle.net.
  6. It depends on how long testing takes. That's the purpose of beta testing, to find bugs before releasing it as a final build so while it shouldn't be too long, it does depend on how testing goes for the beta because if new issues are found in the beta, then that would delay the release since the Developers would need to fix it first and put it through another full testing cycle prior to releasing it (they must test every change to the code fully to check for bugs/issues prior to releasing it in a final build). So QA is testing it, and now of course it is also available for public testing, and as far as I've heard it's gone well so far so I don't expect it to be too much longer, assuming it continues to go well.
  7. Yes, this is a bug. You are supposed to be able to install Malwarebytes elsewhere, but for whatever reason, when you do, it often results in component updates failing to install properly, and while I don't know the exact reason, I have my suspicions. I have a theory that because component updates are stored under Malwarebytes ProgramData folder (that same location I mentioned earlier where definitions, logs and settings are stored), whenever a new component update package is downloaded, a script tries to install the new files to their appropriate locations, including under Malwarebytes program folder and either A it is mistakenly hard-coded to place the files under C:\Program Files\Malwarebytes (which is unlikely, though possible), or B it fails because of permissions, as moving files from one drive to another is sometimes not possible for a program to do due to permissions restrictions in Windows. I've reported the issue to the Product team already, and I will report it once more now that you guys are still seeing it, and hopefully they'll figure out what's causing it so that in the future you may install Malwarebytes wherever you wish without worrying about whether or not it's going to function properly.
  8. There were a few different factors that made fixing this take so long as I understand it (bear in mind I have no direct internal info from the Devs so this is just based on what I have heard from the staff publicly). First, they did have trouble replicating the issue so they had to rely only on data collected from affected users and it can be time consuming trying to track down the exact cause of a crash in a driver via info pulled from crash dumps as they don't always indicate exactly why a particular driver crashed, just that it did crash. They also believed they had it fixed a couple of builds back, but it turned out that the fix they implemented did not correct the issue being addressed by this latest beta (though it did correct other crashes some users were having) and once they discovered that fix did not correct this issue for all users, they had to go back to the drawing board, scouring the code once more to try to track down the cause. They also didn't want to lose any functionality, and while they obviously don't want to crash anyone's systems, there were changes made recently to the Web Protection component which expanded its capabilities, and it was most likely this area of the code that they had to fix to eliminate the BSOD, but doing so without losing that new functionality may have proved tricky (basically, a few releases back they implemented more specific URL blocking in the Web Protection component, and it is my personal hypothesis that this change is where the BSODs started, but since Research needed this new code to be able to provide the best protection possible and to cut down on false positives, the Devs had to find a way to fix the BSOD issue without sacrificing these new enhanced features). Much of that is just my own theory though, so please take it with a grain of salt. But I do know from past first-hand experience having worked QA myself in the past and having worked directly with the Malwarebytes Devs on bugs and issues that it can sometimes take a long time to track down the cause of an issue, especially without a lot of data and no ability to replicate the issue on our own test systems (this means for example that the Devs couldn't just put together a debug build to pass to the QA team to document the issue more thoroughly to reveal the cause of the problem more quickly, something they will often do with such issues when QA is able to replicate a bug on their own systems).
  9. I recall there being a problem with update packages when Malwarebytes is not installed on C:\ or not installed in the default Program Files location so that is likely the cause of the issue with getting the beta and other component updates (the latest non-beta component package version is 1.0.391, so it should not be 1.0.0 if you're fully up to date with the latest non-beta build). I currently know of no workaround for the issue other than installing Malwarebytes to its default location. Also bear in mind that even if installed in another location or on a different drive, the data that Malwarebytes stores such as its definitions, configuration files and logs are all stored in C:\ProgramData which is what takes up most of the space that Malwarebytes consumes on a system, so installing its program files to a different directory or drive doesn't really do much to prevent using space on C:\. For example, here are the numbers for my own installation: C:\Program Files\Malwarebytes - 163 MB C:\ProgramData\Malwarebytes - 261 MB As you can see, the space consumed by Malwarebytes' data folder is considerably larger than that consumed by its program files, and it will only increase in size over time as signatures are updated and new logs are created from scans, real-time protection and other program activities. Also, Malwarebytes drivers will always install to C:\Windows\System32\drivers, so that's more data that cannot be relocated to a different drive. Those files aren't very large, but when added to the space occupied by its ProgramData folder, it just tips the scales that much further, rendering the size of its program files folder that much less significant in comparison.
  10. Yes, contacting Support directly via the options found on this page would be your best option to receive assistance with any license related problems. Also, to create a support ticket you don't need a Malwarebytes account at all, just a valid email address and you should be able to create a support ticket as the two are not connected.
  11. Hey guys, to be clear, in order to install the latest build you need to open Malwarebytes, navigate to Settings>Application and click on the Install Application Updates button. Updating by any other method will most likely only update the signatures/definitions, not the actual program/software or its components. Also, if you wish to install the recently released beta to see if that fixes the issues you're having, then prior to clicking on that button, you need to scroll down the Application tab and enable the following option: Once you've done that and clicked Install Application Updates, you should shortly see the following in Settings>About (once the update has had a chance to download and install after clicking the button): I do not know if this issue was addressed in the latest beta or not, however I do know for a fact that it does correct several other issues so it's probably still worth installing even if this particular problem is not fixed.
  12. No problem, hopefully the BSOD issue will finally be resolved with the beta. This bug has lingered for far too long and I know you guys have been waiting for a fix for a long time.
  13. Here is how you identify whether or not you have the beta. Since it is a Component Update, not a full release, only the Component package version changes which can be verified under Settings>About as illustrated and highlighted in the image below:
  14. Hehe, well it's not up to me, but I'll definitely suggest it to the Product team for consideration.
  15. If that's the case, then I think something like Microsoft's approach might be a better idea since it provides the best of both worlds without compromising any functionality:
  16. Ah, that explains it. Yes, the fact that after a scan the Scan tab gets stuck on the scan results page (even when nothing was detected by the previous scan) is kind of confusing. I've actually asked the Product team to review that and consider changing it so that if there were no detections during the previous scan, they return the Scan tab to normal after a short amount of time (like maybe a few seconds or a minute or two) so that users don't have to remember to click the 'X' to close the scan results screen and return to the normal scan selection screen. Hopefully they will change it eventually.
  17. Oh, I see the problem. You're in the wrong part of the program. You need to be on the Scan tab, not in the Scan Schedule. This image should help:
  18. Oh, is that all. That's no problem. Open Malwarebytes and go to the Scan tab then select the middle option Custom Scan then click Configure Scan and you will be presented with the options to select which areas to scan, including your entire drive(s) if you wish, then just click Scan Now and the scan will begin.
  19. Greetings and welcome, What specifically are you trying to do? Are you trying to create a scheduled Custom scan that runs automatically after the scheduled Threat scan? As far as I know this has never been possible to trigger one scan after another unless you just schedule them close together using the scheduled time. There used to be an option to scan after a successful database update, however with updates being released usually 10 or more times per day, it doesn't make a lot of sense to scan that often. There are a lot of options for scheduled scans as you can see in the images below, however I'd need more details on exactly what you're trying to use as a trigger for the scan to understand what options you would need to set: You may refer to the documentation in this support article as well as the document on this page for more information on the available options for the scan scheduler in Malwarebytes Premium. If you are using the Free version then you are not allowed to make any changes to the scheduled scan except to remove it if you don't want scheduled scans to occur, otherwise it runs once per day if you leave it in the scheduler.
  20. Greetings, The option to exclude the most recently blocked site actually goes away on its own after a certain amount of time has passed, so as long as you don't click it to exclude the site you won't have to worry about the site being excluded or the item persisting in the menu permanently. I don't know what the specific duration is but someone from the staff may.
  21. Greetings, It appears that the Windows Management Instrumentation (WMI) service is missing or damaged on your system, which is most likely what's causing the issue (and also may be causing other problems with other software and components on your system as many things rely on and use it, not just Malwarebytes). Please do the following: Please open an administrative command prompt by clicking START and typing services.msc and pressing Enter In the Services window, scroll down the list until you find Windows Management Instrumentation and double-click on it Make certain the Startup type: is set to Automatic, and if it isn't, set it to Automatic via the provided drop-down menu then click Apply and click the Start button to start the service. If that failed or the Windows Management Instrumentation service was not listed, proceed with the following: Tweaking.com Windows Repair All-in-One Download Tweaking.com Windows Repair from here and install it or if you would prefer, you may instead download and extract the portable version from here Once installed or extracted, launch Repair_Windows.exe Click on the Repairs - Main tab Click on the Open Repairs button Once it displays the list of repairs, click the checkbox next to All Repairs so that everything listed is UNCHECKED Now, click the checkbox next to Repair WMI so that it is checked Click on the Start Repairs button at the bottom Once it completes, allow it to restart your system Once that's done, see if Malwarebytes now works properly. If it doesn't, then try reinstalling the latest version of Malwarebytes from here to see if that fixes the problem. Please let us know how it goes. Thanks
  22. Most antivirus programs are no longer true antivirus programs because true computer viruses haven't existed in the wild for several years now, with the last one seen, I believe, being the final variants of Virut which themselves were in fact so broken that files infected by it could not reliably be cleaned/disinfected by the AVs that attempted to do so (or even the targeted Virut disinfection tools developed separately by many AV vendors for this purpose; something many major AV vendors do these days for any true computer viruses since their remediation engines now often lack file disinfection technology, just like Malwarebytes). The lines are very much blurred now, and technically speaking, malware is a sub-class of software of which viruses are a sub-category (all viruses are malware, but not all malware are viruses) so in theory, any comprehensive anti-malware *should* be capable of dealing with viruses, and in some limited capacity, Malwarebytes is in that it will detect a virus dropper/installer and even a virus infected file, but the difference is, if a file on the system is infected by the virus (i.e. an existing file that was clean before the virus appended its code to it) Malwarebytes will not be able to disinfect the file to make it clean again, but as I already mentioned, most actual antiviruses can't do that these days either and their techniques share much more with the Malware Protection/scan engine component of Malwarebytes than they once did as they have begun to evolve based on the direction that most modern threats have taken and as older disinfection techniques have fallen by the wayside as the bad guys have changed up their methods of attack. One day true computer viruses may make a return, but it's not too likely given how damaging they are, usually breaking the basic functions of the files they infect, meaning it's very easy for them to render a system unbootable and/or unable to reach the web, both of which are requirements for any modern threat now that the goal is to make money, not just to infect (and possibly irreversibly damage) as many systems as possible.
  23. Greetings, To start with, please see if you can complete the scan in Safe Mode. If you need instructions on how to access Safe Mode, let me know and also tell me what version of Windows you're using (i.e. Windows XP, 7, 8/8.1 or Windows 10) and I'll provide them. Next, if that doesn't solve the problem, then please try downloading and running Malwarebytes Anti-Rootkit which can be found here as it may have better luck finishing the scan and removing the threats. If that didn't work or didn't eliminate all of the issues, then please run ADWCleaner and likewise scan with it and have it remove anything it finds. Be sure to restart the system after running each scan with each tool if anything was removed as this is usually a required step of the cleanup process. If the issue still persists, then please go ahead and follow the instructions in this topic and then create a new thread in the malware removal area including the requested logs and info by clicking here and one of our malware removal specialists will assist you in checking and cleaning the system as soon as one is available. Please let us know if there's anything else we can do to help. Thanks
  24. Yep, it's an x86/x64 compatibility issue. The browse window in Norton is being redirected to SysWOW64 rather than System32, so any native 64 bit drivers can't be excluded. That's OK though, as that's likely not the solution to the problem anyway. Chances are, there's something else going on with the system/Malwarebytes installation causing the problem, otherwise we'd be hearing from a lot more Norton/Symantec customers having problems using Malwarebytes, especially if the anti-rootkit driver fails to function as that would also impact Malwarebytes free users, not just paying customers of the Premium version. I'd recommend posting the logs as instructed below and we can take a look at what's going on with your Malwarebytes installation and hopefully figure out how to fix it: Download and run the Malwarebytes Support Tool Accept the EULA and click Advanced Options on the main page (not Get Started) Click the Gather Logs button, and once it completes, attach the zip file it creates on your desktop to your next reply
×
×
  • 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.