MalwareBytes and 195da22.msp

[Kirk Bubul]

My OS is XP Media Center Edition Version 2002, SP3.
After working flawlessly for several weekly scans, my current, updated
Malwarebytes Anti-Malware has twice hung ("not responding") when it
gets to C:\Windows\installer\195da22.msp. A full and complete scan
normally takes over an hour to complete, and the hangs has come at
about the 48-minute mark.

Thanks in advance for any ideas about what's going on.

 

[MowGreen]

How old is the .msp ? Did this happen with MBAM's previous definitions
or just the latest ones ?

Hover the mouse cursor over 195da22.msp and a balloon should appear
telling you the Type: and the Title: or, *right click* it, choose
Properties, then click the Summary tab and see if anything greyed out is
listed next to Title:


MowGreen
===============
*-343-* FDNY
Never Forgotten
===============

 

[ColTom2]

Malwarebytes Forum http://www.malwarebytes.org/forums/

ColTom2


My OS is XP Media Center Edition Version 2002, SP3.
After working flawlessly for several weekly scans, my current, updated
Malwarebytes Anti-Malware has twice hung ("not responding") when it
gets to C:\Windows\installer\195da22.msp. A full and complete scan
normally takes over an hour to complete, and the hangs has come at
about the 48-minute mark.

Thanks in advance for any ideas about what's going on.

 

[Kirk Bubul]

How old is the .msp ? Did this happen with MBAM's previous definitions
or just the latest ones ?

Hover the mouse cursor over 195da22.msp and a balloon should appear
telling you the Type: and the Title: or, *right click* it, choose
Properties, then click the Summary tab and see if anything greyed out is
listed next to Title:

Weird: when I tried to find this file, I can't find an Installer
folder under the Windows folder. And a file search doesn't come up
with a file by that name. But I carefully wrote down the file name
twice, days apart, and they match. Google and Bing don't give any
results for the file name.

This hangup has happened with the last two updates of definitions that
I have done, the first about a week ago and the second today.

 

[R. McCarty]

Explorer by default does not show Hidden, System & Protected files.
You have to modify the View options for those to appear. ( Folder
Options ).

If your system is up to date ( SP3 + Patches ) there is no Microsoft
patch file with that ID # on my primary desktop. Every machine varies
so the fact it's not on my PC doesn't mean your .Msp file is not a valid
component.

I'm not sure why you're doing a Full scan. That is usually something
that should be initially done. However, future runs with Malwarebytes
using a Quick Scan should be adequate.

If you do locate the file, I'd pay attention to it's file size. Most .Msp
modules are less than 10 Megabytes. Some may be as large as 110
Megabytes to 250 Megabytes.

 

[Kirk Bubul]

Explorer by default does not show Hidden, System & Protected files.
You have to modify the View options for those to appear. ( Folder
Options ).

Good point. I just did that. 195da22.msp is 6,818,816 bytes big and
was last modified 5/12/09 (which happens to be Update Tuesday).

If your system is up to date ( SP3 + Patches ) there is no Microsoft
patch file with that ID # on my primary desktop. Every machine varies
so the fact it's not on my PC doesn't mean your .Msp file is not a valid
component.

I'm not sure why you're doing a Full scan. That is usually something
that should be initially done. However, future runs with Malwarebytes
using a Quick Scan should be adequate. Didn't know this.

If you do locate the file, I'd pay attention to it's file size. Most .Msp
modules are less than 10 Megabytes. Some may be as large as 110
Megabytes to 250 Megabytes.

I updated the definitions and tried again. First a Quick Scan that
took only 5 minutes to be successful, followed by a Full Scan. This
time I watched closely. When the scan was about half done, at the 42
minute mark, it got to 195da22.msp. What I hadn't noticed before was
that when chewing on a large file, MBAM doesn't update the elapsed
time counter until the file is finished. Well, ol' 195da22.msp took
all of almost 28 minutes to scan. During all that time the elapsed
time counter stayed frozen at 42 minutes, 16 seconds. Once it was
done with that (I assume) huge file - see the paragraph above - it
partied on until finished at the 1 hour, 27 minute, 42 second mark.

Live and learn. I think that I mistook the "frozen" elapsed time
counter for a computer freeze. Then I tried to Pause and Abort the
scan until the top line in MBAM told me that it was not responding.. .
Either that, or the new Database Version 2265 that I downloaded just
before these last two scans was a fix for my original problem.

Whatever. Thanks for the responses and I'll be more patient in the
future.