From a user in support system:
Anyone comment on this?

Working fine here on XP Pro Tom.
give me a few minutes and I will check on Vista too.

No Problems on 32 or 64bit Vista.

Hi,

I was the one who reported the bug.

I was using XP 32bit.

This issue is reproducible with 2 other computers (with XP 32bit).
Will it be helpful to add the log file for this execution? ("mbam.exe /debug").

Is there is something to do with that when running as administrator?

Thanks for your help,
Elad.

Anyone can help me with this?

I'm still having the same issue (also tried it after updating today)...

Thanks..

I too reproduce this problem.

The database version field is blank when i run mbam.exe /debug and export the file.

But if generate the log thru the main UI, it populates the database version.

I am running MalwareBytes version 1.30

It also happens with MalwareBytes version 1.34
Snippet from log:
"Malwarebytes' Anti-Malware 1.34
Database version:
Executable location: C:\Program Files\Malwarebytes' Anti-Malware
Database location: C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref
"

Well I'm "glad" I'm not the only one having this problem.

Is there any solution for this? or any upcoming fix?

Using the latest version here, Vista 32 home premium under a standard user account.

Using run and 'mbam.exe /debug' it asks for the admin password and then asks me where to save the file. It saves it as mbam-info.txt and the beginning shows this:

Malwarebytes' Anti-Malware 1.34
Database version:
Executable location: C:\Program Files\Malwarebytes' Anti-Malware
Database location: C:\ProgramData\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref

Running the collect information tool via MBAM itself results in this:

Malwarebytes' Anti-Malware 1.34
Database version: 1861
Executable location: C:\Program Files\Malwarebytes' Anti-Malware
Database location: C:\ProgramData\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref






But here's the strange part: (Possibly another bug?)
If I leave MBAM to create the info as the defualt name (through either the /debug command or through the GUI), it will create the file with a .txt extension.
However, while making these info files on my desktop I started renaming them so they wouldn't overwrite. I changed the name in the 'save as' box to 'mbam-info 3', and the resulting file was NOT a .txt file. In properties the file type is listed as 'file'. In the 'save as' box, even though I changed the name (there was no extension on the name as I have windows set to hide them) the little 'file type' drop-down was still set at text document, but it doesn't save as one if you modify the name. Strange. If you modify the name at all it saves as a file, not as a .txt.


Also, anyone find it amusing that the debug feature has some bugs???

Well, it seems like the "/debug" feature does have more than one unexpected behavior.

Insomniac, did you find any solution for running "mbam.exe /debug" and get the expected results?
I mean, with the Database version?

Thanks.

No, but I didn't look too hard for a solution as I've only used the /debug feature once, and that was to test this bug .