Visual Studio 2008 Service Pack 1 Released

Visual Studio 2008 Service Pack 1 Released

  • Comments 15

Microsoft .NET Framework 3.5 Service Pack 1, Visual Studio 2008 Service Pack 1, and Team Foundation Server 2008 Service Pack 1 have been released. This is a big release on the heals of SQL Server 2008 which has a dependency on .and includes NET Framework 3.5 SP1.

This is a big release with many new features and improvements over previous releases. The service pack package itself has undergone a number of significant changes including a web bootstrap that downloads only the updates you need on your system and splits up larger patch packages into smaller packages that install together in a single transaction. For example, the default installation installs only VC libraries and tools for x86 so the patches which contain x64 and IA64 libraries and tools are not downloaded and applied. If you later install those features, re-run SP1 to update them.

There are a lot of updates and new packages. There are 5 update executables (.exe files), 4 installer packages (.msi files), and 13 patch packages (.msp files) per supported language. The executables actually contain a mix of installer and patch packages, including the .NET Framework 3.5 SP1.

If you're having problems installing NetFX 3.5 SP1, VS 2008 SP1, or TFS 2008 SP1 please be sure to run the log collection utility available for download. If you're installing VS2008 SP1 you will find an HTML log file in your %TEMP% directory with a name matching the pattern Microsoft Visual Studio 2008 SP1_*.html. When you open this file, the error will be displayed. With Internet Explorer you may need to first click the action bar that reads, "To help protect your security, Internet Explorer has restricted this webpage from running scripts or ActiveX control that could access your computer. Click here for options...". There is a lot of rich information in this log, and it links to other files containing more detail that have the same file name with the .txt extension.

Please watch here for more news about and support of SP1.

Leave a Comment
  • Please add 7 and 2 and type the answer here:
  • Post
  • If only it would install faster ;)

  • I would like to officially beg and plead for a new DVD on MSDN downloads that has Visual Studio 2008 with SP1 pre-applied.  You created one for the Express crowd, how about taking care of those of us that have actually paid  for our MSDN subscriptions (to the tune of over $4000 each)?  I've never understood Microsoft's attitude on this subject - rather than have a single MS employee take the time to create the disk and publish it, instead they have a single employee create the disk and publish instructions (if we're lucky) - thus requiring tens of thousands of developers to repeat the same damn steps.  Where is the logic in that?

  • I'd also love to see an integrated VS2008 w/ SP1 ISO, although I'd be happy with slipstreaming instructions. Is there an ETA on their availability (or even a rough draft)?

  • I want Visual Studio 2008 with SP1 .

    Or a way to make it myself.

  • Why does the VS2008 SP1 installer want to install ONLY on c: drive? And that too it requires 5GB of free space on the C: drive!

    this is really killing me...for various reasons, my vs2008 installation is on D: drive.

    This kind of constraint is not justified.

  • As mentioned yesterday .NET Framework 3.5 SP1 and Visual Studio 2008 SP1 were released. Here is a more

  • Sesh, because SP1 upgrades VS if VS is installed on C: it will have to upgrade files on C:. Also, Windows Installer itself - which is the engine that installs .msi and .msp files which comprise SP1 - requires a lot of space on your system drive. See for details.

    Watch this blog for upcoming information on potential workarounds that aren't already mentioned in the aforementioned blog post.

  • Even after reinstalling the RTM and running the patch removal tool I cannot install SP1. I'm getting error:

    You must first use <A HREF="">Microsoft Visual Studio Patch removal tool</A> before installing Visual Studio 2008 SP1.  The tool will verify Visual Studio integrity and remove previous Visual Studio 2008 updates or pre-release software

    Microsoft Visual Studio 2008 - KB944899

  • kanad, did the patch removal tool finished completely and successfully? Please try running it again then go to %TEMP% and ZIP the latest "Microsoft Visual Studio 2008 SP1*.*" files (by date modified) and provide them on a web server, then contact me with the path. If you need server space, you can sign up for 5 GB free at with only a free Live Passport.

  • I see the VS2008 SP1 installer is as ridiculously, absurdly slow as the VS2005 SP1 installer.  I don't understand why it takes an order of magnitude longer to patch the product than to originally install it.  It must take some serious engineering to drag out copying a couple hundred megabytes of files over 2+ hours.

  • JS, see the other article you commented on about how space is consumed by Windows Installer and I'm sure you'll see that "copying a couple hundred megabytes of files" is an understatement. There's a lot that happens behind the scenes when patching, and patching a product (when a great many files are patched) is often slower because of all that. But in most experiences seen so far, VS 2008 SP1 installs in about 1/3 the time of VS 2005 SP1 despite installing (potentially) 3-4 times as many files.

  • I, like Sesh have vs2008 installed on D:\ drive and sp1 only looks at C:\ for free space. The update is unable to progress and I can't free up enough space on C:\. Any word on a workaround yet? TIA

  • Tanski, there is no workaround. Windows Installer - the technology which installs VS and SP1 - requires a certain amount of space on your system drive. The SP1 bootstrap application actually looks on both C: and D: (in your configuration; generically on your system drive and on the main VS installation drive) for a certain amount of free space. For more information, see There are some things mentioned in there you can do to free up some space, but it may not be enough. I recommend always leaving your system partition plenty large as many products - whether using Windows Installer or not - need to install some components on the system drive, be in in Program Files\Common Files or in the system folder (though that is not generally recommended).

  • Also unable to install SP1 due to it requiring C: to have more space. Apparently you can't grow C: either under Windows. Sigh...

    How about:

    1) Use mount points instead of drive letters, so you don't have such rigid volumes, the idea of a "system disk" in terms of a volume is a throw back (e.g. how about zfs quota based volumes? Or paths where OS files live?).

    2) Make the installer smarter to figure out there is plenty of space on other drives, which would appear to work based off of the blog link at least.

    3) Also, shouldn't the installer honor %TEMP% and write it's temp files there? Rather than to the root of the drive?

  • Help. The patch removal tool fails with the following error:

    (IronSpigot::BaseMspInstaller::PerformAction) </span>PerformMsiOperation returned 0x66F<BR></span>

    I cannot run the sp1 install without the patch removal tool completing. The steps that created this situation are:

    I had sp1 beta installed so I ran the patch removal tool, but the system hung when it asked for installation media. I tried to restart without any success, so i deinstalled vs 2008. i did not bother deinstalling sp1 beta. i then reinstalled vs 2008, but it would not install sp1 without the patch removal tool which fails with the above error.

    What can I do now?

Page 1 of 1 (15 items)