Jump to content

Version 1.21


Recommended Posts

  • Replies 72
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Just updated ran a quick scan and all went well. Thanks Marcin. :)

Malwarebytes' Anti-Malware 1.21

Database version: 967

Windows 5.1.2600 Service Pack 3

12:42:44 PM 7/19/2008

mbam-log-7-19-2008 (12-42-44).txt

Scan type: Quick Scan

Objects scanned: 38195

Time elapsed: 2 minute(s), 30 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 RubbeR DuckY. I don't believe I get any refund. I think MBAM is a good program and I am willing to wait for the registration fix as long as it is in the pipeline.

Sinerely,

Lu Chin

Lu Chin,

Have I ever issued you your refund? We found the problem and are currently reprogramming the entire protection module. The fix should come around then

Link to post
Share on other sites

Installed via the program, only thing out of norm was a popup telling me the program was already running during the install. This was true, I clicked ok and the install completed and asked for a reboot. I said ok, machine rebooted, I updated manually and ran a quick scan.

Malwarebytes' Anti-Malware 1.21

Database version: 967

Windows 5.1.2600 Service Pack 2

11:39:31 AM 7/19/2008

mbam-log-7-19-2008 (11-39-31).txt

Scan type: Quick Scan

Objects scanned: 38070

Time elapsed: 5 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

Updated well using the internal updater, no problems to report.

Malwarebytes' Anti-Malware 1.21

Database version: 967

Windows 5.1.2600 Service Pack 3

8:27:01 PM 7/19/2008

mbam-log-7-19-2008 (20-27-01).txt

Scan type: Full Scan (C:\|)

Objects scanned: 91876

Time elapsed: 32 minute(s), 14 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)

--------

Thanks

Link to post
Share on other sites

FYI, I encountered the Code5 error message when attempting to upgrade to v1.21 via the internal program updater. This is the second version update out of the last three wherein I have been unable to update via the updater. v1.20 worked okay, but v1.19 & 1.21 produced Code5 errors that required that I uninstall the existing version, then install the new.

Just wanted to report that to you. It's not a big deal or anything. :)

Same thing happened with a second computer. Code5, had to uninstall in order to install. This was all based on using the internal program updater and following the instructions given during that process.

Both computers running WinXP Home SP3 with MBAM being used as on-demand scanner.

Link to post
Share on other sites

Well I'm glad that most people are reporting that v1.21 is working for them but over 12 hours ago I posted that I can no longer install v1.20 or indeed v1.21. I've tried several times, completely uninstalling and rebooting before trying another install but I still see these code 5 errors. Any suggestions?

Link to post
Share on other sites

I've tried that, several times. The program installs but doesn't run. I can't remember the error message now but I think it made reference to a file that couldn't install as it's not properly registered.

Edit: I've just tried again and I get Run-time error 339 and the option to send a report to Microsoft. I also get an application error that refers to an instruction at 0x773f65f1.

Link to post
Share on other sites

  • Root Admin

ihatespam, what operating system are you installing it on?

I'm trying to figure out what all of the systems that freeze have in common. I have tested it personally on 7 systems (Windows XP, Vista, with service packs and without) now and can not reproduce this freeze.

Link to post
Share on other sites

This happens when the shell extension is in use, that's why it can't overwrite it :).
So what is a user supposed to do with that information? I have no idea why the shell extension is in use. All I know is, I open the program, click on "Check for updates" and follow the prompts. Then I get the Code5. At least tell the user to uninstall the existing version prior to installing the new one. Or tell us how we should close the shell extension. All I do is scan with the program then click on Exit. Does that leave the shell extension in use?
Link to post
Share on other sites

Just want to clarify that with 1.21 on my XP SP3 systems, a Quick Scan that normally took 2-3 minutes with 1.20 now takes 20+ minutes. mbam hangs (more accurately a long pause) after the first 10-15 seconds of scanning or so, trying to exit at this point creates an application hang event ID 1002 error by mbam.exe in windows (basically a non-responding application). A Quick Scan will finish if you let it but it takes 20+ minutes. It seems to scan then pause, scan then pause, cpu usage for mbam.exe drops to 0 when it pauses, and mbam is non-responsive during the pauses. Turning off TeaTimer and SD Helper in Spybot does not help, nor does turning of Spywareblaster, nor does turing off all AV real time scanning.

I am also getting this fp with mbam 1.21:

Registry Data Items Infected:

HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Internet Explorer\Control Panel\Homepage (Hijack.Homepage) -> Bad: (1) Good: (0),

when Spybot S&D "IE Tweaks-Lock IE start page against user changes" is ticked.

Hope this info helps.

Link to post
Share on other sites

I don't know if this might help: I have OA firewall installed, AVG 8.0 (paid version), SpywareBlaster with all protection enabled and RogueRemover Pro with immunized protection enabled and they were all running/enabled when updating and installing version 1.21 yesterday. Even Scotty remained silent.

Still no problems when running a scan (with MBAM's protection module always enabled when running them):

Malwarebytes' Anti-Malware 1.21

Database version: 969

Windows 5.1.2600 Service Pack 3

9:03:43 20/07/2008

mbam-log-7-20-2008 (09-03-43).txt

Scan type: Quick Scan

Objects scanned: 43501

Time elapsed: 5 minute(s), 2 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

Kindly regards,

Mona.

Link to post
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • 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.