Looking for answers -- first to understand what ccSvcHst is doing.
I'll just conclude by going through the usual complaint </rant> I've been a Norton customer for a very long time. ccSvcHst is routinely pegging my system at 100 per cent CPU. Must be time to take this junk software off and go to McAfee. Nothing is worth this aggravation. Symantec/Norton doesn't care -- there are no solutions. </rant>
OK, I've got that out of my system.
Anyone know anything about what ccSvcHst is doing?
Looking for answers -- first to understand what ccSvcHst is doing.
I'll just conclude by going through the usual complaint </rant> I've been a Norton customer for a very long time. ccSvcHst is routinely pegging my system at 100 per cent CPU. Must be time to take this junk software off and go to McAfee. Nothing is worth this aggravation. Symantec/Norton doesn't care -- there are no solutions. </rant>
OK, I've got that out of my system.
Anyone know anything about what ccSvcHst is doing?
It wasn't running any sort of idle time scan. It appears that defintions had been updated recently. That's the only indicator I could see at least at the top level.
The ccsvchst.exe file is automatically added to your computer upon installing the Norton software, and it is referred to as the Symantec Service Framework. The ccsvchst.exe file works to display the GUI (Graphical User Interface) of Norton products, which usually include the Norton Security Suites.
You are entitled to a free upgrade (Symantec calls it "update" but that can call it "banana" for all I care; it's an upgrade) to your product. You can get it from NIS2010.
I personally found this new version to have much fewer issues with topping out the CPU. And I like it better for a lot of reasons.
Right, ccSvcHst is part of Norton's installation, that's clear.
But what specifically is it doing with the jillons of CPU cycles it consumes?
There are actually two ccSvcHst's active while Norton is working. One of these is involved in scanning. If the scanner bumps into a large file (think compressed file with a lot of executables within it, or a huge installation package), it will resist interruption until it finishes that job. In terms of engineering, there is a lot of logic for this. Most files are small and scanned in microseconds. You don't want to double or even triple the length of the overall scanning time by testing for "interrupts" in the middle of a single file scan. Unfortunately, this means that once committed to the file, it will stay with that file until finished.
One strategy is to determine the size of the file that is being scanned and if small move into the subroutine currently being used; and if big, allow for user interrupts during the scan. However, such a policy could keep a big package of compressed malware from ever being scanned ... at least, until too late.
It's a toss-up and the Symantec coin came down with the current strategy.
The positive side is that once such files have been dealt with they are usually marked and become a nonissue in the future. I always set my new NIS's for a full system scan, go away for an hour or so, come back and have no CPU problem. It it crops up some time in the future, I can always do the say thing again. Nothing wrong with regular full system scans.
The original poster hasn't stated which Norton product he is using, but since he did mention 16.7.2.11, I would have to assume he is using NAV 2009 and not NIS 2009. I don't know if ccSvcHst would be doing anything different if it is for NAV. I believe also that one possible reason for this high CPU usage could be some form of malware on his system which isn't being picked up by NAV.
I have same problem the only solution I have found is to use silent mode for 6 hours when switching on to silent mode I reboot and that stops 100 cpu usage. I use NIS2010 17.1.0 .19 but has same with NIS2009
Looking for answers -- first to understand what ccSvcHst is doing.
I'll just conclude by going through the usual complaint </rant> I've been a Norton customer for a very long time. ccSvcHst is routinely pegging my system at 100 per cent CPU. Must be time to take this junk software off and go to McAfee. Nothing is worth this aggravation. Symantec/Norton doesn't care -- there are no solutions. </rant>
OK, I've got that out of my system.
Anyone know anything about what ccSvcHst is doing?
RedRock
As per mijcar's recommendation, please upgrade to the 2010 product.
I had the same CPU overload issue with NIS 2009 that was resolved by upgrading to the NIS 2010 product (please refer to my previous posts regarding this issue for details). For me, it was never a Scan issue; the Norton History always pointed to hte Norton Community Watch scan, associated with DLL entries that ended up causing a saturation of one of my CPUs.
The original poster can't go with the free upgrade to NIS 2010 since he appears to have NAV according to his version number stated in one of his posts. He could go with the free version to NAV 2010 if he still has a valid subscription for NAV 2009.
The original poster can't go with the free upgrade to NIS 2010 since he appears to have NAV according to his version number stated in one of his posts. He could go with the free version to NAV 2010 if he still has a valid subscription for NAV 2009.
When it happens, it practically disables the computer, the fan is on constantly, and the computer gets quite hot.
If you google this, it appears to be a common problem.
Surely, Symantec should have been able to fix this as some of these posts from google go back years.
Any suggestions would be appreciated.
The fix pretty much is to move up to the free upgradeto NAV2010 available from Symantec at Norton Updater/Upgrader. The site says "updater", but it really moves you up to the next version NAV2010.