It looks that there have been some changes in the way that the latest build of NIS loads.
When the system boots, W7 x64, the systray icon is no longer present at startup, and it only appears when the nis.exe*32 user, loads, one minute after the system boots.
Sometimes it shows a red X for a fraction of a second then turn to green, and sometimes it becomes green directly.
It looks that there have been some changes in the way that the latest build of NIS loads.
When the system boots, W7 x64, the systray icon is no longer present at startup, and it only appears when the nis.exe*32 user, loads, one minute after the system boots.
Sometimes it shows a red X for a fraction of a second then turn to green, and sometimes it becomes green directly.
I have Boot time protection set to off as I do not want to see a ton of Windows performance errors with boot time protection set to on.
Also, I have LU always set to manual so it isn't that either, and you should know that LU never runs while the system is booting as it could cause issues.
I didn't have that glitch with any previous version of NIS 19, 20 or 21, the NIS systray icon was always present in the green state when the desktop appeared.
Then after one minute the NIS user process was loading.
I insist that either something changed in the way NIS 21.1.0.18 loads or it's a glitch.
I also noticed that in taskmgr now the 2 Norton processes are nis.exe *32 and not NIS.exe *32 but that's irrelevant.
Just to clarify, now when the desktop theme appears I have NO NIS icon at all in the taskbar, it is only appearing after approximatively 1 minute whe the nis.exe process loads.
I have Boot time protection set to off as I do not want to see a ton of Windows performance errors with boot time protection set to on.
Also, I have LU always set to manual so it isn't that either, and you should know that LU never runs while the system is booting as it could cause issues.
I didn't have that glitch with any previous version of NIS 19, 20 or 21, the NIS systray icon was always present in the green state when the desktop appeared.
Then after one minute the NIS user process was loading.
I insist that either something changed in the way NIS 21.1.0.18 loads or it's a glitch.
I also noticed that in taskmgr now the 2 Norton processes are nis.exe *32 and not NIS.exe *32 but that's irrelevant.
Let me know what you think.
Thank you in advance.
Best regards,
Not sure what Windows performance errors you see with boot time protection turned on? I do not see any errors and I have Boot Time Protection set to Aggressive. This just loads the Norton processes as early in the Windows boot process as possible to give maximum protection against anything getting in or executed during the boot process.
I have not tested with NIS 21 but with NIS 20 I got performance startup errors, ccsvchst, NDIS, and other NIS drivers which mabye took some secs more to load but enough to generate performance errors, (Event Viewer - diagnostics-performance - Microsoft).
I know it's harmless but it was annoying to see, so, Boot Time protection set to off and no more errors, event Id 101-109.).
However to come back to the issue, before 21.1.0.18 build the systray icon was loading properly even with Boot Protection set to OFF.
FWIW, NIS 21.1.0.18 on Win 7 64 bit, Boot Protection set to Aggressive, the green check marked Norton Icon appears with teh desktop - no delay for it to appear and no Red X.
Thank you for your reply, I've checked a few moments ago with the Normal & Aggressive settings and indeed the NIS icon shows up normally.
My question is why with all the previous NIS versions, 21.0.1.2 included, the icon showed up normally even with Boot Time Protection set to OFF and now it doesn't.
FYI, most of the time the icon is green, only 2 or 3 times it was momentarily red before switching to green.
Hi Apostolos, like yank I have my Boot Time Protection set to Aggressive, and the icon always appears, albeit sometimes after other icons have loaded. My boot time with this setting is normally about 65 seconds, from switch on to the desktop. For that level of protection, I'm happy to wait.... Has Autofix picked up any problems ?
I know all you have stated about Aggressive Boot Protection etc, my question is why the latest version of NIS 21.1.0.18 has this icon glitch, and the previous version 21.0.1.3 didn't have it.
Apparently something changed in the latest NIS Engine.
With Boot Protection set to off my OS takes 53 secs to boot and with Aggressive 60 secs.
In both cases I'm getting Performance errors, (not previously shown with NIS 21.0.1.3), for BASHx64 driver, cc_set Symantec Network driver and Symantec Iron driver but with the Agrressive setting the delays are higher.
I also noticed in Security History that the number of IPS signatures to monitor is no longer present just a description.
That's also new with the 21.1.0.18 version.
Now, NIS icon is loading exactly 1 minute after the desktop theme appears and 99% of the time it is directly green. (OFF setting).
I know all you have stated about Aggressive Boot Protection etc, my question is why the latest version of NIS 21.1.0.18 has this icon glitch, and the previous version 21.0.1.3 didn't have it.
Apparently something changed in the latest NIS Engine.
With Boot Protection set to off my OS takes 53 secs to boot and with Aggressive 60 secs.
In both cases I'm getting Performance errors, (not previously shown with NIS 21.0.1.3), for BASHx64 driver, cc_set Symantec Network driver and Symantec Iron driver but with the Agrressive setting the delays are higher.
I also noticed in Security History that the number of IPS signatures to monitor is no longer present just a description.
That's also new with the 21.1.0.18 version.
Now, NIS icon is loading exactly 1 minute after the desktop theme appears and 99% of the time it is directly green. (OFF setting).
Regards,
There have been other threads reporting things being reported in History that were not there before. The icon loading may have changed as well.
A program develpoer has the control over what the program reports and how things are displayed. They often choose to change things with a new version so they can say it is 'New and Improved'.
You need to note that just because the icon is not there, your system is still protected. The icon display is a separate process. In this case, it seems Norton wanted to focus on loading protection items before the cosmetics of the user interface.
This application took longer than usual to start up, resulting in a performance degradation in the system startup process: File Name : NIS.exe Friendly Name : Norton Internet Security Version : 12.11.0.16 Total Time : 1576ms Degradation Time : 576ms Incident Time (UTC) : 2013-10-17T05:42:34.765200400Z
This application took longer than usual to start up, resulting in a performance degradation in the system startup process: File Name : NIS.exe Friendly Name : Norton Internet Security Version : 12.11.0.16 Total Time : 1775ms Degradation Time : 775ms Incident Time (UTC) : 2013-10-15T14:07:53.718400400Z
T'would be nice to just get a fix for Outlook, not a new systemic problem.
I havee the same issue with 21.1.0.18 and on other hand I can't go to Outlook untill Norton icon is appear.
Тhis is ridiculous! Same bug from 2012 is here
If I want "icon" I must set Boot Time Protection to Normal or Agresive which leads to slow boot. If I want fast boot than I must wait 2 minutes (1:55) for icon because I Outlook wont start because Norton Anti Spam component ..directly linked to "icon apear"
Thank you for the insight, it would be nice if you could, or some other users, set your boot time protection to off momentarily and report what you are seeing.
This could motivate Symantec developpers to look into this problem, or they could in the next build delete the OFF feature in boot and let us have the Normal or Aggressive option or improve the NIS icon loading.
I didn't yet received the latest patch on my other systems but as soon as I get it I'll report back.
I am on Win 7 64 bit, NIS 21.1.0.18 and set my Boot time protection to OFF. I then rebooted and paid specific attention to the Norton Icon appearingin the System Tray. It appeared 25 seconds after the desktop appeared (I used a stop watch). It was green.
So that aspect of my system changed when I changed from Aggressive (Icon appears instantly) to OFF (25 second delay).
I didn;t checkall the other boot rimes etc - as they do not concern me. As long as it boots, I am happy!
First I want to tell you that I received today the patch to upgrade to NIS21.1
I tried to reproduce what you asked , I set the boot time protection to OFF, then I did some testing and this is what I got :
Both restarting the computer that doing a cold start , the NIS icon in the systray appears only 1.5 minutes after I get to the desktop, while both processes "nis.exe" are present in the task manager immediately, but i don't have a red X in the systray.
This means that NIS is not working properly during the startup, I think Symantec should investigate to solve this issue. It is not normal that the NIS icon in the systray appears only after 1.5 minutes.
Apostolos, we both have a problem, even if it occurs in a different manner .
Until this problem is not resolved by Symantec, I would suggest you to set the boot time protection to normal, which are the settings that I have always maintained. If this were not enough, it would be appropriate to set to aggressive.
FYI, setting the boot time protection to OFF, I have found that NIS requires about 50 MB of RAM in addition, this was also the case with all the previous versions of NIS.
Thank you both for your comments, it appears that it is in fact a glitch.
When I said that 2 or 3 times I had a red x, I meant that it was only for a fraction of a second then turn instantly to green.
Most of the time is green.
It is red sometimes probably because because NIS tells to the GPU to show the icon when it hasn't loaded at 100% yet.
As I said, the glitch is not present with Boot Time Protection set to Normal or Aggressive but Symantec should take at consideration that not all of the users want to change this setting whenever a new version is working as expected or not.
Otherwise I agree that the 2 nis.exe *32 processes are present in taskmgr as expected and that there is no Protection problem.
I just updated a second W7 x64 pc to the 21.1.0.18 version and it has exactly the same symptoms, the NIS icon appears about 35-40 secs after the desktop theme.
First I want to tell you that I received today the patch to upgrade to NIS21.1
I tried to reproduce what you asked , I set the boot time protection to OFF, then I did some testing and this is what I got :
Both restarting the computer that doing a cold start , the NIS icon in the systray appears only 1.5 minutes after I get to the desktop, while both processes "nis.exe" are present in the task manager immediately, but i don't have a red X in the systray.
This means that NIS is not working properly during the startup, I think Symantec should investigate to solve this issue. It is not normal that the NIS icon in the systray appears only after 1.5 minutes.
Apostolos, we both have a problem, even if it occurs in a different manner .
Until this problem is not resolved by Symantec, I would suggest you to set the boot time protection to normal, which are the settings that I have always maintained. If this were not enough, it would be appropriate to set to aggressive.
FYI, setting the boot time protection to OFF, I have found that NIS requires about 50 MB of RAM in addition, this was also the case with all the previous versions of NIS.
I hope this might help you.
Sandro
just to add: Windows 7 32 bit
NIS.exe and ccsvchst.exe showing in task manager shows that Norton IS protecting you. It is just the icon not yet displayed, which I do not see as a critical feature to have loaded immediately. It is the protection I want.
NIS.exe and ccsvchst.exe showing in task manager shows that Norton IS protecting you. It is just the icon not yet displayed, which I do not see as a critical feature to have loaded immediately. It is the protection I want.
I agree Peter,
In fact, in my previous post , I pointed out that the nis.exe processes are started correctly, that would mean that we are still protected. BTW, I did not say that it is a critical issue, the problem is that the NIS icon appears in the systray with a long delay,
1.5 mins, LazarusLong reported 2 mins.
This means that the NIS GUI cannot be opened during this time, also, I've never had this delay in any previous version of NIS.
This is the issue I pointed out (although not critical). From my point of view, Symantec should consider this problem so they can