Recently replaced XP w/NIS 2010 with full clean installation of Win 7 32 bit. I then re-installed Norton from DVD. Since about Thursday of last week, when I leave PC idling, Norton takes over. When I get back to PC I see the following message: "Norton Internet Security is currently performing background tasks", and basically stops me from doing anything.
I right click on desktop to get to Task Manager and I can see the little time circle but nothing happens. I reboot and then when it happens again I try ctrl-alt-del and I do get the screen that allows me to select Task Manager, but then nothing happens from then on. I can see the hard drive light is solidly on.
I checked my last update and it is version: 17.7.0.12. Yesterday, I followed the suggestions of downloading definitions to desktop as outlined under "My computer runs slowly after I install my Norton 2010 product for the first time" and in Settings, I had to turn ON the Early Load status indicator. I then ran Full Scan as instructed, rebooted and ran Full Scan again as instructed. BTW, I do not have any other security sfotware installed. At this stage, I don't know what else to do. I thank you in advance for any assistance you can provide.
I'm 100% sure that I ran Full Scan last night twice, and because I have 4 drives with approximately 700GB which takes a few hours to run, I did not run it after reading your comment.
I did go into Settings and changed the compressed files to NO as you suggested.
The Idle timeout is set to the default which is 10 minutes and while on the subject, I've not tailored NIS and I'm using default for everything.
I entered run and when the command drop menu came up, I then entered chkdsk c: /r but nothing happened. I did it twice including once under the Administrator's login. FYI, I do have and run Diskeeper 2010, which I assume would let me know if I have problems.
Again, out of the blue, my problem started days (maybe even a couple of weeks) after I had installed Win 7 Ultimate and NIS 2010.
Lets see if the Compressed Files Scan solves the problem.
Again thank you for taking time to assit me with this problem. I'll keep you posted on progress or lack off.
Recently replaced XP w/NIS 2010 with full clean installation of Win 7 32 bit. I then re-installed Norton from DVD. Since about Thursday of last week, when I leave PC idling, Norton takes over. When I get back to PC I see the following message: "Norton Internet Security is currently performing background tasks", and basically stops me from doing anything.
I right click on desktop to get to Task Manager and I can see the little time circle but nothing happens. I reboot and then when it happens again I try ctrl-alt-del and I do get the screen that allows me to select Task Manager, but then nothing happens from then on. I can see the hard drive light is solidly on.
I checked my last update and it is version: 17.7.0.12. Yesterday, I followed the suggestions of downloading definitions to desktop as outlined under "My computer runs slowly after I install my Norton 2010 product for the first time" and in Settings, I had to turn ON the Early Load status indicator. I then ran Full Scan as instructed, rebooted and ran Full Scan again as instructed. BTW, I do not have any other security sfotware installed. At this stage, I don't know what else to do. I thank you in advance for any assistance you can provide.
You might want to subscribe to bcotter's thread Idle Time Scan is Locking Up My PC. No solution has been posted as of 16-June-2010 but some of the replies there might be helpful.
Thanks for the update. Regarding the chkdsk command. You can't run chkdsk directly from the run command. You need to type in the word cmd and run that. This will bring up a Command Prompt window. From this window you would perform the chkdsk command.
Since you have 4 drives I would recommend running chkdsk on all of them because the NIS scan could be getting stuck on any one of them. You can also run a Custom scan with NIS by selecting Scan Now > Custom Scan then choose the drive.
To run chkdsk for each of the drives you would enter the following from the Command Prompt window.
chkdsk x: /r
where x in the above is the drive letter to run the chkdsk on. I would recommend doing drive C last. So you would run this four times, each time replacing the X with the next drive letter to scan. You should let each one complete before doing the next one.
When you get to the C drive Windows will tell you that it needs to be scheduled for the next reboot. Answer Yes to this and then reboot and chkdsk will run.
Running this will give you a clean bill of health on your drives or it will find a problem and attempt to fix it. Either way it is good to run this.
You might want to subscribe to bcotter's thread Idle Time Scan is Locking Up My PC. No solution has been posted as of 16-June-2010 but some of the replies there might be helpful.
Hi lmacri,
Totally agreed. It is good to be aware of similar threads. This type of problem can be caused by so many things, up to and including even a bug. Did I say that magic word?
Seriously though, many things can cause this including but not limited to hard drive problems (bad sectors, etc), compressed files, other scans running at the same time from other software, malware.... The list goes on and on.
Thank you for all the responses. I contacted Norton support yesterday, and their analysit established a remote session controlling my PC and he did a number of things (i.e. deleted %temp% and temp folders/files, changed Silent Mode to 1 day, turned off the idle time optimizer (changed from 10 minutes to 30 minutes the idle time out) and a couple of other things I don't remember. It seems to be working OK, but I suspect that I may still have a problem in that if Ileave the PC idleing, and a scheduled Full Scan starts, the scan goes to sleep the same as the PC.....Need more observation to confirm. I also posted this info on the other thread regarding PC locking up during idle as suggested by some of you and I'll follow up on that thread from now on. Again thank you all.
I'm noticing a bit of glitchiness in several threads where the new version has updated an older version of Norton. There may have been an installation by disc, or pre-installed, where the version number is not known. I'm suspecting that an extra reboot at the time of the update might have solved any issues. There doesn't seem to be any problems when the versions were updated continually.
If further problems occur, I would recommend uninstalling and reinstalling the version from the website. This will give you a cleaner update to the 17.7.0.12.
