Windows Update doesn't see some updates post-SP3

[Guest Craig]

Greetings,

 

Prior to downloading and installing Win XP SP3 on two WinXP Home machines,

a Custom Windows Update let me know that I could choose to install .NET

Framework 1.1, 3 (and maybe 3.5), as well as letting me know that my current

..NET Framework 2 had a Service Pack available--the one that was issued

several months ago.

 

After installing SP3, when I do a Custom (or for that matter, an Express)

Windows Update, I'm still told that .NET Framework 1.1 is available to

install, but I'm no longer told that the .NET Framework v2 Service Pack is

available and I'm not told that I could download and install .NET Framework

3 or 3.5. This is true for two of two computers I've updated.

 

At first, I wondered if these no-longer-offered options were part of WinXP

SP3 but I do not see them listed under Add/Remove Programs and a couple of

MS MVP fellas insisted that no .NET Framework installation or update was

included with SP3 and I tend to believe them.

 

Has anyone else seen the disappearance of the availability of these items

post-SP3? ...or know what's going on?

 

 

For what it's worth, I have no software on my PCs needing .NET Framework

1.1 or 3. And my required .NET Framework 2 (with all updates except the most

recent Service Pack) remains un-Service-Packed since one of the programs I

use that requires .NET 2 does not seem to like the fully service-packed .NET

2, so I'm really OK with these not being offered anymore by Custom Windows

Update, but I am curious.

 

Craig

[Guest PA Bear [MS MVP]]

Re: Windows Update doesn't see some updates post-SP3

 

Free unlimited installation and compatibility support is available for

Windows XP, but only for Service Pack 3 (SP3), until 14 Apr-09. Chat and

e-mail support is available only in the United States and Canada.

 

• US:

http://support.microsoft.com/oas/default.aspx?ln=en-us&prid=11273&gprid=522131

 

• CA:

http://support.microsoft.com/oas/default.aspx?ln=en-ca&prid=11273&gprid=522131

 

• UK:

http://support.microsoft.com/oas/default.aspx?ln=en-gb&prid=11273&gprid=522131

 

• AU:

http://support.microsoft.com/oas/default.aspx?ln=en-au&prid=11273&gprid=522131

 

• Other: http://support.microsoft.com/oas/default.aspx?gprid=1173 | select

Windows XP | select Windows XP Service Pack 3

--

~Robear Dyer (PA Bear)

MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002

AumHa VSOP & Admin http://aumha.net

DTS-L http://dts-l.net/

 

Craig wrote:

> Greetings,

>

> Prior to downloading and installing Win XP SP3 on two WinXP Home

> machines,

> a Custom Windows Update let me know that I could choose to install .NET

> Framework 1.1, 3 (and maybe 3.5), as well as letting me know that my

> current

> .NET Framework 2 had a Service Pack available--the one that was issued

> several months ago.

>

> After installing SP3, when I do a Custom (or for that matter, an Express)

> Windows Update, I'm still told that .NET Framework 1.1 is available to

> install, but I'm no longer told that the .NET Framework v2 Service Pack is

> available and I'm not told that I could download and install .NET

> Framework

> 3 or 3.5. This is true for two of two computers I've updated.

>

> At first, I wondered if these no-longer-offered options were part of

> WinXP

> SP3 but I do not see them listed under Add/Remove Programs and a couple of

> MS MVP fellas insisted that no .NET Framework installation or update was

> included with SP3 and I tend to believe them.

>

> Has anyone else seen the disappearance of the availability of these items

> post-SP3? ...or know what's going on?

>

>

> For what it's worth, I have no software on my PCs needing .NET Framework

> 1.1 or 3. And my required .NET Framework 2 (with all updates except the

> most

> recent Service Pack) remains un-Service-Packed since one of the programs I

> use that requires .NET 2 does not seem to like the fully service-packed

> .NET

> 2, so I'm really OK with these not being offered anymore by Custom Windows

> Update, but I am curious.

>

> Craig