Norton Internet Security / Norton AntiVirus

[huwyngr Norton Fighter]

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

[reese_anschultz]

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.

[huwyngr Norton Fighter]

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

[Jody]

Thanks much

Jody

[pigvomit]

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!

[reese_anschultz]

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.

[pigvomit]

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?

[reese_anschultz]

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. 

[pigvomit]

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.

[pigvomit]

I do not see your public e-mail address.