.NET 1.1 Security Update Won't Install

[David Owens]

I can't get the .NET 1.1 SP1 security update to install.
It fails every time. I tried just uninstalling .NET 1.1
because I don't have any software that needs it, but for
some reason Windows Update still keeps nagging me about
installing the security update, even with .NET 1.1 not
installed.

Is there a way to completely clean out whatever leftover
parts of .NET 1.1 are still there? I found a MS Knowledge
Base article about manually uninstalling .NET but it wanted
me to also uninstall 2.0. Windows XP wouldn't let me
uninstall 2.0 because it said there was software that depended
on it.

 

[Newbie Coder]

David,

It seems that hundreds of people are reporting the same thing in the 'Windows
Update' newsgroup (microsoft.public.windowsupdate) and almost every second post
is the same thing. Maybe you should look/ask in there

 

[Guest]

The error you are probably getting is, "Registered JIT Debugger is not
available", and you are not the only one for this Update KB928366.
The complaints are not in the "thousands". MS is working on this and
a new Update or Hotfix is forthcoming. Temporarily stop your Updates
so the Update balloon stops bothering you, or Hide the Update icon on
your Taskbar. Help is on the way, but when..................................?
Changing to v2.0 will not solve this nor trying to delete NET Framework 1.1.

 

[Gerry]

David

http://groups.google.com/group/micr...9dd6e?lnk=st&q=&rnum=3&hl=en#e59017ce9f59dd6e

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Guest]

I am confused by all this. I am going to wait for MS to resolve this mess!

 

[Stan]

I am confused by all this. I am going to wait for MS to resolve this mess!

By that time, and if they even do get this one resolved, Black Tuesday
will roll around again in just 29 days and you will be going through
all this again with some other ill-conceived update abortion.

 

[Edward W. Thompson]

I am confused by all this. I am going to wait for MS to resolve this mess!

snip

You can solve your problem by completely removing all versions of 'net' (Ver
1,2 and 3) then reinstall. Likely you don't need ver.3 yet. The procedure
to do this is well documented by MS in the KB.