Jump to content

Version 1.19


Recommended Posts

  • Root Admin

Version 1.19 (June 28th, 2008)

1. (FIXED) Various problems with update.

2. (FIXED) Improved protection module stability and speed.

3. (ADDED) Advanced detection schemes for Trojan.Vundo.

4. (ADDED) Windows version number to log file.

5. (ADDED) Support for Czech language.

Please post any comments regarding 1.19 in this thread.

Link to post
Share on other sites

Just updated through internal updater.

No problems to report here,

Great work! :P

Malwarebytes' Anti-Malware 1.19Versione del database: 899Windows 5.1.2600 Service Pack 3
22.22.10 28/06/2008mbam-log-6-28-2008 (22-22-10).txt
Tipo di scansione: Scansione rapidaElementi scansionati: 41921Tempo trascorso: 2 minute(s), 54 second(s)
Processi delle memoria infetti: 0Moduli della memoria infetti: 0Chiavi di registro infette: 0Valori di registro infetti: 0Elementi dato del registro infetti: 0Cartelle infette: 0File infetti: 0

Malwarebytes' Anti-Malware 1.19 (Italian version)

Quick scan - Elapsed Time 2 minutes 54 sec.

No malware detected.

Thank you very much :P

Best Regards

----------------------

Intel Core Duo 4300 - 4 GB RAM DDR2 800 - 160 GB HDD Maxtor

Firefox 3.0 - AVIRA Security Suite 8.0 - SpyBot Search & Destroy 1.5.2 - SuperAntiSpyware free 4.1, Winpatrol 2008, Java Cool SpywareBaster 4.1

Link to post
Share on other sites

Installation went smoothly and everything seems to be working fine :P

As fast as ever - Hope you don't mind if I ask a question - With the growing number of detections, how to you keep the scan times super fast?

Malwarebytes' Anti-Malware 1.19

Database version: 899

Windows 6.0.6001 Service Pack 1

21:28:30 28/06/2008

mbam-log-6-28-2008 (21-28-30).txt

Scan type: Quick Scan

Objects scanned: 35068

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

  • Root Admin
With the growing number of detections, how to you keep the scan times super fast?

Well, a few ways.

1. We keep optimizing our code, finding faster and faster ways to do everything.

2. The bottleneck is not the actual definitions, it is reading the data from the disk, for example file enumeration.

Even if we had 1,000,000 extra detections, the scan times would not be significantly slower. If you had 1,000 extra files however, that would be the limiting factor. So finding faster and faster ways to read files and interpret them is where we spend most of our time.

Link to post
Share on other sites

Update went well, uninstalled and reinstalled. NO problems to report.

Malwarebytes' Anti-Malware 1.19

Database version: 899

Windows 5.1.2600 Service Pack 3

11:24:59 PM 6/28/2008

mbam-log-6-28-2008 (23-24-59).txt

Scan type: Quick Scan

Objects scanned: 44130

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

Hello Marcin

Used Protection Module Scheduling auto updates and Quick scan auto options, no problems or errors to report. No pre-ATF-Cleaner scan, very fast indeed. Nice work :P

1. Malwarebytes' Anti-Malware 1.19

Database version: 900

Windows 6.0.6001 Service Pack 1

6:51:36 PM 6/28/2008

mbam-log-6-28-2008 (18-51-36).txt

Scan type: Quick Scan

Objects scanned: 37746

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

No problems or errors to report in the Full scan mode, still fast :P

2. Malwarebytes' Anti-Malware 1.19

Database version: 901

Windows 6.0.6001 Service Pack 1

9:08:43 AM 6/29/2008

mbam-log-6-29-2008 (09-08-43).txt

Scan type: Full Scan (C:\|)

Objects scanned: 102358

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

Link to post
Share on other sites

Internal update. No problems.

Malwarebytes' Anti-Malware 1.19

Database version: 900

Windows 5.1.2600 Service Pack 3

6:25:15 PM 2008-06-28

mbam-log-6-28-2008 (18-25-15).txt

Scan type: Quick Scan

Objects scanned: 57597

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

Link to post
Share on other sites

No, problems at all with updating to version 1.19:

Malwarebytes' Anti-Malware 1.19

Database version: 901

Windows 5.1.2600 Service Pack 3

2:10:54 29/06/2008

mbam-log-6-29-2008 (02-10-54).txt

Scan type: Quick Scan

Objects scanned: 42478

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

Thank you and have a nice weekend.

Mona.

Link to post
Share on other sites

hello

pc1 win xp pro sp2 with Mbam full version Avira Antivir Pe Online Armor 150 beta

i uninstalled mbam 1.18 with revo uninstaller and installed mbam 1.19 with no problems

restarted now with the realtime guard on about every 30 sec. i'm getting mbamservice.exe

using cpu for about 30 sec. it goes up and down between 90% 20% 40% 10%

so i made Avira Antivir not start at startup and it is still the same so i made OA 150 beta

not start at startup and it's still doing it with windows firewall and just mbam 1.19 running

i'v restarted a bunch and it's still the same

in event viewer after installing i still get 1 error eventid:1 mbamservice

The description for Event ID ( 1 ) in Source ( MBAMService ) cannot be found. The local computer

may not have the necessary registry information or message DLL files to display messages from a remote computer.

You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details.

