Since they would appear to be in an adaware temp location it could be that these are unpacked signatures that are being detected by avast when they are unpacked. This is one of the reasons I always pause standard shield before doing a scan with any other security software. It avoids potential conflict, double scanning (slows overall scan duration) and in this it would appear to detect unpacked signatures.
and it really started doing that after i updated avast. what the problem, and also before i updated avast the warning when i was scanning with ad aware never popped up.
Delete your Java cache to get rid of the .class malware. It looks like Ad-Aware is looking in the Java cache and avast! is detecting Ad-Aware’s temp files.
Looks like a thorough clean up is in order. If you download CCleaner from the link in David’s post, that will delete temp files and can be set to delete the Java cache.
There was nothing there to help, rather to try and explain why you might have got the detections and that they might be false detections.
that didn't help
So what did you do, that didn't work ?
The IE lock ups could be a coincidence, is your browser fully up to date, IE6 SP2 plus any updates after SP2 ?
If not I suggest you ensure it is fully up to date
and also before i updated avast the warning when i was scanning with ad aware never popped up.
There was me thinking I had explained why that happened (running adaware whilst avast standard shield is not paused), you have also had adaware updates since then also.
Whilst compiling this post, I started an adaware ‘Smart System Scan’ and didn’t pause standard shield and I haven’t experienced any warning or virus alerts.
The other thing that you should know is that the AAWTMP folder is only during the time you have an adaware scan running once completed and closed the temp files and AAWTMP folder are deleted.