System Idle Freezing

I downloaded the 2009 update and have regretted it ever since. As SOON as my computer is turned on, up pops a screen stating that NIS 2009 is "inititializing", then gives me a message that there is another installer running and before I can even take a breath, NIS begins to install and immediately FREEZES the whole system. Yes.. it freezes.. not just slows. I know the difference. If I can ever be fast enough to stop it from initialzing/installing, so that I can get into my computer, I am going to uninstall 2009 and not install it again until I know Norton has worked out the bugs. Or I will go to another security program.  I have NEVER had so much trouble with a Norton Product. EVER.

It makes me very leary of purchasing the whole program instead of just an update. All I want to do at this point is be able to even get into my system so I can remove NIS 20009! My cursor won't even move! Trying Ctrl/Alt/delete does not end it either.

I've gotten stuck and can't get out. I have to shut down the whole system. Does anyone know how to start my computer without NIS starting? It won't even let me get into my "start up" configuration to turn it off. HELP!

Start in Safe Mode with step-by-step confirmation.

Are you using any other security programs such as Spy Sweeper?

I started a new thread on my freezing problem, but it may be the same as this one.  Though what I am seeing is more a freeze of the c drive access - I can move the cursor around, until I tell the computer to do something with the c drive.  Alt-Ctrl-Del will not bring up the system monitoring, and if it is on, it is frozen also.  Upon turning off and turning on the computer, I get a message that the size of a tmp file in SrTEmp is not valid.

 

I too am very frustrated with Norton/Symantec.  You can read my tale of woe in my thread.  Before 2008, Nortons was a great product.  2008 really was frustrating, but if got used to every few minutes the computer going off and doing Nortons stuff on its own, it wasn't as bad as freezing up the computer.  The amazing thing is that Symantec has any customers left.  Definitely when I buy a new computer, I won't use Norton/Symantec products unless something really turns around.

 

Steve Prevette

Pasco WA

What other security products are you running? Do not blame Norton till we know the full extent of what your running on your pc.

No other security products.  Windows firewall, standard Windows XP with automatic updates.

 

I do blame Nortons as

 

1. this only started after installation of Nortons 2009

2.  The files that keep getting tripped on Scandisk upon restart are Nortons files

3.  The Nortons tech attempted to delete the temporary file, which apparently was a required file for Nortons as Nortons stopped working.

4.  Nortons 2009 has had me remove and reinstall Nortons 2009 at least six times in October.

5.  Google Nortons sometime and discover what the world thinks of Nortons software.

 

And the complete lack of responsiveness from Nortons I find suspicious as a Quality Professional.

 

 

Hello prevette,

 

Sorry about your frustrations. Have you tried running a disk defragmenter on your computer? It might be possible that the product wrote a temp file to a bad sector on your hard drive, which is causing the program to "freak out" if you will. Have you tried running a chkdsk c: /f from the command prompt, and then selecting to have it run on reboot?

Articles you find on Norton are from older Norton products. Not Norton 2009 products. Do not bash when your asking for help. Is your Scandisk a removable drive?

Message Edited by Dieselman743 on 11-02-2008 08:50 PM


Tim_Lopez wrote:

Hello prevette,

 

Sorry about your frustrations. Have you tried running a disk defragmenter on your computer? It might be possible that the product wrote a temp file to a bad sector on your hard drive, which is causing the program to "freak out" if you will. Have you tried running a chkdsk c: /f from the command prompt, and then selecting to have it run on reboot?


Yes, I have run a chkdsk c: /f, and have also defraged.  There is a bad sector that does show up on the scan disks, but since the computer knows about it, it should not be a problem.  If there was a drive problem, I would think that other files would show up on the disk scan other than these temp files.  I have seen (less frequently than the tmp error) an error message for the first byte of a Norton's log being improper.

 

- Steve


Dieselman743 wrote:
Articles you find on Norton are from older Norton products. Not Norton 2009 products. Do not bash when your asking for help. Is your Scandisk a removable drive?
Message Edited by Dieselman743 on 11-02-2008 08:50 PM

 

The c drive, which is where the error is showing up at, is the internal drive.  I do also have a removable drive, and that has been checked and defragged also.

 

Please just understand the level of frustration that this is causing.  I have attempted on multiple occasions to get any sort of response through Norton/Symantec official channels, and there has not even been an acknowledgement of this problem, except for the one phone call and one generic response email.  Trying to conduct troubleshooting and error testing of a "beta" product through a public discussion board doesn't seem like a very good business model.  If I could get confirmation that I could reset to 2008, I would do so and be willing to test if the problem goes away.

 

 I certainly am not "bashing" you.  But just leave it as I am a very disgruntled Norton's customer, and at this rate, not likely to be one much longer.

Did you do an over the top install of NIS 2009 or did you uninstall NIS 2008 first? Its best to uninstall NIS 2008 first. Try uninstall NIS 2009 and rebooting. Then running the Norton Removal Tool and rebooting. Install NIS 2009.

 

 http://service1.symantec.com/Support/tsgeninfo.nsf/docid/2005033108162039?OpenDocument&seg=hm&lg=en&ct=us


Dieselman743 wrote:

Did you do an over the top install of NIS 2009 or did you uninstall NIS 2008 first? Its best to uninstall NIS 2008 first. Try uninstall NIS 2009 and rebooting. Then running the Norton Removal Tool and rebooting. Install NIS 2009.

 

 http://service1.symantec.com/Support/tsgeninfo.nsf/docid/2005033108162039?OpenDocument&seg=hm&lg=en&ct=us


 

I used whatever methodology that the notice for 2009 was available was.  I will try what you have suggested tonight.

 

Thank you for your help.

 

- Steve

Hello Steve,

 

Again, I'm sorry for the frustrations. I'll see to it that your issues are resolved. Please try Dieselman743's suggestion and let us know if it helps.

I performed two sequential uninstalls, and one install.  I also ran a chkdsk /f.  I'll report back on the next freeze, or at the end of the week if there are no freezes.

 

Thanks,

Steve

Did you run the Norton Removal Tool?

I have a similar problem on my laptop in that after installing NIS09 my CPU usage was really really high, usually 100% (can be seen here http://community.norton.com/norton/board/message?board.id=nis_feedback&thread.id=17102) this did not happen before install (I had 360(2) and just installed over top without running the NRT) but after stopping the indexing service mentioned here CPU usage is normal again… so does this mean that there is a conflict there and if so how do I keep the services running with NIS and still have my CPU usage normal (laymen alert here, PC literate enough to cause great harm to any pc within 100m)… also I have NIS installed on our pc and this does not happen… (seperate issue for tha machine in my thread which may have a solution once I try out a suggestion)…


Dieselman743 wrote:
Did you run the Norton Removal Tool?

 

Yes, twice.

I have discovered as part of my Charter Communications internet access, I can get their virus protection for free.  I have changed over to it, it is working wonderfully, and I am never going to renew or buy a Nortons product again.

 

I suppose there won't be much chance of it, but I am going to ask Symantec to return the remaining portion of my subscription costs for this year.

Hello Prevette,

 

Have you tried using the recently released patch (16.1.0.33)? We fixed some issues that seem to be identical to the issues you had. If you run LiveUpdate, you should be able to download the new patch.

 

Let me know if this helps!