It’s time to revisit the many .NET Framework updates, starting with the often problematic Windows XP/.NET update process.
Windows 8 also has a few platform fixes, and there are a few leftovers for Vista and Windows 7.
Typically, Patch Watch items are broken down by patch number. But due to the complexity of .NET updates, I’ve divided them up by platform. For more on these updates, see MS13-004 and MS13-007.I’ve not seen reports of problems with any of these .NET updates — aside from the usual installation problems.
Installing .NET updates on Windows XP
Windows XP SP3 and XP Pro x64 SP2 users should see one or more of the following .NET updates:
- KB 2742595 for .NET 4
- KB 2742596 for .NET 2.0 SP2
- KB 2742597 for .NET 1.1 SP1
- KB 2742607 for .NET 1.0 SP3
- KB 2736416 for .NET 3.5 SP1
- KB 2736428 for .NET 4
- KB 2756918 for .NET 3.0 SP2
Windows XP doesn’t typically ship with .NET installed; it accompanies any application — such as QuickBooks and video-card control panels — that needs it. However, it’s not unusual to find .NET 1.0 or 1.1 on Windows XP systems.
The less-common .NET 4 typically shows up with the latest version of QuickBooks 2013 and other recent business applications. If you see .NET 4 and you are fairly certain you don’t have an application that needs it, it’s possible that Microsoft Update installed it. To pave the way toward new and better apps, Microsoft offers .NET 4 to any system with .NET 3.0 or 3.5 installed. Microsoft needn’t be so pushy; most of the business software I use includes .NET 4, if it’s required.
Adding .NET patches to Windows XP. Patching .NET on XP systems is a crapshoot — it either installs nicely or fights you all the way. Start by reviewing the process of running Aaron Stebner’s .NET Framework Cleanup Tool (site), so you can remove and reinstall any .NET updates that fail. Aaron states that this tool should be used when all else fails. I believe just the opposite: it’s the first tool I go to when .NET fails to install.