marty44 wrote: > I am unable to install as many others have indicated. Is it a Microsoft > problem? Does anyone have a fix? I am tired of seeing the yellow shield pop > up!
Unless Users contact MS and report this installation issue then Microsoft will *never* be aware of it. This is an *ongoing issue with .NET Security updates*.
PLEASE call MS as they will provide *no-charge support* in getting this update installed. From KB953927:
" How to obtain help and support for this security update
For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for support issues with security updates, visit the Microsoft International Support Web site: http://support.microsoft.com/common/international.aspx?rdpath=4 North American customers can also obtain instant access to unlimited no-charge e-mail support or to unlimited individual chat support by visiting the following Microsoft Web site: http://support.microsoft.com/oas/default.aspx?&prid=7552 "
MowGreen =============== *-343-* FDNY Never Forgotten ===============
banthecheck.com "Security updates should *never* have *non-security content* prechecked"
With all due respect Mow, if MS are still unaware of the widespread problems with the latest suite of updates, they have their heads right up their collective arses (or asses, if you prefer). It is unfair to users as well as to you guys who assist in these groups day in and day out.
Bill
"MowGreen" <mowgr...@nowandzen.com> wrote in message
>> I am unable to install as many others have indicated. Is it a Microsoft >> problem? Does anyone have a fix? I am tired of seeing the yellow shield >> pop up!
> Unless Users contact MS and report this installation issue then Microsoft > will *never* be aware of it. > This is an *ongoing issue with .NET Security updates*.
> PLEASE call MS as they will provide *no-charge support* in getting this > update installed. > From KB953927:
> " How to obtain help and support for this security update
> For home users, no-charge support is available by calling 1-866-PCSAFETY > in the United States and Canada or by contacting your local Microsoft > subsidiary. For more information about how to contact your local Microsoft > subsidiary for support issues with security updates, visit the Microsoft > International Support Web site: > http://support.microsoft.com/common/international.aspx?rdpath=4 > North American customers can also obtain instant access to unlimited > no-charge e-mail support or to unlimited individual chat support by > visiting the following Microsoft Web site: > http://support.microsoft.com/oas/default.aspx?&prid=7552 "
Bill wrote: > With all due respect Mow, if MS are still unaware of the widespread > problems with the latest suite of updates, they have their heads right > up their collective arses (or asses, if you prefer). It is unfair to > users as well as to you guys who assist in these groups day in and day out.
> Bill
LOL, Bill. Unfair or not, trust me, MS is *not* aware of how many Users are experiencing issues installing the latest round of updates unless said Users contact them. There is no MS presence in this newsgroup.
In regards to updating, the primary method for MS' data collection comes from Users' systems sending it to MS. But, that data is skewed when an update appears to install properly, the info is sent to MS servers, the User reboots, and the update is offered again. The User attempts to install it again, the data is again sent as a succesful installation, the User reboots, the update is offered again.
After reading a great deal of posts in this NG it appears that a primary cause of update installation failure this month is that there were just too many of them being done at once. Then add in a kernel update and an update for the notoriously brittle .NET Framework. The result is what we're seeing in NGs and on forums ... a *much* higher number of Users reporting update installation issues. And wireless networks break ... and systems don't boot after installing the updates ... and broken .NET Frameworks that must be uninstalled and reinstalled.
It's highly unusual to see the number of posts that show a User manually downloading the updates, installing them, rebooting, and there are no installation issues. To me, that's an indication that certain updates should have installed on their own (known as an exclusive installation) and NOT in conjunction with the installation of other updates.
> Friday, October 16, 2009 > Changes to existing Non-Security Content:
> * Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) > o Updating metadata of the following items to mark them for *exclusive install*: > * Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update for .NET > versions 2.0 through 3.5 (KB951847) x64 > * Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update for .NET > versions 2.0 through 3.5 (KB951847) x86
The .NET update is extremely complex and it needed to be installed by itself with no other update installation taking place. It is now thanks to those who immediately contacted MS to report the installation failures. You can bet your bottom dollar that those who reported this issue were Business or Enterprise Users. *Home Users need to report updating issues* as Business and Enterprise do so that MS is made aware of them.
MowGreen =============== *-343-* FDNY Never Forgotten ===============
banthecheck.com "Security updates should *never* have *non-security content* prechecked"
> > With all due respect Mow, if MS are still unaware of the widespread > > problems with the latest suite of updates, they have their heads right > > up their collective arses (or asses, if you prefer). It is unfair to > > users as well as to you guys who assist in these groups day in and day out.
> > Bill
> LOL, Bill. Unfair or not, trust me, MS is *not* aware of how many Users > are experiencing issues installing the latest round of updates unless > said Users contact them. There is no MS presence in this newsgroup.
> In regards to updating, the primary method for MS' data collection > comes from Users' systems sending it to MS. But, that data is skewed > when an update appears to install properly, the info is sent to MS > servers, the User reboots, and the update is offered again. > The User attempts to install it again, the data is again sent as a > succesful installation, the User reboots, the update is offered again.
> After reading a great deal of posts in this NG it appears that a primary > cause of update installation failure this month is that there were just > too many of them being done at once. Then add in a kernel update and an > update for the notoriously brittle .NET Framework. The result is what > we're seeing in NGs and on forums ... a *much* higher number of Users > reporting update installation issues. > And wireless networks break ... and systems don't boot after installing > the updates ... and broken .NET Frameworks that must be uninstalled and > reinstalled.
> It's highly unusual to see the number of posts that show a User manually > downloading the updates, installing them, rebooting, and there are no > installation issues. To me, that's an indication that certain updates > should have installed on their own (known as an exclusive installation) > and NOT in conjunction with the installation of other updates.
> > Friday, October 16, 2009 > > Changes to existing Non-Security Content:
> > * Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) > > o Updating metadata of the following items to mark them for *exclusive install*: > > * Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update for .NET > > versions 2.0 through 3.5 (KB951847) x64 > > * Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update for .NET > > versions 2.0 through 3.5 (KB951847) x86
> The .NET update is extremely complex and it needed to be installed by > itself > with no other update installation taking place. It is now thanks to > those who immediately contacted MS to report the installation failures. > You can bet your bottom dollar that those who reported this issue were > Business or Enterprise Users. > *Home Users need to report updating issues* as Business and Enterprise > do so that MS is made aware of them.
I am having problems downloading the newest set of updates and after reading this post while looking for a solution it appears to me that MowGreen has a vast knowledge of how to fix this problem. Please, I need your help. My problem comes with the downloading of a critical update and i guess it is called KB973636. I have gone thru the searches looking for it, can't find it. WTH? And please be nice because I am not a computer whiz at all but I give it my best shot. Any help you can be will be appreciated. Thanks.
> > With all due respect Mow, if MS are still unaware of the widespread > > problems with the latest suite of updates, they have their heads right > > up their collective arses (or asses, if you prefer). It is unfair to > > users as well as to you guys who assist in these groups day in and day out.
> > Bill
> LOL, Bill. Unfair or not, trust me, MS is *not* aware of how many Users > are experiencing issues installing the latest round of updates unless > said Users contact them. There is no MS presence in this newsgroup.
> In regards to updating, the primary method for MS' data collection > comes from Users' systems sending it to MS. But, that data is skewed > when an update appears to install properly, the info is sent to MS > servers, the User reboots, and the update is offered again. > The User attempts to install it again, the data is again sent as a > succesful installation, the User reboots, the update is offered again.
> After reading a great deal of posts in this NG it appears that a primary > cause of update installation failure this month is that there were just > too many of them being done at once. Then add in a kernel update and an > update for the notoriously brittle .NET Framework. The result is what > we're seeing in NGs and on forums ... a *much* higher number of Users > reporting update installation issues. > And wireless networks break ... and systems don't boot after installing > the updates ... and broken .NET Frameworks that must be uninstalled and > reinstalled.
> It's highly unusual to see the number of posts that show a User manually > downloading the updates, installing them, rebooting, and there are no > installation issues. To me, that's an indication that certain updates > should have installed on their own (known as an exclusive installation) > and NOT in conjunction with the installation of other updates.
> > Friday, October 16, 2009 > > Changes to existing Non-Security Content:
> > * Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) > > o Updating metadata of the following items to mark them for *exclusive install*: > > * Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update for .NET > > versions 2.0 through 3.5 (KB951847) x64 > > * Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update for .NET > > versions 2.0 through 3.5 (KB951847) x86
> The .NET update is extremely complex and it needed to be installed by > itself > with no other update installation taking place. It is now thanks to > those who immediately contacted MS to report the installation failures. > You can bet your bottom dollar that those who reported this issue were > Business or Enterprise Users. > *Home Users need to report updating issues* as Business and Enterprise > do so that MS is made aware of them.
|
