Similar issue here, with a Compaq CQ5500Y that came pre-loaded with an HP WIM of W7 Home Premium (currently running SP1
{i.e., Build 7601} & fully patched as of 22Jul13) that came with Norton Internet Security 2010. I originally noticed
problems in April with N360 presenting faulty behavior in filling logins - for which I have supplied multiple Issue Reports
for multiple sites; only one of which has rcv'd an "affirmative reply" (i.e., notification that the issue had been resolved)
- especially with some secure logins, although not most...and soon developed into similar situation as Flynne reports above,
IE9 AppCrash with the faulting modules invariably being associated with ccsvchst; this escalated into some strange
recursive-loop behavior with certain site logins.
I eventually restored the box to factory settings, ran the Norton Removal Tool & manually removed (after 1st backing it up, of course) what it does not in AppData, ProgramData, HKCU, & HKLM, and loaded all the Windows Features & 1Soft/3rd Party software I employ. After letting WUP do it's thing (both previous to, after the reset, and after installing add'l programs), verified that none of the afore-mentioned behavior was present with any of the users: creator/admin, built-in admin, IIS 7.5, or the standard user account I normally use on a daily basis (interestingly enough, that's the account that had the most trouble; many of this issues with it were not present when performing the same action from the elevated account), and following the last reboot/system snapshot, I performed a "desktop web install" using N360Downloader 3.1.0.14. yesterday evening. Things seemed pretty stable until I began to add my exclusions for Scans, Signatures, & Auto-Protect/Sonar/DwnLd Intelligence Detection; the latter didn't "take" the first time through (unless I'm mistaken, there's no importing function from a saved database or .reg file that will accomplish this, and each exclusion has to be entered one @ a time in the same fashion that address book exclusions must be laboriously entered manually for any unsupported mail client - such as, surprisingly enough, Windows Live Mail, Thunderbird, Claws, etc.): closing the system center & reopening to the Exclusions Configuration dialog showed a blank screen. Resigning myself to adding my exclusions again, I was dismayed to find Norton freeze up, invoking the WER dialog Flynne mentioned, "Symantec Service Framework" having crashed (first time I've ever seen that particular bug-a-boo). Restarting the 'puter allowed the exclusions to be added again, but once again it didn't "take"; the solution for that proved to be applying the additions one @ a time, after they'd been individually entered, rather than en masse as I'd tried the first two times.
Unhappily, the strange mis-behaviour returned for the standard user account, so verified that it was exclusive to IE (Chrome
is the only other of my browsers that includes N360 integration, as I only use Firefox with TORS or TAILS, and Safari
doesn't seem to be supported unless I am misinformed), and that it was due to N360 (IEx64, IE No AddOns, and IE9x86 with
Norton integration disabled all swim merrily along). Will have to see what Support has to say about this, but given my
previous experience with the help desk personnel, I won't be holding my breath...not very interested in upgrading to IE10,
as I don't yet have a handle on the change in the way that cookies index information is stored, but I may try that in a VM
with one of my spare N360 keys and see what the difference may be, if any...