Wow, thanks a lot!
Now... I can see that some of the extractions (of new virus definitions) failed with "Not enough space on disk error" during the file extraction. That's possible I guess - if there was a low disk-space condition during the update, the virus definition extraction failed - and made the problem even worse because the partially extracted folder remained on disk (and again and again, each time there was a little space - but not enough for a correct update - it got consumed by an incomplete one). Unfortunately some of the folders (the biggest ones) failed later, during a "preparation" phase... and the error doesn't really say what went wrong. Could have been a low-disk space as well (the preparation phase creates additional files, so if the previous extraction filled the drive up to its maximum...
I admit it sounds like a bit of a coincidence - to happen so many times, plus I can see the listing says 2GB free on the C: drive. On the other hand, I believe free disk space used to be sometimes reported incorrectly by the system, so I guess it can be the case.
You certainly don't want to edit the aswdefs.ini file and "move it" to newer definitions - they are not complete and Avast wouldn't be able to load them (if they were OK, the ini file would get updated automatically). I'd suggest to manually remove the folders other than the one referenced in aswdefs.ini (i.e. if aswdefs.ini still says 19020600 is the latest, remove all the newer ones). You can keep those whose name ends with _stream - those are streaming updates and they are actually being used to protect you, plus they are small anyway).
This should hopefully make some space on disk - and then try to update the virus definition (maybe even via the full update downloaded from our web). Of course, if you could free some more space on disk (in other ways, not just in Avast folder), that could help as well.
What happens when you do that? Does the number in aswdefs.ini finally change?