The following information is part of the event: MBAMService, Error: MBAM driver unloading failed.

also i email my mbam log from 1 pc to the other with yahoo to post it here and when i opend the attachment i sent

mbam must of tryed to scan it because in event viewer i see this about the sametime i opend it but i'v

tryed to get mbam to do it again but i doin't see it in event viewer now when i try to do it again

theres about 62 errors eventid:1 mbamservice

The description for Event ID ( 1 ) in Source ( MBAMService ) cannot be found. The local computer

may not have the necessary registry information or message DLL files to display messages from a remote computer.

You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details.

The following information is part of the event: MBAMService, Error: Scanner::GetMD5 failed.

with the realtime guard on the quick scan take longer to start and run but with it off it scans

faster

Malwarebytes' Anti-Malware 1.19

Database version: 900

Windows 5.1.2600 Service Pack 2

3:45:46 PM 6/28/2008

mbam-log-6-28-2008 (15-45-46).txt

Scan type: Quick Scan

Objects scanned: 40561

Time elapsed: 4 minute(s), 27 second(s)

Malwarebytes' Anti-Malware 1.19

Database version: 900

Windows 5.1.2600 Service Pack 2

4:06:42 PM 6/28/2008

mbam-log-6-28-2008 (16-06-42).txt

Scan type: Quick Scan

Objects scanned: 40571

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

pc2 win xp pro MCE sp2 Mbam free Online Armor free 2.1.0.131 Avria Antivir Pe

updated mbam to 1.19 from within the program with no problem

Malwarebytes' Anti-Malware 1.19

Database version: 899

Windows 5.1.2600 Service Pack 2

1:15:36 PM 6/28/2008

mbam-log-6-28-2008 (13-15-36).txt

Scan type: Quick Scan

Objects scanned: 41521

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

thanks

:P

Link to post
Share on other sites

Updated to V1.19 through the internal updater. Quick scan ran fine. Full Scan caused BSOD. I tried to upload the dmp file, but received a message I am not permitted to upload this type of file, so I uploaded through this link http://uploads.malwarebytes.org/

Protection Module is running fine.

Malwarebytes' Anti-Malware 1.19

Database version: 901

Windows 6.0.6001 Service Pack 1

8:31:11 PM 6/28/2008

mbam-log-6-28-2008 (20-31-11).txt

Scan type: Quick Scan

Objects scanned: 36015

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

sysdata.xml

Version.txt

sysdata.xml

Version.txt

Link to post
Share on other sites

Hi everybody, this is my first message here :P

I've updated to 1.19 with the internal updater, and now the full scan blocks after 1 min or 2. It just freezes and I have to quit the program with the task manager.

I have Vista SP1, with Kaspersky 7.0 and Spyware Doctor 5.5 running, I don't know if it's related. Version 1.18 was running just fine.

Bye.

Link to post
Share on other sites

Clicked on 'Update' to update to new version.

- new version d/l and install started but failed.

- installed as far as Registering files....

- Error with the following message: c:\Program Files\Malwarebytes'Anti-Malware\mbaext.dll Unable to register the DLL/OCX: RegSvr32 failed with exit code 0x5.

Aborted install - rolled back.

I then opened +/- Progs and uninstalled from there.

Downloaded the full program and it failed to install at the same point with the same message.

Any ideas?

XP SP3 fully updated

OA Beta 150

NOD32 3.0.667.0

SAS Pro 4.15.000

Rgds

chalawah

Link to post
Share on other sites

You need to uninstall, restart, and reinstall. The restart will delete the files that were in use.

Hi DuckY,

Apologies. I didn't make it clear that with the second attempt to install 1.19 - from the +/- Progs the uninstall process prompted for a reboot and restart.

The second failed attempt came after this reboot and restart.

I have tried again with OA beta Program Guard turned off and I get the same results.

Cheers,

chalawah

Link to post
Share on other sites

Last night I ran a scan with Avira Free (full scan) and it also caused a BSOD. I then turned off the MBAM protection module (after disconnecting from the net) and ran the Avira scan with no problems. I did not have time to run a full scan with MBAM with the protection module off to see if it would work that way. The MBAM full scan has caused two BSOD with V1.19 while the protection module is on. Not sure if you want the BSOD dmp file from the AVira crash. Thanks

Link to post
Share on other sites

hello

well i uninstalled OA beta 151 cleaned up and then uninstalled Mbam 1.19 and reinstalled

Mbam 1.19 with just windows firewall and Avira Antivir Pe and i still get Mbam using

cpu every 30 sec. or so and sometimes that error in event viewer about Mbam's driver

not unloading on restart

then i uninstalled Avira Antivir Pe cleaned up ran Avira's reg cleaner then uninstalled

Mbam 1.19 and cleaned up reinstalled Mbam with just windows firewall running and i still

get Mbam using cpu every 30 sec. but after like 8 or so restarts of the pc i doin't see

nothing in the event viewer about Mbam's driver not unloading

thanks

:)

Link to post
Share on other sites

I didn't notice it at all until I had updated today and yes it was from It-Mate server. I can't seem to keep it on Malwarebytes.or for the location to update from it always goes to either It-Mate or Malware support. I installed from Major Geeks.

LOL WoW I just did an update and did it from MWB and it's fixed!

Link to post
Share on other sites

Guest
This topic is now closed to further replies.
  • 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.