Re: service pack 3, do I need it?




"Craig" wrote...

"Shenan Stanley" wrote...

Craig wrote:
Contrary to what I had been told earlier, I'm pretty sure that SP3
will install .NET Framework Version 2 and 3 (or is it 3.5?),
complete with their service packs. It doesn't install .NET 1.1 and
I'm unsure if it would update a PC's version 1.1 if found on a PC.

SP3 contains no .NET Frameworks or updates - nor does it require any that
I have found. There are many people out there without any .NET
Frameworks - 1.1, 2.0. 30. or 3.5 (non-cumulative.)

Hmm, what you say does agree with what I had been told shortly before SP3
became available. But I'm confused. Prior to installing SP3, my full (not
Express) Windows Update always reminded me that my .NET Framework v2 had a
Service Pack available to update it...and that I was offered .NET
Framework v 3 (or maybe it was 3.5) and .NET Framework 1.1 to install. I
chose not to install any of these three updates so all three offers were
made each time I did a full Windows Update. But now after installing SP3,
I'm not being offered a v2 update or an installation of 3. I am still
offered the 1.1 installation. If SP3 didn't install and update .NET
Framework 2 and 3, then why am I no longer be offered these with Windows
Update? I am curious and confused right now. Thanks.

Craig

Shenan,

OK, I'm getting off the OP's questions, but in looking further, I believe
you are correct and SP3 does not add or update .NET Frameworks. In checking
through my "Add/Remove Programs" with "show updates," all that I see is my
original unservice-patched .NET 2. I do not see that my system has patched
..NET 2 or installed .NET 3 when installing SP3.

There is a problem still. Prior to installing SP3, Windows Update told me
I had a .NET 2 Service Pack available and that all of .NET 3 was also
available to add (as well as .NET 1.1). After upgrading my XP to SP3,
Windows Update (Custom, not Express) no longer offers me the upgrade to my
installed .NET 2 or the installation of .NET 3. I wonder if this is a
bug/oversight on MS's part post-SP3 and wonder if it'll be remedied in the
future to again offer me the various .NET Framework stuff.

Craig


.



Relevant Pages

  • Re: Simply security improvements that Microsoft has not done
    ... Windows Update to find the latest updates. ... > Users with a dialup modem are unlikely to do this because of the download ... > Developing programs that run under the .Net framework 1.1 ... > After installing a fresh copy of Windows XP Pro and then installing SP2 I ...
    (microsoft.public.windowsupdate)
  • Re: COMAPI FATAL: Unable to connect to the service (hr=80080005)
    ... If having all those .NET Framework versions & updates installed concerns you, please discuss it in a new thread in microsoft.public.windowsxp.general newsgroup. ... I do not think that installing the .NET Framework updates had anything to do with Windows Update starting to work again. ... could update Internet Explorer 7 back to a new 8 release 1 that WORKS ...
    (microsoft.public.windowsupdate)
  • Re: COMAPI FATAL: Unable to connect to the service (hr=80080005)
    ... I wouldn't add to them by installing beta software ... Internet Explorer security update that just released in Feb 2009 and is ... me to find that particular download and of course when I go to Windows ... the very thorough Castle Cops How To Fix Windows Update internet file ...
    (microsoft.public.windowsupdate)
  • Installed SP3, now getting "Generic Host Process for Win32 Services has encountered a problem" messa
    ... After the required restart, it pushed SP3 to me (I'd had a problem ... related to a corrupted installation file installing this previously). ... The yellow Windows update shield was there again and pushed another ...
    (microsoft.public.windowsxp.general)
  • Re: COMAPI FATAL: Unable to connect to the service (hr=80080005)
    ... Explorer 8 running fast ... ... some of them but they were not BITS or Windows Update ... ... and this download seem to be happening at a much slower pace than what I have ... I wouldn't add to them by installing beta ...
    (microsoft.public.windowsupdate)

Loading