NIS 2008 May Break Device Manager Under Windows XP Pro SP3

Norton Security | Norton Internet Security
21

I have read the article concerning the problem I report in Re that regards Windows XP after installation of SP3, but mine concerns the

Norton 360 2.0 and Network less after installing SP1 on my PC with Vista Home Premium.

 

Are you working on this issue of learned other in same troubles?

 

Tks in advance for your kind help.

22

We’ve developed a LiveUpdate solution that is available now, which will prevent this issue with Windows XP SP3 from occurring. Users should ensure they run LiveUpdate and reboot their computer; then they can install SP3. We suggest users ensure they have this latest update before applying any operating system upgrade. Please note that this LiveUpdate solution only addresses issues related to Symantec products. For instructions on how to run LiveUpdate manually, please go to

 

http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/2006060207314913.

 

For users who have already downloaded SP3 and have run into problems, manual instructions for removing the additional registry keys created by Microsoft’s fixccs.exe file can be found below. We will post an automated tool next week.

 

For N360 v2:

http://solutions.symantec.com/sdccommon/asp/symcu_contentredirect.asp?docid=20080516113101EN

 

For N360 v1:

http://service1.symantec.com/support/norton360.nsf/docid/2008051623480975

 

For 2008 products:

http://solutions.symantec.com/sdccommon/asp/symcu_contentredirect.asp?docid=20080516112507EN

 

For all other products:

http://service1.symantec.com/Support/sharedtech.nsf/docid/2008051623512613

 

23

Reese -- In your message you say: 

 

<<

We’ve developed a LiveUpdate solution that is available now, which will prevent this issue with Windows XP SP3 from occurring. Users should ensure they run LiveUpdate and reboot their computer; then they can install SP3.

 >>

 

but in all the documents linked to it says:

 

<< Numerous registry keys are added when you upgrade to Windows XP Service Pack 3 or Windows Vista Service Pack 1 with a Norton product installed. >>

Note also that http://www.symantec.com/norton/support/kb/web_view.jsp?wv_type=public_web&docurl=20080528154203EN is headed XP SP3 and VISTA SP1 but at the bottom where it says Applies to: it only says XP .....

 

Could you please confirm that the problem occurs with XP SP3 and with VISTA SP1 and that the same solutions all apply.

Message Edited by huwyngr on 05-30-2008 09:28 PM
24

I have seen one report in this thread of a user encountering a similar issue with Vista SP1. It also appears that the FixCCS.exe application is run during that upgrade so the opportunity for this issue to occur exists there as well. Given how long Vista SP1 has been available relative to the XP SP3 upgrade and the rarity of this issue on Vista, it appears that the FixCCS.exe program doesn’t need to “fix” stuff as often on Vista, but it may on occasion.

25

Thanks for clarifying -- I'll pass that on.

 

I've posted a couple of messages elsewhere pointing to your message with the fix information.

26

Hi Reese,

 

I have had issues the last weeks, after first upgrading XP SP2 to Vista early last year and an installation of Vista SP1 6 weeks ago.

After this standalone SP1 installation on top of some Norton softwares I got a feeling, that my system did not

perform well.

A recovery to a date before the SP1 -installation and uninstalling all Norton softwares, I installed SP1

again and after that reinstalled all Norton softwares.

I found the system stabillizing much faster on a “non Norton software presence”, some hours, compaired to 2 to 3 days on the first SP1 installation.

Instead I got an error 3035,5.

By searching Symantec Support on this error, I got 3 possible causes. I used one, disabling “Windows Vista User Account Control”, restarted

and got a number of corrections from one “malware-detecting application” telling registry keys have been changed.

My system is now working as I have expected.

 

Kurt

27

Thanks Kurt for your experience. Although I can’t explain everything that you saw, I’m glad that you got it working.

28

Thank you and the Symantec team for your excellent work on this problem and for the soon-to-be released "automated deletion tool"!

 

However, this may not fully solve the problem in all cases. I have found that after deleting all the spurious $%& keys, Dev Manager still shows a problem with four Symantec Network Security Miniports ( "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)" ).

 

