Yeh, I know that. But when the SP1 comes out? You can't pick ou bits of a service pack, can you?FC, you can always delete any update by going to the Windows Update panel and clicking on the "Installed Updates" link in the lower left corner. Look over all of your updates and highlight the one(s) that you want to remove.
Then click the "Uninstall a program" link to remove the highlighted update(s) and restart your computer to complete the process.
I've done this before when I decided to delete the Microsoft .NET 4 framework update.
BTW .. for this patch Tuesday, I had 12 updates to install.
Do you be before the event or after, Cat? I find the links in the right hand window give me all the information I could possible want.And why all of the hush-hush by M$ over this? I found out the real reasons for these updates through third parties, not by Microsoft. Not once, in the releases by M$, were the actual reasons given.
These were major security issues, why does M$ wants to keep us in the dark?
Cat
There is only two listings for that update, both listings failed to update. Who knows it may update tomorrow.Cliff.
There are one or two reasons for this message. The most common reason which I experience is that, through other paths, I have already got the update. Have a browse through your history.
Microsoft .NET Framework 3.5 SP1 Update for Windows 7 and Windows Server 2008 R2 for x64-based Systems (KB982526)
Installation date: 6/23/2010 1:35 AM
Installation status: Failed
Error details: Code 80200053
Update type: Important
This update addresses a set of known issues of the Microsoft .NET Framework 3.5 Service Pack 1. After you install this item, you may have to restart your computer.
More information:
http://go.microsoft.com/fwlink/?LinkId=190967
Help and Support:
http://support.microsoft.com
Here it is:WOW! What a thread! This has people stirred up as much I could ever do...
I see a few paranoid people here... if they have "proof" through 3rd party sources about the "security issues" give the links so we can check them out.
Yes, I have had issues in the past with updates not installing the first time around, usually within a few days they do and all is good.
.NET builds upon itself, so that's how it works. It has always been that way with .NET and probably always will, at least for near future.
Service Packs have always included the critical and security updates, not the "recommended" updates or optional updates.
That seems like more of an excuse to me, than an explanation, but I agree that it mirrors what Microsoft would tell consumers, as they're masters at doublespeak.Microsoft is supposedly trying to protect you or very often protect themselves from software piracy.
What did you find on that page which explained the updates, and what did you find "informative"?Here it is:
http://www.computerworld.com/s/article/9190719/Microsoft_release
Check it out, these things were never described in detail by M$, they only give reasons that tech users understands, not common since details that the average user can understand.
I mean, a lot was at stake here. And that was only one of the third party articles I could scrounge to find.
Cat
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.