Seems like doing a Program update worked!! Been 15mins without a notice. BTW I could do without the Avast gadget, the sys tray icon does a good enough job of letting me know if I’m secure or not.
I did another program update about 10mins ago and it seems to have cleared up the problem.
I reported it as a false positive at the same time it stopped showing up so either the definitions update fixed it, or avast is now ignoring it.
Essexboy, I too have the exact same problem following a Windows 7 64 Bit update to SP1. How can I upload a false positive from the chest other than restoring? If I choose this option, Avast will keep on picking this file up as a Trojan.
NoordZee update your avast program and definitions and see if its still happening.
I got the same annoying problem just after installing Service Pack 1 from Microsoft. I do not know what to do…The warning keeps appearing every few seconds.
After doing the update it was clear until a minute ago when:
BING BING BING BING Threat Detected …
AHHHHHHHHHH!!!
http://forum.avast.com/index.php?topic=72696.0
I think if you manually update your virus definitions to the latest version 110301-2 it supposedly fixes the problem.
Nope, see post above…
Just updated the virus defs at the very last version 010311-2, but the problem is still here >:(
After updating program and definitions I rescanned c:/windows/Microsoft.NET folder and no threats were found. Thinking the update might have cleared the false positive I extracted mscorlib.dll from the virus chest back into c:/windows/Microsoft.NET and rescan and the same threat was detected. I updated program and virus definitions again and did a reboot thorough scan, which returned:
virustotal.com says its a FP. Is everyone sure avast stopped reporting this as a threat for them or is it just bc its in the Chest? I had like 32 copies of it in mine.
Same problem heare!!!:)
Object: C:\Windows\assembly\Native_v2050727…\mscorsw
Infection/; Win32.spyyey_BG[trj]
Aby ideas???
lucky me I haven’t re-installed Avast yet. For unrelated reasons here I re-installed Windows yesterday and mscorsvw.exe ran at a 50% CPU load during half and hour, three times (see screen shot). First time was after the install of “MS .net framework 4 client profile” through Windows update, second time through a security update for it, and finally a new update of the same stuff included in SP1 >>> = 01:30h of CPU @ 50%.
I ranted already about that on MS forum when the program was released. Just been told at the time that they were aware of that and it was wanted this way. Well as seen in task manager it’s an optimization phase ;D
Sorry for the off topic but it’s still about the same file 
Do you have a link to that thread on the ms forum?
filc, thank you. I am completely up to date but still went through the motions. When my computer restarted, the same message came up again. I believe that the only way we all can be sure that this particular file is not picked up as a Trojan is for Avast technicians to incorporate a ‘cure’ in the next update. As a matter of further interest, when I tried to restore the two files that reside in the Virus Chest, a message came up that the file in question is already in existence and would I like to replace it or overwrite it. Hm…!
(was related to .net 3.5 at the time)
May I ask why moving the file to chest fails and it’s hard deleted instead? Not exactly happy with the whole thing getting recompiled over and over again - which drains CPU like hell because of broken M$ .Net code. (For those who wonder - the CPU usage ain’t any fault of Avast, the “optimization” utility is just that shitty.) >:(
And no, 110301-2 virus definitions don’t fix it, in fact this version caused the issue here.
And no, 110301-2 virus definitions don’t fix it, in fact this version caused the issue here.
[/quote]
Doktornotor, I agree with you.
I wouldn’t mind if the OP of this thread corrected the title, making it clear that it’s obviously an FP.
Anyone who is still suffering from this problem can get temporary relief by uninstalling Service Pack 1. That was the only thing I could do to stop the constant pop ups. You can do this by going into the Control Panel, Programs and Features, click on View Installed Updates, and scroll down to the Microsoft Windows section. Right Click on Service Pack 1 and select Uninstall. Doing this will take several minutes, but seems to restore all of the previous Windows updates which were overwritten by Service Pack 1.