I came down with this same issue early in the morning of Sunday 9/25 after running an Avast! Full Scan. It found the exact same 3 "corrupt" files that you show on your screen shot. I followed Avast! instructions and moved them to the Chest (it wouldn't move the 3rd, probably because it had already done that with its doppleganger, the 1st file)...I then continued following Avast!'s instructions and ran a boot-time scan. The pc rebooted after that and I experienced just what someone else on the Forum mentioned: after the reboot the system (Windows 7) seemed fine but Avast! wouldn't run, most of the applications wouldn't run (my Control Panel was not, however, empty, and seemed to work normally). Virtually all of the rest of my applications were DOA (e.g., Firefox, Word, Excel, Avast!, IE, folders, etc.). Clicking on an icon for, let's say, Ad-Aware, wouldn't move you there. Nothing would happen. The speculation is that this was caused by moving kernel32.dll to the virus Chest...was this a system file? - c:\windows\sysWOW64\kernel32.dll|>[emul]) which was actually NOT infected (a false positive). I used a similar solution to what was suggested: In the Command Prompt type SFC /Scannow. Once it's finished corrupted files will be repaired and your .exe's will work once again. After running the scan (about 25 min) I received a note from Windows saying "Windows Resource Protection found corrupted files and successfully repaired them. Details are included in the CBS.log windr\logs\CBS\CBS.log" After that message I rebooted and ran a new Full Avast! scan: it found no problems. More importantly, the pc appears to be running normally again.
All of this leads me to an overwhelming question: When given a "Threat Alert" after or during an Avast! scan, how does one who is not savvy with computers differentiate between a genuine virus (which needs attending to and needs to either be removed or moved to the virus chest) and a false positive which probably should be left alone?
Thanks.