NET FRAMEWORK 2.0 and 3.0 SP1

These SP1 Framework updates are issued by the update site following a request
from my supervisor to install MSN Messenger at the office. It had been
previously installed (Live version 8.1) from home. The primary difference is
that now, the proxy is turned on in the options - the proxy option was not
used from home.

I am not sure why it triggered the SP1 update of the NET Framework 2.0 and
3.0 or even sure if the Network Admin here has discovered a way to block
specific downloads of updates and this is why it is occuring. Clicking the
red question mark lists no explanation except to take a trip here and leave a
message.

I will try to re-install from home this evening and update the newsgroup on
this thread (to be sure it is not blocked on the network domain by a GP (or
something along these lines). Meanwhile, SP1 does not install for NET
Framework 2.0 or 3.0 and the filters I used to pull information on this did
not yield any significant information.
--
Regards,
Jamie

..NET Framework 2.0 SP1 and .NET Framework 3.0 SP1 were released to the
Windows Update servers on 04 Dec-07. Both were first available at the
Download Center on 20 Nov-07.

Windows version, please?

Check Windowsupdate.log (%windir%\Windowsupdate.log) for errors associated
with the download/install.

How to read the Windowsupdate.log file
http://support.microsoft.com/kb/902093

The Resolution in following KB article *might* help (feel free to ignore the
title):

When you try to install an update for the .NET Framework 1.0, 1.1, or 2.0,
you may receive Windows Update error code "0x643" or Windows Installer error
code "1603":
http://support.microsoft.com/kb/923100
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin http://aumha.net
DTS-L.ORG http://66.39.69.143/


thejamie wrote:
> These SP1 Framework updates are issued by the update site following a
> request from my supervisor to install MSN Messenger at the office. It had
> been previously installed (Live version 8.1) from home. The primary
> difference is that now, the proxy is turned on in the options - the proxy
> option was not used from home.
>
> I am not sure why it triggered the SP1 update of the NET Framework 2.0 and
> 3.0 or even sure if the Network Admin here has discovered a way to block
> specific downloads of updates and this is why it is occuring. Clicking
> the
> red question mark lists no explanation except to take a trip here and
> leave
> a message.
>
> I will try to re-install from home this evening and update the newsgroup
> on
> this thread (to be sure it is not blocked on the network domain by a GP
> (or
> something along these lines). Meanwhile, SP1 does not install for NET
> Framework 2.0 or 3.0 and the filters I used to pull information on this
> did
> not yield any significant information.

Both .NET 2.0 SP1 and 3.0 SP1 were just released recently.
They have nothing to do with Messenger, AFAIK.
If they still will not install from home, please let us know.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


thejamie wrote:

> These SP1 Framework updates are issued by the update site following a request
> from my supervisor to install MSN Messenger at the office. It had been
> previously installed (Live version 8.1) from home. The primary difference is
> that now, the proxy is turned on in the options - the proxy option was not
> used from home.
>
> I am not sure why it triggered the SP1 update of the NET Framework 2.0 and
> 3.0 or even sure if the Network Admin here has discovered a way to block
> specific downloads of updates and this is why it is occuring. Clicking the
> red question mark lists no explanation except to take a trip here and leave a
> message.
>
> I will try to re-install from home this evening and update the newsgroup on
> this thread (to be sure it is not blocked on the network domain by a GP (or
> something along these lines). Meanwhile, SP1 does not install for NET
> Framework 2.0 or 3.0 and the filters I used to pull information on this did
> not yield any significant information.

This one is confounding. I searched a bit more and discovered Net Framework
3.5 is on my system (or was - it is gone now and all is well). The MSN
Messenger figures in because it issued a warning to check the Windows Update
site for updates adding the proxy information.

Once I was up at the site and WU attempted to update DF2.0 and DF3.0, the
dfsvc.exe started acting up and the GUIDs in the registry for the MSDN
license were not at all the same as the ones in my registry. In addition
devenv (VS IDE) SQL Mgr stopped working. All applications that referred to
the Click Once Manifest stopped working (dfsvc.exe). And to make matters
worse, everything pointed to the NET Framework 2. and 3. for a reinstall -
prevented, of course, by 3.5 which is inclusive of both.

What I am missing here is how I managed to download 3.5. It is a beta. How
did it get into my environment? URGH! I must have been sleep walking or
something.

Anyhow, all is well now. Fair warning to those who download betas (which
would be everyone on this site I expect), 3.5 is problematic only after you
install and then return to the Windows Update site. Once there, the 2 and 3
updates fail and your system goes haywire until you uninstall the 3.5.
--
Regards,
Jamie


"MowGreen [MVP]" wrote:

> Both .NET 2.0 SP1 and 3.0 SP1 were just released recently.
> They have nothing to do with Messenger, AFAIK.
> If they still will not install from home, please let us know.
>
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> thejamie wrote:
>
> > These SP1 Framework updates are issued by the update site following a request
> > from my supervisor to install MSN Messenger at the office. It had been
> > previously installed (Live version 8.1) from home. The primary difference is
> > that now, the proxy is turned on in the options - the proxy option was not
> > used from home.
> >
> > I am not sure why it triggered the SP1 update of the NET Framework 2.0 and
> > 3.0 or even sure if the Network Admin here has discovered a way to block
> > specific downloads of updates and this is why it is occuring. Clicking the
> > red question mark lists no explanation except to take a trip here and leave a
> > message.
> >
> > I will try to re-install from home this evening and update the newsgroup on
> > this thread (to be sure it is not blocked on the network domain by a GP (or
> > something along these lines). Meanwhile, SP1 does not install for NET
> > Framework 2.0 or 3.0 and the filters I used to pull information on this did
> > not yield any significant information.
>

Thanks for the information, Jamie. Unfortunately, other Users may not be
as adept as you are in diagnosing the SPs installation failures.
Hopefully, they'll see this post. <w>

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


thejamie wrote:

> This one is confounding. I searched a bit more and discovered Net Framework
> 3.5 is on my system (or was - it is gone now and all is well). The MSN
> Messenger figures in because it issued a warning to check the Windows Update
> site for updates adding the proxy information.
>
> Once I was up at the site and WU attempted to update DF2.0 and DF3.0, the
> dfsvc.exe started acting up and the GUIDs in the registry for the MSDN
> license were not at all the same as the ones in my registry. In addition
> devenv (VS IDE) SQL Mgr stopped working. All applications that referred to
> the Click Once Manifest stopped working (dfsvc.exe). And to make matters
> worse, everything pointed to the NET Framework 2. and 3. for a reinstall -
> prevented, of course, by 3.5 which is inclusive of both.
>
> What I am missing here is how I managed to download 3.5. It is a beta. How
> did it get into my environment? URGH! I must have been sleep walking or
> something.
>
> Anyhow, all is well now. Fair warning to those who download betas (which
> would be everyone on this site I expect), 3.5 is problematic only after you
> install and then return to the Windows Update site. Once there, the 2 and 3
> updates fail and your system goes haywire until you uninstall the 3.5.