Evidently FSS is scanning that file, as it would do with any html file in any other location. WS should scan “things” from a website (essentially). Avast is not interpreting this file as from a website, but as a file as any other.
I understand that, but what I meant is that the webshield should have got it first.
I understood what you meant. I just disagree with the “absolute” character of the assumption. If the file was not infected when you actually got to the original website (meaning the file was infected after that moment), or if Avast was not able to identify the specific malware in that same moment, then the FSS can find that file after that first moment, either because now the FSS now finds the infection (that maybe wasn’t there before), or because a new database update is able to find the infection (and previously, it wasn’t).
Just to be clear, I am NOT saying you are incorrect. I am saying that there are other possibilities other than “the Web Shield is not working as it should”.
If the WS was supposed to catch that and it didn’t, and just a few seconds after that the FSS warned you (with no database update in between), then you are correct in your assumption. But I would extend that a little bit forward. Why the Network Shield didn’t stop the file from being downloaded and saved in your system in the first place?
Well, the FSS alerted on the page loading, which is what made me assume that it was missed by the webshield…I see what you meant now, about my choice of words 
Either way, I am not exactly sure what is happening there…maybe this is slightly OT here, I don’t know.
Is the webshlock.txt file in that location, as I suspect that it isn’t and I don’t know if that is required to lock the for for scanning by the web shield. And subsequent removal from the folder on successful completion of the scan.
The webshlock.txt is in C:\Windows\Temp_avast_ where it should be.
It’s most likely the Script Shield, not Web Shield, and possibly has something to do with the IE Protected Mode.
neommy, are those leftover unp*.tmp files empty (0 bytes in size), or do they contain any data?
Furthermore, are you logged on as an administrator, or some other user?
Yes, that is where I would expect it to be along with the unp…tmp files. But I will bet there isn’t one in the C:\Users\Scott\AppData\Local\Temp\Low_avast_\unp208123638.tmp folder, which is what I’m on about.
e.g. If it isn’t in the same folder as the unp…tmp files:
No there isn’t one in the Temp\Low_avast_ folder, never was. 
Nearly replied to igor earlier but caught his edit ;D
They are 0 bytes in size, and do not contain any data.
As far as I know I am logged as an administrator.
That is what I thought and why I think content in that folder might not be being scanned or if it is, not cleared as there is no reference to the files locked by the web shield (web sh lock.txt).
That is my concern to coordinate this so that everything goes to the one folder whatever that happens to be. For me in XP Pro and Win7 32bit it is c:\windows\temp_avast_.
Whilst in my win7 netbook I don’t have the …\Temp\Low_avast_ folder, I do have an …\Temp_avast_ folder, but when browsing the web I don’t get any unp…tmp files in that location they all go to c:\windows\temp_avast_ folder.
So I don’t understand this disparity. Edit: perhaps this is used for other shields, such as the script shield as Igor mentions. If so I can’t understand the logic in this surely it would be best to use the one avast location.
A mí también me pasa lo mismo.
Este problema empezó cuando instalé la version de avast la 6.0.1289. y solo me pasa cuando utiliza el Internet Explorer 9.
Pd. Perdonar si escribo en español.
Ok for the members who do not read Spanish.
Solidacid, the poster above, says that the same is happening to him but just when using IE 9. I just mentioned to him, from Spanish Forum, that he was not the only one with this problem and up to now there seems to be no fix.
@ Solidacid
Si se llegara a encontrar una solucion te lo aviso en el hilo que tenemos en el foro de español.
Saludos.
Thank you Solidacid, nice to know that I am not all alone in this big world, ;D and iroc9555 for the English translation.
I am still having temporary files, I am using IE9, and Avast 6.0.1289, and all I can add is that the date of the beginning of this problem is at most 12-15 days before the beginning date of this topic.
Neommy.
Thank you.
After you answered igor question in reply # 29, he never got in touch with you afterwards ? I thought he could have had an answer to this glich.
Regards.
I’m afraid I don’t, as I wasn’t able to simulate the behavior.
I might try to get rid of the temporary files in the Script Shield altogether, which would solve the problem as a side effect, but I’d still like to know what’s causing this thing.
Igor.
Thanks for answering. This is a rare event.
Regards.
Well, this may not be such a rare event indeed;
I am deriving this result from the solution! After doing many things to solve the problem, ( actually my number one suspect were network adjustments at the control panel, I have the habit of playing with everything at my computer ) I finally did two more things;
- I made a deep clean at my computer, with Windows 7 64 Bits’s and IE 9’s own tools, and CCleaner. And then I uninstalled Comodo, both from the Control Panel then with its own community prepared uninstallation tool, rebooting many times, and deleting many times. I even used Registry Seeker just to delete " comodo " name from everywhere at the registry.
- Then I resetted IE9. From tools-internet options-advanced-I used both of the two tools here.
rebooted, and it was gone!
I reinstalled Comodo.
I now have one avast folder in Temp, and one avast folder in Temp-Low …But now no temporary file is produced, both of these avast folders are empty since one day! ;D