• .NET Framework 3.5 Service Pack 1 pushed in weird places

    I just received an automatic notification on my 32-bit Vista machines, saying there’s a high priority update available. When I click through, I’m informed that Microsoft wants to update .NET Framework 3.5 to Service Pack 1.

    That’s a little annoying, but here’s the weird part:

    My Windows 7 Build 7000 machine isn’t getting nagged, and

    Several of my Windows XP machines are getting nagged, but they’re running .NET Framework 2.0.

    Where does Microsoft get off pushing a version upgrade of .NET Framework as a “high priority update”?

    Thanks to SB for the heads-up!

    UPDATE: Microsoft’s article

    KB894199 identifies this as the anticipated “out of sequence” patch I wrote about a few days ago. The KB article says:

    The Microsoft .NET Framework 3.5 Service Pack 1 is a full cumulative update that contains many new features that build incrementally upon the .NET Framework 2.0, the .NET Framework 3.0, and the .NET Framework 3.5. It includes cumulative servicing updates to the .NET Framework 2.0 and the .NET Framework 3.0 subcomponents. The .NET Framework 3.5 Family Update provides important application compatibility updates.

    So there’s something seriously out of whack: either the update is identifying itself incorrectly (Windows Update says it’s offering .NET 3.5 SP 1, when it may just be updating .NET 2.0 or 3.0), or somebody at Microsoft set things up so the wrong patch is pushed.

    Either way, you would be well advised to avoid the patch until it’s all sorted out.