When Will FP Win32:Malware-Gen be Fixed?

Like many others here, I also got the warning yesterday re: Win32:Malware-Gen on Avast. I scanned using MBAM, SAS, and Prevx and came out clean on 4 separate scans each. I also sent my EMPTY folder that Avast flagged as malware to VT yesterday, but they rejected it because it was empty. Thank you to others who had something in their folders because today (as of 20:30 Eastern Time - New York), VT is still reporting that only Avast and G-Data are still reporting Win32:Malware-Gen :[url=ftp://analisis/057d5999a4542f59deb950c82540efa155670286ddb1951ebc29f04befb304ef-1264969914]

analisis/057d5999a4542f59deb950c82540efa155670286ddb1951ebc29f04befb304ef-1264969914 [/url]

I have the lastest update of Avast definitions to v. 100131-1. Any idea when this FP will be fixed? Thank you.

Hi. I’m having the same issue, so I hope you don’t mind if I add to yours.

I have one .exe file I’ve had on my computer for the past two years come up as a virus the other day as “Win32:Malware-gen”. The VPS has been updated twice since then, but it still alerts as a virus. I also ran it through Virus Total, and 2 out of 40 showed up as malware (Avast and GData).

I guess my question about this is; Does Avast need to evaluate/isolate each program identified? Or is there a blanket fix for “Win32:Malware-gen”?

Avast had a global problem with a FP back in December 2009, but they were able to fix it with the following definitions update and they were much quicker to respond to the FP than this time around.

I read here in the forums that it was fixed, but not for me and others. I know it makes a difference what part of the world you life in when you get the update, but I’m looking at the actual version of the definition, and that’s the one I have that corrected it according to others…but not everyone (like you and me). So there is still a problem that Avast needs to address.

Between my original post and now, I did another complete MBAM, SAS, and Prevx scan twice more and I’m clean. I also went on the Wilder’s Forum and it was posted as a suspected FP with Avast that it was supposedly fixed with the last update 100131-1.

I hope they fix it with the next update! I’ll be much happier then.

I actually moved the “problem” file to a flashdrive until the fix is out. I have checked it with each new VPS update and it still sets off alarms.

I’ve had Avast for a couple of years now, but never posted to this site. Typically, I’ll just surf the forum until I find the answer to my question. But this latest issue doesn’t seem to be getting much attention, so when I saw your post, I thought I’d sign up and add my voice to the problem.

I lucked out back in December when that fiasco happened. I didn’t have my computer on when that one hit. A bunch of co-workers were fuming when that happened. (It was so bad that quite a number of them had to completely re-install Windows on their system. I don’t think they run Avast anymore.)

Well, hopefully some one from Avast will address this issue before long.

Well SafeSurf, I just received the latest VPS update 100201-0 and it still identifies my file as a virus, Win32:Malware-Gen.

It looks like the Alwil/Avast folks don’t think this problem is very important.

I’m disappointed. The one time I reach out for help and no one does anything to try and fix the problem.

I checked with the guys at work that were affected by the December problem, and they all abandoned Avast and now run Avira. I’m going to spend some time researching Avira this week and see how the computer world feels about their software.

I spent some time overnight reviewing a lot of older Avast forum issues, and it seems like over the past few months something has changed. The attitude of the Alwil/Avast folks has gone from great support to “it’s not our fault, check some other web sites for answers”. (The other thing about these forums, it’s hard to tell who is Alwil/Avast support. I see alot of answers from people who I think are just users like you and I. They can offer good advice, but they are in no position to fix the problems.)

Best of luck to you, SafeSurf.

Send the sample to virus@avast.com zipped and password protected with the password in the e-mail body with the subject “False Positive”.

You can also provide a link to this thread.

Hello,
I scanned this file with VPS 100201-0 and is not detected. Was there running some other scan during update that the new VPS wasn’t applied?

Milos

I sent the scan to VT while nothing was being scanned.

I am happy to say that Avast finally fixed the FP problem tonight with the definitions update to v. 100201-1. Thank you, but I hope in the future you can fix it quicker than several days.

I think this malware issue is causing a problem for me also. When I restart or close the computer down, AVAST lists a statement "removable medium attached or inserted in this computer, you need to remove it before closing.

How/where do I find the attached medium. The problem seems to have started with a Trojan Horse from the internet and apparently is tied in with “win32:malware” issues.

Can anyone give me advise? I am not very informed on how to deal with viruses or internal computer issues.

Thanks,
Bill


Welcome to the forums, Bill Saddler :slight_smile:

Removable “medium” (media?) would be something like a USB drive/stick, an SD card, or other similar media in a USB port or in a card reader. These should be removed before shutting down your computer.