In TechNet, others have reported having this same residual problem with these miniports but no solution has yet been posted there.

 

I would much appreciate your help with this remaining problem .......

 

DougN

 

 

29

Hi! Has any one seen Norton's Automated Tool fix yet?

for the SP3 mess.

I have been waiting on it and afraid I may have missed

seeing the post.

Jo

1 Like
30

Jody, the tool isn’t ready yet but is planned to be released some time this week. A message will be posted to this thread when the tool becomes available describing how to get the tool.

Message Edited by reese_anschultz on 06-03-2008 09:59 AM

31

Good news -- I may have a candidate for it.

 

Is it intended to fix all general consequences of installing SP3 on a computer (HP AMD) where NIS2008 was already installed?

 

Do you know whether this new tool would be a satisfactory alternative to uninstall NIS2008, run NRT and then apply the tool on the HP website intended to fix their computer [with SP3 applied already] prior to installing SP3 but prior to installing Norton's? Or whether it is still needed to clean out the registry corruption which I presume the MS utility is intended to prevent?

 

Microsoft Windows XP SP3 Upgrade Utility for systems with AMD processors.   HP Pavilion a706n Desktop PC

which is one I'm dealing with at the moment.

 

My inclination is to have her uninstall NIS, clean up, apply fix and reinstall since she is having multiple problems including LiveUpdate "not working".

 

TIA -- she's hanging on with bated breath <g>

 

Edited by HWG to correct statement about SP3 being already installed -- my oops!

Message Edited by huwyngr on 06-03-2008 05:19 PM
32

The HP AMD issue is unrelated to the Norton issue. I don't believe that the referenced tool will clean up the $%&... keys. The MS tool is to fix an incorrectly installed driver which causes constant rebooting.

 

Uninstalling NIS and running SymNRT may not clean up the $%&... keys. The user should still clean up these keys after SymNRT has been run just to be safe.

 

It seems to me that running the MS Upgrade Utility for systems with AMD processors probably should be the first step toward recovering one of these systems, after that, clean up NIS.

33

OK Thanks – I’ll digest this and come back with some more questions, I expect <g>

34

Thanks much

Jody

1 Like
35

I also have found that after deleting all the spurious $%& keys, Dev Manager still shows a problem with four Symantec Network Security Miniports ( "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)" ).

 

No solutions posted anywhere!

36

We have not reproduced a problem with "Symantec Network Security Miniports" inhouse so this is difficult to diagnose. If you or DougN could export the entire CurrentControlSet area of your registry and e-mail it to me, we might be better able to understand what the problem is.

 

Given the symptoms, right now the only solution that I can offer is to uninstall your Norton product and then re-install it.

 

37

I did uninstall NIS 2008 using your unistall tool. Then I deleted the garbage manually which allowed my device manager to show my devices which lead to me seeing   "Symantec Network Security Miniports" not being functional.

 

I do not see a way to attach files so how do I senf your my registry section?

38

Click on my name in and you should see my profile. I've made my e-mail address public.

 

Did you first uninstall Norton Internet Security using the Add/Remove programs or did you go straight to SymNRT?

 

Regardless of how you removed NIS, I suspect that you can now fix the problem by simply re-installing NIS. 

39

Did you first uninstall Norton Internet Security using the Add/Remove programs or did you go straight to SymNRT? I went straight to SymNRT.

 

Regardless of how you removed NIS, I suspect that you can now fix the problem by simply re-installing NIS. 

 

I saw the problem both after I  removed NIS 2008 & deleted the bogus registry entries. I could then see the device manager populated prior to rebooting. After rebooting the problem remained and after NIS 2008 installation with rebooting, the problem entries remain in the device manager window.

 

The entries are:

 

Intel(R) PRO/1000 PL Network Connection - Symantec Network Security Miniport [with a yellow ! symbol in front of it]

WAN Miniport (IP) - Symantec Network Security Miniport [with a yellow ! symbol in front of it]

 

The error in the properties device status window is:

 

 Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

Click Troubleshoot to start the troubleshooter for this device.

 

Troubleshoot does not help.

40

I do not see your public e-mail address.