All three of my machines (2 Windows 7 64-bit and 1 Vista 32-bit) now have the new 21.2 version of NIS. When I get a new version I usually open the Norton tasks window, and leave it open for a while just to verify that the various tasks are running more or less as usual.
This morning I found that, on all three machines, I would get the "Norton Internet Security has stopped working" window (see attached screenshot). I ONLY get this when the Norton tasks window is open. If I leave it closed, everything seems fine. It appears that NIS restarts itself soon after Windows shuts it down.
I don't recall ever seeing this before, in any version of NIS.
Task Window left open over 35 minutes - could not duplicate on NIS Win 7 version 21.2.0.38????
Hi yank
Was the 35 minutes mainly Idle time? I can reproduce the issue using a combination of Idle time and Sleep.
To reproduce:
1. Open the Norton Tasks window.
2. Let the PC Idle for 10 minutes.
3. In the Norton Tasks window, click on the 'Last Run' column header to sort the Norton Task list. Perform the sort a couple of times. The Norton Tasks window has become unstable at this point and is prone to hanging for short periods while sorting (note the repeated task names below):
4. Leave the Norton Tasks window open and send the PC to Sleep for half an hour or so.
5. Wake the PC. Upon resume, the following error will be displayed:
The Norton Product Developers will need to investigate and resolve this issue.
Norton Internet Security 21.2.0.38 Windows 7 Home Premium 7601.18247.x86fre.win7sp1_gdr.130828-1532
No thank you - don't have the desire to try to mess up the sorting, nor the time to permit sleep. Repeated sorting is not the usual functions someone would perform, nor putting a system to sleep while the sorting has frozen. I can't see why anyone would do that?
So as, you say,
"The Norton Product Developers will need to investigate and resolve this issue."
No thank you - don't have the desire to try to mess up the sorting, nor the time to permit sleep. Repeated sorting is not the usual functions someone would perform, nor putting a system to sleep while the sorting has frozen. I can't see why anyone would do that?
So as, you say,
"The Norton Product Developers will need to investigate and resolve this issue."
In my case, it wasn't nearly that complicated. I powered up my computer from the hibernate mode it had been in overnight, bought up the Tasks window, clicked once to change the sort order to "last run" (no repeated sort changing needed), and the crash happened in less than 10 minutes. On three different computers.
To the best of my recollection, my Vista machine that displayed this behavior hadn't been in sleep or hibernate mode. I had just re-booted to finish installing the new 21.2 update. The only actions I performed after re-booting were to bring up the Norton tasks window, and change the sort order to Last Run. So maybe the key is changing the sort column? And again, I only changed the sort column once, not multiple times.
Guess it's too late to edit my last post, so I'll just reply to myself again. Anyway, I just finished a short, non-scientific test, and it appears that, at least on my computer, changing the sort column is indeed the only trigger to cause this error. Here's what I did:
1. Cold booted.
2. Opened Norton Tasks window, did nothing else. Everything was normal, no error after at least 30 minutes.
3. Re-booted.
4. Opened Norton Tasks window, clicked once to change sort column to "last run", did nothing else. Received the same error message I showed above within about 5 minutes.
Guess it's too late to edit my last post, so I'll just reply to myself again. Anyway, I just finished a short, non-scientific test, and it appears that, at least on my computer, changing the sort column is indeed the only trigger to cause this error. Here's what I did:
1. Cold booted.
2. Opened Norton Tasks window, did nothing else. Everything was normal, no error after at least 30 minutes.
3. Re-booted.
4. Opened Norton Tasks window, clicked once to change sort column to "last run", did nothing else. Received the same error message I showed above within about 5 minutes.
Thanks - I just performed Step 4 only in your instructions above and I received the same error message too.
The purpose of the repeated sorting in Step 3 in my previous post was to highlight to the developers that there were multiple issues with the Norton tasks window ie. hanging for short periods while sorting and repeating task name values.
