News Stay informed about the latest enterprise technology news and product updates.

Windows Service Pack Blocker soon to lose XP (SP3), Vista (SP1) blocks

Since December 2007, Microsoft has offered a Windows Service Pack Blocker Tool Kit to organizations that wish to prevent deployment of service packs in their environments. Blogging for the Vista Team Blog, Microsoft Windows Communication Manager Matt LeBlanc indicated on 1/29/2008 that this tool will soon relinquish its ability to block XP SP3 and Vista SP1. The expiration date for XP SP3 is 5/19/2008 and for Vista SP1 is 4/28/2009, each 12 months to the day from the original release of those service packs, and each in keeping with the tool’s stated ability to block current service packs up to 12 months after their release dates. After these dates, these SPs will be available directly from Windows Update.

With Vista and Windows Server 2008 shortly to become the focus of a shared SP2 release (currently guesstimated for April, 2009), this tool retains its capability and may be used to block or defer installation of this new SP for up to 12 months after its eventual general availability date. The Blocker offers admins three different ways to manage Service Packs:

  • An MS-signed executable that manages a Registry Key (in HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate) to block or allow Windows Update delivery of a current SP.
  • A script that works like the MS executable except that it allows the admin to supply the name of a remote machine where the block/unblock operations may be performed.
  • An administrative (.ADM) template that permits admins to import GPOs to block or unblock delivery of SPs into a Group Policy environment.

As Microsoft observes in connection with the Blocker “this toolkit will not prevent the installation of the service pack from CD/DVD, or from the stand-alone download package. This simply prevents the service pack from being delivered over Windows Update.”

For environments where more time is often needed to test and accommodate SPs, the Blocker can be a handy tool. As long as admins understand it does not last forever–in fact, a year from the SPs general availability date is as much leeway as it can provide–the tool can be a useful element in their Vista, XP, and Windows Server 2008 toolbox.

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

I have a problem: my XP is running SP2. When I try to install SP3, it rejects it. My (horrible Toshiba) Vista refuses to install SP1. What will happen to these 2 machines???
If the SPs can't be installed the status of SP blocker toolkit won't affect them at all. I'm curious, though: what kind of messages do these failures product? Do you get anything useful from the Event Viewer or pop-ups to help gather more information about the causes of failure? When the time comes to install SPs, I usually make a complete image backup before I start. Because you sometimes cannot recover/roll back from a partial/incomplete SP install this may be the only way to restore a system that experiences difficulty partway through to proper operation. I'd urge you to do this, and also to report back here with more information about what Windows reports when the SP applications fails. HTH, and thanks for posting, --Ed--