The problem described in the 2 posts in this subject was apparently due to a
fault in Ad-Aware SE Personal Definitions File SE1R91. DF SE1R92 does not
identify the Registry entry as Spyware.

Thanks to those who responded to the posts.