Jump to content

The update to 1.37

Recommended Posts

Worked as expected on my XP Pro SP2 laptop. Had a bit of a hiccup on the desktop running Windows XP Media Center Edition SP2. On the MCE computer, the update was downloaded and installed, and then Malwarebytes did not open up again with a message that the update had been successfully installed. Taskmanager showed that it was running, but the program did not appear to be open. I double clicked the icon and was told Malwarebytes was already running. I ended the process in task manager and then was able to open Malwarebytes. It indicated that it is version 1.37.

I rebooted (because I do that after any program update) and Malwarebytes appeared to be running normally. It said it was 1.37, and I had it update again and it downloaded a different database (2183). I just ran a quick scan with it and it seems to be fine, no problems found.

I'm using the free version, and AVG free 8.5.339, along with the Windows firewall (my computers are behind a router), no other resident security software running in the background. I use SuperAntispyware free daily as an on demand scanner, and although I have an old version of Spybot S & D installed, I haven't run it in months and I don't have any of its resident features running.

Has anyone else had this happen during the update, and is it anything I need to worry about if things now appear to be normal?

BTW, if the developers COULD come up with a test file that we could trust and try, that would be great. ;) I saw that other thread, but I'm a bit wary of using a site that's not connected to or authorized by Malwarebytes.

Link to post
Share on other sites

I'm using the free version, and AVG free 8.5.339

The same here without any problems ;)

Malwarebytes' Anti-Malware 1.37

Database version: 2184

Windows 5.1.2600 Service Pack 3

27.05.2009 11:41:30

mbam-log-2009-05-27 (11-41-30).txt

Scan type: Quick Scan

Objects scanned: 68229

Time elapsed: 3 minute(s), 37 second(s)

Memory Processes Infected: 0

Memory Modules Infected: 0

Registry Keys Infected: 0

Registry Values Infected: 0

Registry Data Items Infected: 0

Folders Infected: 0

Files Infected: 0

Memory Processes Infected:

(No malicious items detected)

Memory Modules Infected:

(No malicious items detected)

Registry Keys Infected:

(No malicious items detected)

Registry Values Infected:

(No malicious items detected)

Registry Data Items Infected:

(No malicious items detected)

Folders Infected:

(No malicious items detected)

Files Infected:

(No malicious items detected)

Link to post
Share on other sites

Thanks, AdvancedSetup. ;) Maybe the database didn't get installed because I closed it too early in taskmanager and perhaps that's why I had to redownload that part of it. Hopefully I didn't mess up any other part of the update.

And I'm glad AVG is playing nicely with Malwarebytes.

Link to post
Share on other sites

I actually ended up deciding to uninstall and reinstall because I was worried that, having ended the process in task manager when I did the update, I may have messed up the installation of the update without knowing it.

The program uninstalls and reinstalls smoothly, which is nice. And at least now I can have some peace of mind. :P

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
  • 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.