New
#11
Thanks for the update people.
Cheers
When the 22.5.5.15 patch was announced, I was already on 22.5.4.24 and had the problem with the greyed out autoprotect that 22.5.5.15 fixed. Liveupdate did say it upgraded the engine but I remained at 22.5.4.24 but the autoprotect problem was gone so I'm not in a hurry for the 22.5.5.15 as apparently I got updated to the same version except some files were changed in the engine. I might have newer updates too but as of now it's still 22.5.4.24 and I'm using Norton Security 2016. I just wished they updated the installers as just like Windows Update, the liveupdate is done in phases except it was announced on November 26, 2015 and it's almost a month.
I actually was running Norton 360 Premier 22.5.4.24 until a month ago and I always had that problem ever since August 2015 while 22.5 worked fine under Windows 7 HP without problems. Something else is triggering that problem which 22.5.4.24 was supposed to fixed but apparently didn't. Symantec has always been a little on the buggy side with their products compared to Peter Norton Computing as I and others have experienced for the last 27+ years, they turned good products into buggy ones with their acquisitions of Delrina (WinFax), Norton (Norton Utilities) and the other tools from Quarterdeck and the company that made the product that became Norton Ghost.
Like I said earlier My Norton has NO problems, why you did, I have no idea. I also have reinstalled my version twice, completely removing previous ones, then reinstalling same version again. Had to remove Norton before I did my clean install of Windows 10 Pro. Then after installing Windows 10, I ran Windows firewall and defender for about 3 to 4 days, then reinstalled my Norton again. And I always use Norton's un-install app which completely removes Norton. All I know is I have no problems running Norton with Windows 10 Pro what-so-ever!!! :)
Except you're in the minority, just like with Norton 360 before, some people had Norton's icon show up twice which never got fixed, I saw that problem before too but it disappeared on it's own. Otherwise it wouldn't be on the critical fix list as what both 22.5.4.x and 22.5.5.x fixes. This has nothing to do with installing or uninstalling as it is conflicting with something.
Just saying it works with Windows 10 doesn't mean much as it all depends on how many applications and what applications you have installed. There are normal users and there are power users. My system is not the typical system either as I have a few hundred applications installed so all OSes and A/V's will get pushed to it's limits.
It's listed under Hotfixes:
HOT ISSUES FIXES - NIS/NAV/N360 22.5 | Norton Community