It’s the end of the month: time to get potentially troublesome updates out of the way — starting with .NET patches.
Plus: Numerous nonsecurity updates offered for Win7 and Win8; coping with Office Click-to-Run updating.
Catching up on .NET Framework updates
In the U.S., the end-of-May Memorial Day weekend marks the unofficial start of summer. But that doesn’t mean taking a vacation from .NET updates. On the contrary, the end of the month is when I install .NET updates released during the previous Patch Tuesday (the second Tuesday of the month).
For the best results installing .NET patches, I recommend doing each separately.
Of the following list of patches, I recommend starting at the top with KB 2804576. If it installs without difficulty, work your way down the list, one update at a time. For example, XP users should then install KB 2804577 (.NET 4) if it’s offered. Windows 7 users should move on to KB 2804579 (.NET 3.5.1). If you’re offered KB 2804582 or KB 2804583 (.NET 4.5), install it last.
- KB 2804576 for .NET 2.0 and .NET 4 (XP, Vista, Win7)
- KB 2804577 for .NET 4 (XP)
- KB 2804579 for .NET 3.5.1 (Win7)
- KB 2804582 for .NET 4.5 (Vista, Win7)
- KB 2804583 for .NET 4.5 (Win8)
- KB 2804584 for .NET 3.5 (Win8)
Windows XP users won’t see the .NET 4.5 update — it’s supported only in Vista, Win7, and Win8. Windows 7 users should check whether they have .NET 1.0 installed before adding any .NET 4 or 4.5 updates. As noted in Aaron Stebner’s WebLog, .NET 1.0 service packs can’t be added if .NET 4 and/or 4.5 are installed.
If you run into trouble with a .NET patch, try the .NET Framework Repair Tool, available free on a Microsoft Download Center page. If it doesn’t fix the problem, follow Aaron’s instructions for using his .NET Framework cleanup tool.