ccSrvHst.exe errors at shutdown

[Guest]

I have Norton Antivirus 2007 installed. I was getting this error before where
ccSrvHst.exe reported that a memory location could not be written to just as
the computer was about to shut down. The computer would shut down after this
message was displayed, whether or not I clicked the OK button. That time it
turned out to be that NAv was trying to check a non-existent floppy drive. I
had already set NAv to not check for a floppy drive, but it reset that
parameter on it's own (or never accepted my change, one or the other).

Since then I installed the .NET updates from Microsoft. Now I am getting the
same error, and a new one. The new error is the same, except that it is a
could not be read error. This is happening everytime I shutdown or restart. I
know I could go to Norton and ask, but I was hoping someone in this forum has
already dealt with this and has a solution. I already checked all of the
settings in NAv and have no clue what is causing this.

I am using XP Professional SP2 with all updates installed. My computer is a
HP Compaq nx9020 notebook (Celeron M processor), 256MB RAM, 40GB storage, DVD
Read/CD-RW

 

[Guest]

I found a warning entry in my event viewer/application log that helped me
find a solution. As follows:

Windows saved user <my computer>\<my user> registry while an application or
service was still using the registry during log off. The memory used by the
user's registry has not been freed. The registry will be unloaded when it is
no longer in use.

This is often caused by services running as a user account, try configuring
the services to run in either the LocalService or NetworkService account.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I followed the above link and found that I could use a program called User
Profile Hive Cleanup to fix the problem. I downloaded it from:

http://www.microsoft.com/downloads/...6D-8912-4E18-B570-42470E2F3582&displaylang=en

It fixed the problem. Not only did the errors stop, but the forced ending of
2 NAv related programs stopped as well, and shutdown is now as fast as it was
before I installed NAv.

Wayne

 

[Guest]

Also, when I checked the log after I restarted again, the following entry
showed up:

The following handles in user profile hive <my computer>\<my user>
(S-1-5-21-57989841-688789844-854245398-1003) have been remapped because they
were preventing the profile from unloading successfully:

svchost.exe (900)
HKCU (0x2d0)


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

From what I know, the above items are not related to NAv, but rather to
Windows Update (from another post I read: svchost.exe -- application error
the instruction...).