CT31

Sorry I didn't do this earlier, but I'd like to post the issue has been resolved for me too. Thank you.

I just updated to the new MB 3.4 Free today. It seems good for the most part. However, I used to be able to scan documents/folders on my computer by right clicking and then hitting 'Scan with Malwarebytes'. After the update today I notice that option is no longer there. Was this intended? Is there a way to get that option back? I'm using a 64bit W7 computer.

I had component update package 1.0.262, but soon after I got it I began to get mbam.exe and tray errors (even though I had the tray icon turned off). Plus, it wouldn't complete threat scans often...most of the time it would freeze on a certain file in memory objects. I went back to 1.0.236 and things work fine now. I'll try updating again when MB puts out a new version.

I may have figured it out. Daman1's post actually got me thinking so I tried clicking on the 'check for updates' on the dashboard and that updated the update package to his number. So I think I'm okay actually. Apparently that part of MB updates whenever I do a threat scan or the dashboard check.

Okay...but I'm curious how I moved from one version number to a higher one without clicking on the Install application updates button and having automatic updates turned off for MB. The only thing I've done is threat scans a couple times since then with MB.

I checked my version of Malwarebytes (Free version) and it said the update package version I had was 1.0.3633. What is somewhat confusing about that is that I read that update package 1.0.3624 was released the other day (and that this was supposed to allow MB users to get Microsoft's mitigation for Meltdown/Spectre). However, I have "Automatically download and install application component updates" off under the "Application" tab. How did I move from one version to a higher version if I have the automatic update system turned off? FYI, I got KB 4056894 from Windows Update a couple days ago so at least that worked. I was curious about this MB issue though. I'm using W7 64-bit. Some more info about my MB: version: 3.3.1.2183 component package version: 1.0.236 update package version: 1.0.3633

One time I waited about 50 minutes and it hadn't moved on from the point I mentioned (usually I cancel the scan if it doesn't move beyond this point in 10 minutes). Usually the entire Threat Scan process (from checking for updates to getting done) takes me about 30-40 minutes. I am pretty sure I had programs and browsers closed though before this recent update (to component package .262) I could browse Chrome with the Threat Scan running and it worked okay.

My Malwarebytes Threat Scan starts normally but it seems to get stuck on "Scan Memory" or "Currently Scanning: Memory Objects" now. Usually it gets past that stage and goes on to "Scan Startup Files" and beyond within a few minutes but now it hangs on this part and doesn't go on. In other words, the "Items Scanned" line stops at a certain number. However, the time elapsed number keeps increasing. The green circle above "Scan Memory" keeps rotating. I've tried uninstalling and then reinstalling MB and that didn't fix things. I can't think of anything I've done recently to cause a problem with this. I also did a Microsoft Security Essentials scan and that came up clean. Any ideas?

By the way Nikhils, I sent you a PM about a (hopefully) minor issue I had with FRST. I wasn't sure if it would have been on topic or not to post it in this thread.

Here's the first thing you asked for. Also, what setting should I have the MB tray icon on? I currently have it on "Hide icon and notifications". mb-check-results.zip

I'll try that first set of instructions later. However, I wanted to clear up something first: from your procmon log instructions it sounds like you think this error comes up when I click on the Malwarebytes desktop icon...that is not the case. This error message occurs when my computer starts up after I enter in my user password and the screen goes to desktop.

Lately it seems every other time I start up my computer, I get this message when Windows comes up after I enter my password on my computer and go to my desktop: "mbamtray.exe - No Disk There is no disk in the drive. Please insert a disk into drive \Device\Harddisk1\DR1" I have no idea why this started coming up since I've never had to insert anything into a drive for Malwarebytes before. I did a threat scan with MB (after closing that error window) and a scan with MSE and both came up clean. Other than this, my computer seems to be working okay. Any ideas on how to solve this? Some more information if it would help: This little pop-up/window error didn't start appearing until after I upgraded my current version of Malwarebytes to component package 1.0.262 FYI, my computer is W7 64-bit.

I tried it just now again, and the final Heuristics scanning took a little longer this time. It was still fairly quick (less than a minute) but not near-instantaneous like it was before. So I guess that's somewhat closer to normal. Is there some heuristics setting I should look at?

I am using the current version of Malwarebytes. It is the free, not the premium, version (and I don't have scheduled scans; I only do manual scans). Over the past few days when I have manually run a "Threat Scan", the scan takes about the normal time it does until it gets to the final step "Heuristics Analysis". That part now goes much faster than it used to...recently that part has only taken a second or two. FYI though, the final total number of "Items Scanned" has been roughly the same as it was before...it's just that as of recently the Heuristics Analysis portion of it has become near instantaneous. There have been no threats detected (my antivirus scans with MSE have also come up clean), so is this somehow a new feature or if not, should I be worried? P.S.: I've attached a text file of the scan report if that will help. mb scan.txt

I clicked on that update in the pinned thread but haven't downloaded it yet. In the file title it had (after 1.0.139) 1.0.2060 which I presume is the update package version. However, my current update package version is 1.0.2092. Would I be making a regression?