As I understand it, Webroot made the very "wise" decision to protect critical system files by deciding what process was allowed to access them. I believe it was the critical shields technology... naturally when Ad-Aware scanned these processes/files, it would hang, as the Webroot software did not allow Ad-Aware to have access to them. This also occured with some other softwares such as ZoneAlarm I believe... presumably, Webroots update to SS gave Ad-Aware permission to access the files in question....... regardless of this fix though, the problem still remains...with this kind of protective method, you may alienate 3rd party applications by restricting the contact they may have with system files/processes.. the symptoms could be very very different... startup / shutdown problems / hanging applications / deadlocks etc... the only way to solve this problem is to turn off the shields in SS that are responsible...
//Chunk