"add/remove programs" won't launch

[Guest]

I've been trying to uninstall/reinstall my virus
protection software (NAV2004) IN WinXP, but each time I
go to START/SETTINGS/CONTROL_PANEL/ADD_OR_REMOVE_PROGRAMS
nothing happens. Watching the TaskManager I've noticed
that a new WINUPDATE.EXE process appears... but then
nothing else happens. Same thing happens when I try to
open the properties window for MyComputer or the
Desktop. Also, each time I restart the PC now I get
something like 20 to 30 instances of the WINUPDATE.EXE
process in the TaskManager.

HELP!!

 

[Guest]

http://www.kellys-korner-xp.com/xp_tweaks.htm
go to this site and look for the fix for add/remove
programs.repair/restore add/remove.

 

[Guest]

The closest fix I found was the "add/remove admin" reg
edit. It didn't fix my problem.

 

[Tom G]

I had this same problem a while back. After some newsgroup searches
suggested that appwiz.cpl file in C:\windows\system32 folder may be damaged
or corrupt, I extracted a fresh copy from my xp disk. The copy I extracted
had a different date than the appwiz.cpl I was about to replace.So instead
of replacing the old one I renamed it Zappwiz.cpl in case I needed to
restore it. Then as I was about to drag the new copy of appwiz into system32
folder I noticed appwiz.cpl was still there!Scrolled down and Zappwiz was
still there too! I imediatly went to control panel and hit add/remove
programs and, viola... worked perfectly and still does. Never did replace
the appwiz.cpl file. Go figure.
Hope maybe this will work for you.

Tom

 

[Guest]

Thanks for the advice Tom, but I wasn't so lucky. My
problem didn't change - it still won't launch via
start/settings/controlpanel, and I still have a bunch
of "winupdate.exe" processes running after startup. But
now I know that I can launch "add/remove programs"
directly by doublecliking
c:/windows/system32/appwiz.cpl! That's something at
least! Thanks!

Dave

 

[Guest]

Problem solved. I had a Protoride.K infection in
Winupdate.exe in my Startup directory. NortonAntivirus
2003 didn't catch it and neither did the scan that is
part of the NAV 2004 installation.