Jump to content

exile360

Experts
  • Content Count

    27,826
  • Joined

  • Last visited

Everything posted by exile360

  1. Unfortunately there probably won't be a solution unless the Developers update Malwarebytes Anti-Rootkit to be compatible with Malwarebytes 3. The format of exclusions in Malwarebytes 3 is different from Malwarebytes 2, and apparently Anti-Rootkit wasn't updated to be able to read the new format so until that happens, it isn't going to be able to use Malwarebytes 3's exclusions list.
  2. OK, sounds good. Just FYI, Malwarebytes Anti-Rootkit BETA is a platform for testing new rootkit detection and remediation capabilities prior to integrating them into the main Malwarebytes product/engine. There haven't been any major new rootkits in quite some time, so there haven't been any new features built into the beta that have yet to be integrated fully into Malwarebytes 3 so you aren't really gaining anything by running both tools. Also, Anti-Rootkit doesn't detect PUPs or PUMs, so for a comprehensive scan you'd still need to run Malwarebytes 3 anyway. On the other hand, there are still some items that ADWCleaner detects that Malwarebytes 3 does not, so it makes an excellent addition to a scanning regimen.
  3. They don't need to go to the beta forum for info. The info in the post pinned in this forum should be sufficient, and in reality most users don't even come to the forums anyway and would probably contact Support if they're really curious or just check the site, though unfortunately the site only includes info on major releases, not CUs. The fact is that most users won't even be aware of CU releases since they install silently and automatically just like database updates, so the only indication that one has been installed is the changing of the version info in the About sub-tab. It would be nice if the Changes.txt file would get an update whenever a new CU is published, but given the fact that these are basically just patch releases, it's somewhat understandable, but maybe a revised version with both the changes from 3.5.1 as well as any current/released CUs in their own sections in the text wouldn't be a bad idea. I'll suggest it to the team. From what I know of 1.0.391 so far, it's really a mixed bag. While it did correct some of the known issues with 3.5.1, it wasn't able to address all of them. The BSOD issues are still happening, as are the issues where some third party apps fail to update when Web Protection is active and there's also a startup issue some users are experiencing where protection doesn't load on boot and another where the tray fails to load on boot. I suspect we'll be seeing at least one more CU in the near future to address these problems, but at least some of the issues from the last release have been resolved.
  4. It should update and scan, but it really isn't a replacement for version 3. A lot of new detection and removal capabilities have been added since then which aren't backwards compatible with older versions of Malwarebytes. If your goal is just to check your system for rootkits with Malwarebytes Anti-Rootkit BETA once in a while, that's fine, but really it's main purpose is as an emergency cleanup tool for badly infected systems. Malwarebytes 3 has rootkit scanning built in and includes the capabilities of Malwarebytes Anti-Rootkit in its engine, so you'd be better off using that alone as a long term solution. Just launch Malwarebytes 3 and go to Settings>Protection and enable the Scan for rootkits option and it will check for rootkits whenever you scan.
  5. There weren't any changes between the beta and the release (hence the same version number rather than it being called 1.0.392+) so whatever was true of the beta is true of the final release version. This also means that anyone who installed the beta need not worry about having to install any new final build of the CU as they already have the final bits installed.
  6. They don't need to reside in the same folder, in fact, try keeping Malwarebytes installed in its default location (C:\Program Files\Malwarebytes\Anti-Malware) and just run Malwarebytes Anti-Rootkit from your desktop and allow it to extract to its default location on the desktop to run it from there and see how it goes. Don't move any files because that won't help. Anti-Rootkit is coded to read the Malwarebytes exclusion files from their default location, but if it isn't compatible with Malwarebytes 3, then you may need to remove that and install Malwarebytes Anti-Malware 2.x. The last released version of 2.x may be found here. You'll need to install it then add exclusions for whatever you don't want Malwarebytes Anti-Rootkit to scan, then it should work.
  7. Greetings, Please open Malwarebytes and navigate to Settings>Application and click on the Install Application Updates button. It should download and install the new component package, version 1.0.391 which includes several fixes and improvements and might resolve this issue so that your games are no longer blocked. Please let us know how it goes. Thanks
  8. Some info regarding the new CU have been posted here. It provides some details about what has been fixed in the release and an overview of some of the changes.
  9. OK, good. Yes, please let me know how it goes. Hopefully you'll have better luck with the new version.
  10. OK, good. Let me know if the notifications do show up again, but hopefully it's resolved now.
  11. Greetings, Actually, there is a way to exclude items from Malwarebytes Anti-Rootkit, but to do so you must have Malwarebytes 3 installed. If you create exclusions in Malwarebytes 3 on a system, Malwarebytes Anti-Rootkit should honor them; at least that's how it worked in the Malwarebytes version 2 days, so as long as they have brought this feature forward into the current builds, then this should still work. From the documentation included with Malwarebytes Anti-Rootkit BETA:
  12. If you return to C:\ProgramData\Malwarebytes\MBAMService and look for a folder called instlrupdate the installer might be in there as well, as indicated by this support article, however I've also seen cases where an orphaned registry entry caused the same thing, so if that folder isn't there or there's no installer inside it, then a registry entry is the most likely cause.
  13. Hehe, good one The installer file should be named something along the lines of mb<something>.exe. It would be pretty obvious if it were there. It's an InnoSetup installer package. The cause of this issue in your case might be a leftover registry entry indicating that the new version needs to be installed. Again, I'd need to logfiles to check though if you could provide them. If you aren't comfortable sharing them publicly then you may send them to me via private message here on the forums. Just hover your mouse over my name above my avatar picture and click Message when the small dialog is displayed.
  14. Greetings, I'm sorry that this is happening, but hopefully we have a fix for the issue. A new component update package was released for Malwarebytes earlier today. If you open Malwarebytes and navigate to Settings>Application and click on the Install Application Updates button found there it should download and install the new update package for you which will bring your installed Component package version: to 1.0.391 (you currently have 1.0.374 installed according to the image you posted, which was the previous version known to be affected by this problem on some systems). Hopefully that corrects the issue, but please let us know how it goes and if any new problems occur. Thanks
  15. OK, it looks like it either hasn't downloaded the installer yet and is just prompting you to do so, or it may be prompting you to install a component update (though that shouldn't be the case I don't think since those are supposed to install automatically and silently in the background without you needing to click anything). The next time the message pops up, please take a screenshot of it and post it here if you wouldn't mind. You can do so by clicking on the pop-up itself (just don't click any of the buttons/controls, just anywhere in the white space of it) and press Alt+Print Screen on your keyboard, then open an image editor like MS Paint and paste the contents of your clipboard there by pressing CTRL+V on your keyboard, then save the image somewhere you can find it and attach the image you saved to your next reply (and you can also insert it into your post if you wish by clicking the (+) on the uploaded image attachment placeholder once the upload completes at the bottom of the forum editor). Also, if you could post the ZIP file I requested above containing the diagnostic logs from the Support Tool, that would be most helpful as it should provide lots more info about what is going on with Malwarebytes and what it is trying to download/install. Thanks
  16. Greetings, I'm sorry that the notifications are giving you a hard time, but we should be able to resolve the problem. First, please begin by providing the following logs which will show us what's going on with your Malwarebytes installation just in case this is the result of a bug the Developers might be unaware of: 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 Next, please right-click on the Malwarebytes system tray icon and select Quit Malwarebytes and click Yes when prompted by User Account Control. Once that's done, navigate to C:\ProgramData\Malwarebytes\MBAMService\lkg_db and delete the installer found there assuming you do not wish to upgrade to the latest release. Once that's done, go ahead and launch Malwarebytes again and it shouldn't bother you about this new version any longer, though please do keep in mind that the last major version released was 3.5.1 which has since had no less than 2 component updates (patches, basically, i.e. minor releases) meaning you'll already be 3 builds behind the latest until you start upgrading. I understand however if there is a bug in the most recent versions which impacts your system for which you are awaiting a fix in a future release as that's reasonable. I just don't want your protection to be too far out of date if it can be avoided as there are almost always both major and minor changes to the protection technologies and detection engines in Malwarebytes with each release, and these past 3 have been no exceptions (on top of the bugfixes for various issues they've included). If you are awaiting a fix for a known issue, if you let us know which bug you have been impacted by, we can check to see if it is one of the problems fixed in the most recent component update, package version 1.0.391 which was released just today to customers and its primarily a bugfix release (you can learn more about it here).
  17. Actually, there is already such a notification (though not quite that wordy, but I think it does the job): It also shows up whenever real-time protection has blocked and quarantined an item which requires a reboot to completely remove. A fairly comprehensive list of current Malwarebytes 3 notifications can be found in the user guide located here.
  18. By the way, if disabling self-protection works, if you could also please do the following as it would help Malwarebytes' Developers to track down the cause of this issue so that they can more quickly get it fixed in an upcoming release we would be most grateful: Download and extract CaptureTrace-Logman.zip Re-enable Self-Protection Navigate to Settings -> Protection Scroll down to Startup Options Disable Start Malwarebytes at Windows startup Reboot the computer Once rebooted, find the files from step 1 Right click on Capture.bat and choose Run as Administrator Once the black window comes up, it will tell you to reproduce the issue Double click the Malwarebytes desktop icon and wait 30 seconds After waiting, click on the black window from step 9 and press Enter Zip up all the files in the folder that opens and attach them in your reply
  19. OK, good, that confirms the bug. If you wouldn't mind doing one last thing for us to aid our Developers in tracking down the root cause and fixing this issue, please do the following as it would be most helpful: Download and extract CaptureTrace-Logman.zip Re-enable Self-Protection Navigate to Settings -> Protection Scroll down to Startup Options Disable Start Malwarebytes at Windows startup Reboot the computer Once rebooted, find the files from step 1 Right click on Capture.bat and choose Run as Administrator Once the black window comes up, it will tell you to reproduce the issue Double click the Malwarebytes desktop icon and wait 30 seconds After waiting, click on the black window from step 9 and press Enter Zip up all the files in the folder that opens and attach them in your reply
  20. I suspect this is being caused by a recently discovered bug. Please open Malwarebytes and navigate to Settings>Protection and scroll down to the Startup Options section as before, but this time turn off the Enable self-protection module setting then restart your computer and let us know if it works or not.
  21. OK, thanks. Did you try disabling self-protection as suggested above by lbdonato? If not, then go ahead and give that a try. There's a recent bug that's cropped up where self-protection causes Malwarebytes to fail to launch on startup on some systems which is being investigated by the Developers.
  22. Excellent, I'm glad to hear it. There are few things that disappoint me more than knowing my system is running slower than it should be, so I'm glad you were able to get yours running better.
  23. Greetings, According to your logs it appears as though it is failing to start because it isn't seeing any user logged in when trying to start the tray: 07/09/18 " 05:42:29.153" 34959 0950 0fa0 INFO ServiceControllerImpl ServiceControllerImplementation::StartApp "ServiceControllerImplementation.cpp" 87 "Starting 'C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe' in session 0x1" 07/09/18 " 05:42:29.153" 34959 0950 0fa0 ERROR ServiceControllerImpl ServiceControllerImplementation::StartApp "ServiceControllerImplementation.cpp" 191 "System error 2 calling CreateProcessAsUser" 07/09/18 " 05:42:29.153" 34959 0950 0fa0 INFO ServiceControllerImpl ServiceControllerImplementation::StartAppIfNotRunning::<lambda_f19f16e888e1a75a06bb8a50e77ae0af>::operator () "ServiceControllerImplementation.cpp" 1853 "Did not start C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe - it is possible that no user is logged in." The tray runs in user mode, so if no user is logged in it will fail to start. There could be a few possible reasons for this, but we'll start with the simplest and work our way from there. First, is timing. It's possible that it's taking too long after system start for the full user login process to complete to the point where Malwarebytes is able to load the tray in user mode, so let's try putting a delay on it and see if that helps: To begin, let's try configuring protection to start after a delay: Open Malwarebytes and navigate to Settings>Protection Scroll down the tab until you locate Startup Options Toggle the setting Delay Real-Time Protection when Malwarebytes starts to On Click the drop-down menu next to Delay protection for: and select 120 seconds to start Restart your system and see if it is now able to start properly after waiting for a few minutes If that worked, you may try backing off the delay by reducing the number of seconds in the drop-down until you find the shortest delay that works and if it doesn't work, you may try increasing the value until you find one that does work (assuming any of them do work) If that failed, you may toggle the Delay Real-Time Protection when Malwarebytes starts setting to Off once more then proceed with the following to determine if the service is the issue: Click on START and type services.msc and press Enter Scroll down the list until you locate Malwarebytes Service in the list and double-click on it In the properties dialog that opens, click the drop-down menu next to Startup type: and select Automatic (Delayed Start) then click Apply and OK then close the Services window Restart your system then see if Malwarebytes starts up on its own this time. Give it a minute or two though, as it's going to be delayed rather than starting immediately Please let me know how it goes. Thanks
  24. My Threat scan only takes just over 2 minutes and scans 232,631 objects. The heuristics portion at the end only takes about 1 second or less. The amount of time it takes varies depending on your system, the number of files, the number of registry startup entries present and your hardware (CPU, RAM, drive etc.) so yes, it can vary wildly between different systems. The heuristics portion at the end is more of a CPU intensive operation than anything because it's primarily checking and comparing several items from earlier portions of the scan, and when no threats have been found once it gets to that point, there isn't much to check so it should be much faster than the earlier parts, especially when no threats have been detected up to that point.
×
×
  • 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.