.net 1.1 SP1?

On just one of my computers, Windows Updates is showing .net 1.1 service
pack 1 as the only outstanding update (the computer has other .net bits,
up to 4.x IIRR), and is consistently failing to install it: done via
updates, it sits at installing for a very long time, then tells me it
wasn't installed. Code 0x66A (yes, a very short/low number).

That took me, eventually, to the .net removal tool to remove certain
bits of .net and then reinstall them. Incidentally, that produced a
different file for .net1.1SP1 to that produced by the upgrade process:
the two files are NDP1.1sp1-KB979906-X86.exe and
NDP1.1sp1-KB867460-X86.exe (I _think_ the higher KB numbered one was
from the update process and the lower from the removal tool page).

Oh, I've just tried again, and it's 0x643 now!

Hm. That took me to a page that suggested a fixit to fix MSI (I thought
that was a maker of motherboards!) which seemed to run OK then try again
- this time updates said I needed .net 1.1SP1 and .net3.5SP1, both of
which failed ... anyway, the 0x643 page then suggests I try .net repair
(as opposed to removal) tool: trying that now.

Computers, don't you just love 'em ...
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"Knowledge isnt elitist - that's rubbish! Why are we embarrassed by the idea
that people know things? It's not a conspiracy against the ignorant. Knowing
things is good!" - Jeremy Paxman, RT 14-20 August 2010

On Fri, 21 Feb 2014 07:34:29 +0000, J. P. Gilliver (John) wrote:
On just one of my computers, Windows Updates is showing .net 1.1 service
pack 1 as the only outstanding update (the computer has other .net bits,
up to 4.x IIRR), and is consistently failing to install it: done via
updates, it sits at installing for a very long time, then tells me it
wasn't installed. Code 0x66A (yes, a very short/low number).

That took me, eventually, to the .net removal tool to remove certain
bits of .net and then reinstall them. Incidentally, that produced a
different file for .net1.1SP1 to that produced by the upgrade process:
the two files are NDP1.1sp1-KB979906-X86.exe and
NDP1.1sp1-KB867460-X86.exe (I _think_ the higher KB numbered one was
from the update process and the lower from the removal tool page).

Oh, I've just tried again, and it's 0x643 now!

Hm. That took me to a page that suggested a fixit to fix MSI (I thought
that was a maker of motherboards!) which seemed to run OK then try again
- this time updates said I needed .net 1.1SP1 and .net3.5SP1, both of
which failed ... anyway, the 0x643 page then suggests I try .net repair
(as opposed to removal) tool: trying that now.

Computers, don't you just love 'em ...

This might help.

http://support.microsoft.com/kb/976982

Don't blame your computer for doing it's job.
Blame the .NET.
The only unmanaged installers/updaters of managed code.
aka. .NET hell.
Welcome to the club!

In message , JJ
writes:
On Fri, 21 Feb 2014 07:34:29 +0000, J. P. Gilliver (John) wrote:
On just one of my computers, Windows Updates is showing .net 1.1 service
pack 1 as the only outstanding update (the computer has other .net bits,
up to 4.x IIRR), and is consistently failing to install it: done via
updates, it sits at installing for a very long time, then tells me it
wasn't installed. Code 0x66A (yes, a very short/low number).

That took me, eventually, to the .net removal tool to remove certain
bits of .net and then reinstall them. Incidentally, that produced a
different file for .net1.1SP1 to that produced by the upgrade process:
the two files are NDP1.1sp1-KB979906-X86.exe and
NDP1.1sp1-KB867460-X86.exe (I _think_ the higher KB numbered one was
from the update process and the lower from the removal tool page).

Oh, I've just tried again, and it's 0x643 now!

Hm. That took me to a page that suggested a fixit to fix MSI (I thought
that was a maker of motherboards!) which seemed to run OK then try again
- this time updates said I needed .net 1.1SP1 and .net3.5SP1, both of
which failed ... anyway, the 0x643 page then suggests I try .net repair
(as opposed to removal) tool: trying that now.

Computers, don't you just love 'em ...

This might help.

http://support.microsoft.com/kb/976982

Yup - bin there; that's the one that started having me fix MSI (whatever
that is, presumably _not_ the motherboard manufacturer, then the .NET
repair tool, then the .net cleanup tool to remove it altogether, ...

Don't blame your computer for doing it's job.
Blame the .NET.

Oh, I do!

The only unmanaged installers/updaters of managed code.
aka. .NET hell.
Welcome to the club!

(-:
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

If you believe in telekinesis, raise my right hand