mbmadiw wrote:
The computer previously used an older NIS (maybe 2006?). It was uninstalled about a year or so ago and replaced with AVG and Spamfighter. I uninstalled those just prior to installing NIS 2009.
I have tried turning off the Antispam as you suggested with a restart, but that didn't work.
There is another profile on this computer. So, just out of curiosity, I logged into it and opened Outlook. The Antispam integrated just like it's supposed to. I went back to the first profile and it still wouldn't integrate into that one.
MB,
Consider the following solution. It takes a little time, but might save you a big headache:
1. Create a new user with a name you like.
2. Make sure the Antispam integrates correctly. If so, ...
3. Copy all the data files from your previous identity, BUT NOT THE SETTINGS (recreate those settings if you want, but don't import them!).
4. Leave your old identity alone for a month or two until you are CERTAIN there are no items left in the previous identity (financial data, tax data, pictures, etc) that you haven't yet copied. Then delete the old identity using the COMPLETE erase option.
5. I don't recommend re-using the old user name even if you liked it. However, if it is important to you, then
a. user windows explorer to get to and delete the old identity if it is still present in the file structure.
b. if you are competent at editing the registry, make a copy of the whole registry first, then do a search for ANY references to the old user name and delete those entries.
c. get a good registry cleaner and look for any broken links (in particular, references to the old user name) and delete them; then repeat until no more problems are found.
Comment: I suspect that you have an upper level (User-name specific) corruption in your registry or -- more likely -- your Documents and Settings files. Searching out and fixing corrupting or missing files is a pain; this strategy should be a lot easier.
P.S. By "corrupting file" I don't mean a corrupt file, but rather a file that is itself okay but which leads to corrupt behavior when it is run. This file might be an artifact of a previous installation, a file that should have been replaced in an update but didn't get to be because the update was interrupted, a file that was replaced during a System Restore but which is no longer appropriate -- the possibilities are endless.