I don't know when this broke exactly, but if I put my Windows XP SP3 computer into standby (close the lid) and then resume it, from that point on NIS 20.2.1.22 things my compter is idle even when it's not.
As such it is kicking off "idle" background processing when I'm actively using my PC. In order to get idle detection working again, I need to reboot my PC. This is a relatively new problem as I've only seen it under NIS 20.2.0.19 and NIS 20.2.1.22.
It looks like it started some time within the last month as you can see that Norton believed my computer was idle for 2 weeks straight (except when the computer was off).
If this keeps up, I'm going to have to remove Norton since when it's doing it's idle processing, my computer is unusable.
I'll check back later as your images are not yet visable until a moderator OK's them.
Have you checked your power settings in Windows? If your system just goes to 'sleep' or hybernates when you close the laptop, Norton will see this as being idle.
It doesn't matter if Norton thinks my system is idle when in standby,it shouldn't think it's idle when I'm actively using my machine.
I decided to run the Norton Removal Tool and reinstall. The Norton removal tool seems to have hung though as it's been sitting at the "Processing MSI's by Product Code" stage for the last 15 minutes with it's task using 97% CPU. How long should it take?
It doesn't matter if Norton thinks my system is idle when in standby,it shouldn't think it's idle when I'm actively using my machine.
I decided to run the Norton Removal Tool and reinstall. The Norton removal tool seems to have hung though as it's been sitting at the "Processing MSI's by Product Code" stage for the last 15 minutes with it's task using 97% CPU. How long should it take?
Having recently used that, yes, it does tend to take that long in that stage.
Okay, I removed and reinstalled and it installed 20.2.0.19. I ran live update, t before I restarted, I closed the lid and waited about 15 minutes. When opened it, Norton identified the system as having slept and now being active, so that worked.
I then tried seeing what would happen if I closed the lid, while Norton said the system was idle. I changed the idle time to 1 minute so I wouldn't have to wait. I waited a few minutes and opened the lid and Norton showed that the system was idle that entire time (instead of being in "sleep" like it did before), but detected the system went active. I'm not sure why Norton showed "idle" as opposed to "sleep" this time, but it may have had with do with leaving the Norton window open, the shorter sleep time or that I had just resumed from standby a few minutes prior to going into standby again.
I rebooted my PC to install the live updates. I was still on 20.2.0.19 so I ran live update again to see if it would update me back to 20.2.1.22, but it didn't.
Please run LiveUpdate (rebooting when requested) unitl LiveUpdate responds with the specific words :no updates found" - you are not completely up to date until you see "no updates found".
Please run LiveUpdate (rebooting when requested) unitl LiveUpdate responds with the specific words :no updates found" - you are not completely up to date until you see "no updates found".
I've already done that. I've even rebooted a few times for good measure.
Also if you are positng in this thread, please make sure it is about the problem I'm having with Norton not detecting when my system is no longer idle.
Also if you are positng in this thread, please make sure it is about the problem I'm having with Norton not detecting when my system is no longer idle.
You commented you were trying to get back to 20.2.1.22 and Yank was just trying to help you do that.
How did you get 20.2.1.22 originally? Was it just through LiveUpdate, or did you email Tony for the download?
The probable reason for your original issue is a corrupted download or update to your Norton product. Your reinstalling seems to have solved this.
You commented you were trying to get back to 20.2.1.22 and Yank was just trying to help you do that.
How did you get 20.2.1.22 originally? Was it just through LiveUpdate, or did you email Tony for the download?
The probable reason for your original issue is a corrupted download or update to your Norton product. Your reinstalling seems to have solved this.
Norton originally updated to 20.2.1.22 on it's own. I didn't do anything special to get it.
Also I'm not 100% sure reinstalling fixed this. I'll need to watch it. I did notice after reinstalling the idle Quick Scan didn't run on it's own, so I uninstalled, ran NRT and reinstalled again, QuickScan still isn't running, though the other processes are.
On a side note, NRT does something weird since every time I run it, my HP printer software wants to reinstall.
Norton originally updated to 20.2.1.22 on it's own. I didn't do anything special to get it.
Also I'm not 100% sure reinstalling fixed this. I'll need to watch it. I did notice after reinstalling the idle Quick Scan didn't run on it's own, so I uninstalled, ran NRT and reinstalled again, QuickScan still isn't running, though the other processes are.
On a side note, NRT does something weird since every time I run it, my HP printer software wants to reinstall.
I have seen one or two other users that have mentioned the HP printer getting removed. I'll see if I can pass this on.
I have seen one or two other users that have mentioned the HP printer getting removed. I'll see if I can pass this on
Technically the printer isn't being removed, but when doing things after NRT, I get a Windows Installer popup telling me certain HP programs are being installed (for example TrayIcon, Web Smart Print, etc). I had to go find the original CD that came with my printer to complete the install since if I canceled the install, it would open again the next time I restarted my PC or opened any folder.
It looks like NRT is somehow flagging the HP programs as needing to be installed even though they already are. It's not a big deal if you have the CD. If you don't it becomes problematic.
Back on the original topic, I have no idea whether re-installing worked or not, because now Norton isn't detecting when my Computer sleeps.
I closed the lid last night and when I opened it this morning, it immediately kicked off the background processing (Ran Live Update and did a Quick Scan), but that's because it thought that the computer was idle when I first resumed it from sleep. Once I moved the mouse around it went active. For the entire time it was "sleeping", Norton shows it as being active with "No Activity".
So it went from detecting sleep, but getting stuck in idle after resuming from sleep, to not detecting sleep at all. I guess this is better since now it only ignores the setting to wait 10 minutes after resuming from sleep to do processing. Before it was just kicking off idle background processing whenever it felt with. I can deal with a few minutes of annoyance after resuming my PC from sleep.
I still need to see what happens if Norton properly detects my PC has went to sleep and see what it does when I resume.
I updated back to 20.2.1.22 today and now Norton is reporting the "idle" time that occurs when the computer is sleeping as "Computer Off". It actually changed from "Idle" to "Computer Off" in the performance window after I rebooted to install 20..2.1.22.
I have yet to see if the problem will return with 20.2.1.22 installed or not.
It detected my computer as "sleep" when I slept it last night and it didn't think it was idle when it was resumed so it looks to be working. At least it did once.
I ended up fixing the issue by completing uninstalling without saving current settings and reinstalling.
It's not 100% fixed as frequently Norton detects sleep as being either active or idle, instead of "Sleeping", but it's no longer detecting active as idle as far as I can tell. It no longer runs its background tasks (other than automatic live update and quick update) when I'm using my system.
