(Not Responding) when scanning C168.msi

[CaveCanem]

Malwarebytes completely Freezes when scanning C:\windows\installer\c168.msi about 1 1/2 to two minutes into a quick scan. CTRL/ALT/DEL failed to end task. This happened twice now. Powerdown was only option. Is this a virus that is not detected by Norton 360 3.00 or a bug?

What led me to install malwarebytes is that a scareware popup was not blocked and my brother may have clicked on it. What should I do?

[AdvancedSetup]

Its possible that it is a conflict between Symantec AV and MBAM.

You can try this. Disconnect from the Internet and disable Symantec AV. Then do a Quick Scan with MBAM and see if it still hangs or not.

When done, re-enable your Anti-Virus and connect back to the Internet.

[deathtospyware]

I think there is something screwy with Norton 360. I have had no problems installing and running MBAM on machines with Norton Internet Security but every machine I encounter with Norton 360 freezes during a MBAM scan. The solution, as Advanced said, is to disconnect from the Internet and disable 360's real time protection. MBAM runs fine then. Why the difference between the two products only Symantec knows and they ain't telling.

[brummie]

Hello all,

I have had virtually the same happen to me the other day, I am running 'Norton Sec. Suite 09', never had a problem with Malwarebytes till now! I scanned for about 3 mins and mine froze at 'Windows\Installer\14' or something like that, also had to power down. Re installed 3 times and same thing? Over on the Symantec forums people always recommend this software and it always appears to run very well with NIS, that is until now. I usually do a scan with M'bytes about once a week.

My system is XP Pro, SP3,

[brummie]

Following on from my last message, I did as you said AdvancedSetup, and scanned ok. I then re enabled Norton Int Sec. and again it froze at 'windows\installer\24707\msi'

I will post a thread on the Symantec forums and see what anyone there comes up with.

One last thing, the only item I installed during the past week was the 'Microsoft Office Converter Pack'

[AdvancedSetup]

We are currently reviewing possible fixes for this. So far we've not found the "common" cause of it.

[brummie]

Hello AdvancedSetup,

I did as suggested and went off line, disabled the 'AV auto protect' in my NIS and scanned without any issues. When I got back on line and re enabled the AV function, the next scan with Malwarebytes froze at the same file. (windows\installer\24707\msi)

There were a couple of people on the Symantec forums who said they had similar problems when scanning with Malwarebytes too! Tried to find the file in question with a view to deleting it (As was suggested to me over there) but cannot find it?

Just wondering if this occured after a recent update to the programme?

Thank you for keeping me posted with events.

[AdvancedSetup]

There is a link on the site here that goes into more details. Maybe when Exile stops by he can find and post the link in question.

Yes, recent versions of Symantec appear to be the issue but I don't have all the details logged myself, but there is another big discussion about it here.

[brummie]

Thanks, I will keep a look out for that as I would be interested in reading more about it!

[exile360]

Greetings, the thread in question should be this one. Prepare for a long read . The issue with Norton (particularly 360, but I suspect they recently changed a driver or something in their other products that causes the same conflict, but just guessing) is primarily discussed on the last few pages.

[brummie]

exile360, thanks for the link to that article, it made for some good reading and I've posted the link onto the Symantec forums re my thread there.

I just did something interesting regarding this problem. My pc and my son's one are joined on an ethernet cable and we both have Norton Security Suite 09. I checked his MBAM prog and it was last updated and scanned on Mar16th. (V.1.34)

I didn't update this but started a quick scan. It got to 'WINDOWS\Installer\350179.msi' and appeared to freeze. I hit the 'alt ctrl del' button and it showed MBAM was 'not responding'. I didn't delete but looked back at the prog and the file suddenly changed to 'WINDOWS\Installer\c9680cmsp' I waited 10 seconds or more and then it carried on scanning? When I looked in task manager it now showed MBAM running. The scan completed after 9mins and 31 secs, having scanned 70,000 items.

Don't know what you make of that but it would appear that something changed with the updated versions after v1.34?

[brummie]

I thought I would update this thread albeit it's a bit old now. I decided to scan my pc with MBAM, updated to latest database and went off line but instead of disabling my Norton Sec. Suite, (I found I could only complete a scan with this disabled since the problem first occured) I decided to leave it and see what happened. The MBAM scan completed without any problems at all. Quick scan completed in under 9 mins. Don't know if anything has been done behind the scenes but it seems to have righted itself somehow.

Was wondering if any others out there have experienced this too?

[Swandog46]

Yes, we made some changes. Thank you for the feedback! Can you please use MBAM normally for a few days and then let us know if it appears resolved.

EDIT: The changes were made to the database, in case anyone reading this is confused. To anyone else with a similar problem: update your database to the newest version and let us know if this resolves the issue.

Edited April 16, 2009 by Swandog46

[brummie]

Thank you Swandog46 for that info. I will do as requested and get back in a few days and update this post. I might also get back to my old thread on the Symantec forums and let them know there too!

[brummie]

It would now appear that this issue is resolved, having done a couple of scans over the past few days, each time updating the database, no problems were encountered.

[exile360]

Excellent, looks like the developers knocked out another kink in the system .