Can't Update Microsoft.NET Framework
in [Windows Update]
|
From: jonb on 19 Feb 2005 21:29 I have the exact same errors. It keeps trying to install those two updates every time I shutdown, requiring an extra 1min to shutdown. What good is auto update if it doesn't work for 6 of us(x1000 probably)? MS charges $100 per support email, so forget that! How are we suppose to even tell them 6000 customers are affected? Maybe MS will fix it in the next auto update? "Mike" wrote: > I can't install the following: > >Security Update for Microsoft .NET Framework, Version 1.0 SP3, English (KB886906) > >Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1 (KB886903) > > When I try to, I get this message: > > Application has generated an exception that could not be handed. > Processid=0x9dc (2524)
From: bs2000 on 19 Feb 2005 21:45 I have tried what theses articles explain it never fixed anything "tablarlu" wrote: > See > http://support.microsoft.com/?kbid=824643 > and follow instructions > When it tells you to dowload SDK to get Msizap.exe jus go to this article > and use the download link there just to get the one utility instead of the > whole SDK. > http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 > > > "Bill Sharpe" wrote: > > > See the post "One solution to the KB886903 install problem" in this > > newsgroup on 2/15. > > A lot of effort involved, but this worked for me for kb886903, not for > > kb886906. > > > > Bill > > > > "Mike" <Mike(a)discussions.microsoft.com> wrote in message > > news:EF8A989F-ED94-4F87-92E2-40E3FB744173(a)microsoft.com... > > I can't install the following: > > >Security Update for Microsoft .NET Framework, Version 1.0 SP3, English > > >(KB886906) > > >Security Update for Microsoft .NET Framework, Version 1.1 Service Pack > > >1 (KB886903) > > > > When I try to, I get this message: > > > > Application has generated an exception that could not be handed. > > Processid=0x9dc (2524) > > > > > >
From: uncle beer on 20 Feb 2005 02:15 >OK that was just wronge. Couldn't agree more. While several "fixes" have been posted by various individuals (including now-cranky MVPs!), none have worked for me either. This is obviously a pretty widespread problem. MS usually makes updates extremely easy. I guess we're all stunned at the astounding LACK OF SUPPORT on this problem. Yours truly, Uncle Beer
From: uncle beer on 20 Feb 2005 05:15 >That's an entirely different problem! >-- >Noel Paton (MS-MVP 2002-2005, Windows) So, Noel...... When are we gonna see any kind of substantial FIX from MS concerning this snafu?? Yours truly, Uncle Beer
From: Bill Sharpe on 20 Feb 2005 14:23
The workaround for finally installing KB886903 as given in a post from Rolando E. Creagh on 2/15 is complex, but it worked on my machine. I have contacted MS support on 2/16, got a response 2/17 that the problem was being turned over to a support specialist who responded 2/18 with the same information as Creagh's post. I had already fixed the KB886903 install hang and asked how to fix the KB886906 problem, which persists. No reply as yet. The problem occurred for me 2/10 as I downloaded 11 security patches, two of which failed to install. If they had just not installed I wouldn't be too concerned. The fact that they brought up error messages at shutdown and again at restart and return from hibernation is what bothers me. I have a shield icon in my traybar saying that updates are ready to install. There's only one pending update now(KB886906) and I would like to get rid of it. There appear to be more than six of us with this or similar problems, based on the number of posts in this newsgroup. Considering the complexity of fixing the KB886903 problem MS obviously has not carefully thought out at least these two updates. I use newsgroups regularly but a number of people I know who use computers have no idea what a newsgroup is or that MS offers free support for update problems. Then there are the people who have no idea what a Windows Update is, but that's another subject! Bill "Noel Paton" <NoelDPspamless(a)btopenworld.com> wrote in message news:OJBNI50FFHA.1348(a)TK2MSFTNGP14.phx.gbl... Considering the number of people who download and install the fixes without any problems - hundreds of thousands a day, at least - the chances are that it's a peculiarity of your setup, rather than a problem with the patch. If we can work out what that peculiarity is, then we may be able to work out a way through the logjam. One way you can assist is to call PSS and ask them - any resolution then gets logged and eventually we all get to hear about it. Otherwise, it's a time-consuming (as if the PSS method wasn't!) process of eliminating possibilities, and a lot of research. -- Noel Paton (MS-MVP 2002-2005, Windows) |