To: DaddyNoodles
I have verified that I now have v2.4.0.4 and yes, I still experience the problem. Since my upgrade to N360 v2 in Apr2008, I have always gone the Symantec Tech Support route for all my N360 v2 problems, but after having been told to make a clean re-install of N360 v2, I finally decided to check out the Symantec User Community.
For the benefit of all N360 v2 users that experienced this same problem, I would like to share the following:
- I have a Windows Vista pc;
- I used N360 v1 since Aug2007 and never once had to contact Symantec Tech Support for any problem;
- Since I upgraded to N360 v2 in Apr2008, all kinds of N360 problems came out --- some, more serious than this one;
- In my first encounter with this "Intrusion Protection" problem, I noted that even the setting that I turned ON in the Firewall_Protection:Intrusion_Prevention page was changed somehow to OFF. But, because I was logged on to my administrator account at that time, I was able to click the "Fix" button;
- Because of the myriad problems that I had with N360 v2 back in Apr2008, I decided to put N360 v2 on a tight leash: by, among other tasks --- manually checking for updates and running manual quick scans right after all HDD activity died down following pc start-up and log on;
- Probably because of these actions, I was fortunate not to have a repeat of the problem ... until sometime in the 2nd week of Sep2008! I immediately reported this to Symantec Tech Support and told them that some recent N360 v2 program update might be the cause. They replied that they will be releasing a patch soon. They must have been referring to v2.4.0.4;
- All went well until the 1st week of Oct2008. Being more vigilant this time, I noted that the problem re-occurred when I was in a hurry to get to work on the pc and failed to do my usual routine of forcing manual checks for updates and manual quick scans after logging on. Symantec Tech Support advised me to make a clean re-install of N360 v2. Because I found this recommendation too drastic, I decided to make some refinements instead: log on to my administrator account first right after pc start-up and then switch over to my limited account after completing the manual routine while at the administrator account;
- The problem still re-occurred when I deliberately ignored my manual routine while still in my administrator account. Although the N360 v2 status flag remained green, I did get the pop up with the same warning message regarding intrusion protection;
In the next few days, I will be repeating the same experiment to see if I can get repeatable results. I am trying to confirm my suspicion that: N360 v2 (and Liveupdate) needs to complete its initialization tasks within a pre-determined time frame right after pc start-up, otherwise; it will flag red.
