As I understand Close Message Handling's security "concept", it is a tool to alert a user of potential unauthorized closure of key/critical security programs...along with other possibilities. Here's what happens when I provide Close Message Handling on Lavasoft's Ad-Watch which is the memory resident spyware/adware blocker of AdAware6 Plus/Pro. 1. Three consecutive HID's appear as various modules start to close on Ad-Watch termination. Each require HID confirmation. 2. Then the MS error alert appears stating that Ad-Watch encountered an error and has to close. I confirm. 3. A fatal exception error box then appears. I confirm that. 4. Another HID box follows and I confirm. 5. Another HID box follows and I confirm. 6. After #5, the HID will not close...just sits there. Each time I click OK, it beeps and nothing else happens. I cannot X it out or get rid of it. 7. A reboot of the computer appears to be the only next step. Okay. I tried this on 2 other security type programs and the same sequence of events occur. I don't mind the multiple HIDs at the beginning, but the error box and fatal exceptions cause me to have to reboot. Thus far the only Close Message Handling "security" application that seems to work smoothly is on PG itself....at least on my block of security programs. Any help/guidance on this would be appreciated.