Did you give the upload a unique name, so they can identify it as yours ?
I also tend to create a text file (readme.txt) with any relevant information, avast topic URL, user name, etc. etc. in the zip file. Not to mention posting the name of the file you uploaded in the topic acts as another searchable reference.
You don’t have read access on the incoming folder, so you won’t see it there. Only if you uploaded it using an FTP program/process would you get confirmation that it was uploaded successfully.
I have the same handle leak problem myself. Win7 Home premium 64-bit fully updated and using the free version of Avast 6.0.1367. Presently AvastSvc.exe (32-bit) is using a massive 138932 handles! Number two in line concerning handle usage is “System” with 4363.
Could the leak come from one or more 3rd party components Avast is using? Like SQLite, HTMLaylout, libPNG, UPX, Zlib etc…
EDIT:
Using Services to stop and then restart “avast! Antivirus” a.k.a. AvastSvc.exe - note that for security reasons I disconnect/connect my UTP cable during this operation - which btw only takes a few seconds, results in a handle count of a much more reasonable 900!
Up to over 100k handles now, not sure how something like this gets past testing, especially since it doesn’t seem just limited to this process either judging by the other thread.
Is this issue now being addressed or is a Full(?) Dump file still required? Incidentally when the Handle Count got up to 58,000 on my WinXP/SP3 system with 1GB memory, the network server stopped working and I got a System Event ID 2020 from Source Srv with “The server was unable to allocate from the system paged pool because the pool was empty.”
When I look at the AvastSvc.exe handles with Process Explorer I see that there are multiple occurrences of the same handles, in particular the “defs” files, e.g., F:\Program Files\Alwil Software\Avast5\defs\11122102\s_idx.map as well as handles for the previous version of the “defs”, e.g. F:\Program Files\Alwil Software\Avast5\defs\11122101\s_idx.map. Perhaps there’s a clue here?
Unless avast releases a new program update really soon (which I doubt), I would suggest first to back up your license file (if you have a paid-for edition), then to uninstall avast, run the specific aswclear.exe removal utility under Windows Safe Mode for BOTH avast 6 and avast 5, selecting the correct folder too.
Then remove any (hidden) folders with “avast*” or “alwil*” as part of the name. Download the latest stable version and install anew. Reboot immediately after the installation process finishes.
I’m NOT saying this will completely solve your particular problem, but since you already have some troubles, then maybe eliminating previous remnants (of previous avast versions) could potentially help.
The latest stable installation would not be just an update from avast 5 to 6 (as you currently have), so some of the issues could be potentially solved. Unfortunately, I can’t assure you this will solve any problem.
Any chance you could provide a fixed version of the AvastSvc.exe that we can replace manually? Waiting until the next full program update could be months from now and since I rarely reboot my computer my AvastSvc.exe is currently using over 140k handles.