Tech

chrome.exe is being detected as infected...

Well, it was not my intention (OP) to get this far (neither the tone of the arguments here). Keep your good work.

Thanks. Keep your good work.

Oh, forgot the source link: http://www.askvg.com/free-1-year-license-of-malwarebytes-anti-malware-premium-edition

Recently, I've read about the effort of MBAM against piracy and the reward of a lifetime license for the users who use a pirated key of MBAM. Well, it's an honorable effort. But, in the next moment, I've though. And what about the loyal users of the free version (which recommend MBAM to a lot of other users)? Should I become a pirate?

I'll add f.exe to the MBAM exclusion list. I have no other solution. Thanks for the support.

Me too. Never did it. Hmmm... SMART status seems ok. The only one with problems is MBAM... strange uh? A month more or less... I've dropped the use of Belarc as it was not adding me any *useful* information. I'll try it again. I'll try. Hmmm... Seems we cannot do anything else?

It's not avast (at least, not the resident) as the results are the same (Process Monitor is the same and MBAM detection is the same).

Yes. I use avast for sure (5.0.454 and the latest virus database). What could have corrupted the directory structure? I've run chkdsk /F more than once and it did not correct anything though...

Yes. I use avast for sure (5.0.454 and the latest virus database). What could have corrupted the directory structure? I've run chkdsk /F more than once and it did not correct anything though...

Ok

Please, elaborate. Chipset drivers? Which hardware? I have none offered by Windows Update and this is a Dell Vostro 1510 with Windows 7 32 bits fully updated. I'm a little afraid to mess with drivers... the last time I've done I need to fully reinstall Windows 7. It's a high price.

Here is another test, with different filters but seems the same results.

Here are both screenshots. The filters and the results. Hope we're getting close of it. Thanks for the support.

Please, help me. I'm not used to Process Monitor. I've run it and scan with MBAM. I've added two filters: mbam.exe process and C:\ folder. I've got the picture, but I don't know how to interpret it.

I used Macrium once (it's installed, but I never use the backup to recover). I'm not with my external disk with the backup. Maybe tomorrow morning. But I really doubt that a file called f.exe ever existed or was backuped... What will I monitor with Process Monitor? A file that does not exist and a process that is never there? ???

Noticed that someone downloaded the logs. Thanks for the support.

Sure. I'll upload them. I can run the tools again, but I think I'll get the same result. They was extensively analyzed by a malware expert of avast forum (Essexboy) (http://forum.avast.com/index.php?topic=59953.0 and http://forum.avast.com/index.php?topic=58921.0). Infection.zip

Exile, the properties are exactly as you've posted.

Exile, the properties are exactly as you've posted.

Exile, the properties are exactly as you've posted.

Sorry for the double (triple) post... I don't know what happened I've tried to boot from a CD (both Linux and DOS) and could never find a file called f.exe. There aren't any references into Windows Registry also. Can anybody help? I'll give up on MBAM if I can't solve this issue. It's the logical of the lack of support. I've tested my computer with ComboFix, OTL, OTM and GMER. Neither of them find the file. The problem seems to be inside MBAM. If not, please, guide me.

The file is gone after boot. But the next MBAM scanning detect it again. It's not shown in Windows Explorer (even unhidding files). I'm afraid to change anything with Microsoft Fix as it is the root driver (C:\).

The file is gone after boot. But the next MBAM scanning detect it again. It's not shown in Windows Explorer (even unhidding files). I'm afraid to change anything with Microsoft Fix as it is the root driver (C:\).

The file is gone after boot. But the next MBAM scanning detect it again. It's not shown in Windows Explorer (even unhidding files). I'm afraid to change anything with Microsoft Fix as it is the root driver (C:\).