Do not repair VS 2008 SP1 from installation media

Do not repair VS 2008 SP1 from installation media

  • Comments 22

If you need to repair Visual Studio 2008 once SP1 has been applied or wish to change which features are installed, you cannot run setup.exe from the original installation media.

When you run repair from media you may see an error like, "A problem has been encountered while loading the setup components. Canceling setup."

Workaround

Open the Control Panel and go to Add/Remove Programs, or on Vista click on the "Uninstall a program" link under Programs. Find Microsoft Visual Studio 2008 (the exact product name will vary based on edition and language installed) and click on the Uninstall/Change button. When setup launches and components are loaded, you will be asked to repair, change features, or uninstall. Choose the option you which to perform and continue as directed.

Details

Visual Studio is actually a collection of different installation packages, just as VS2008 SP1 is a collection of different installation packages. VS2008 SP1 replaces some of the original packages using minor or major upgrades and patches other products. This changes information about the products originally installed like the ProductCode and/or ProductVersion. This affects the detection logic that setup.exe uses to determine what to do when installing, repairing, or uninstalling the product.

This information is stored both on the installation media as well as on your hard disk under the target installation directory. For various reasons including that media is often write-protected, we can only update this information stored on your hard disk. So once SP1 is installed, the detection and package information on the installation media and on your hard disk are out of sync and only the copy on your hard disk contains the correct information.

Leave a Comment
  • Please add 3 and 2 and type the answer here:
  • Post
  • Can SP1 be slipstreamed into/onto the VS Media?  If so, what'd be the necessary steps given that there are at least two installers there (one for VS and the other for Team Explorer).

    Thanks!

  • Is there anyway to include VS 2008 SP1 in installation iso package?

  • onovotny and Mahdi, no SP1 cannot be slipstreamed in a way that is again installable using setup.exe.

  • please give us a guide on slipstream, it would be nice

  • Slipstream installs using setup.exe will not be officially supported.

  • So you mean to say that there is no workaround to slipstream Visual Studio 2008 SP1 ??

  • Avinash, there is no supported method to slipstream VS 2008 SP1 and still run setup.exe to install it all. I recommend installing both silently in succession (you could script it with a batch script) and start it before leaving work. It should only take a few hours to install both VS and SP1.

  • To Heath Stewart:

    Hi, Can you show me the script sample about install both VS2008 and SP1

    thanks.

  • Johnson, basically (and I'll expand on this more in a separate post) you need to create an unattended install of VS2008 and MSDN (optional) as Aaron has blogged for VS2005 (similar instructions for VS2008 - just replace "2005" with "2008" where appropriate) at http://blogs.msdn.com/astebner/archive/2004/11/29/272128.aspx.

    You then run VS2008 SP1 with /createlayout <target path> and then create a batch script that runs setup.exe /q for both of the installation points you created.

  • I actually wanted to add C++ to my Visual Studio 2008 Team System installation (which currently only has C# and Visual Basic) before installing SP1. Unfortunately, I'm getting that same error message: "A problem has been encountered..."

    I've tried it both from the installation disk, and from Add / Remove Programs ("Software" in the German Windows).

    I had an installation of VS 2005 on that machine before, that I have removed (after installing VS 2008).

    Last lines from the log are:

    [10/03/08,17:41:57] MSITOSIT: [2] ERROR processed; exception was thrown for retail build

    Developer Comment:  :  has no associated directory, verify the Feature table is correct

    Build Time:  Thu Dec 11 14:04:18 2003

    HRESULT:  -2147467259

    [10/03/08,17:41:57] Microsoft Visual Studio Team System 2008 Team Suite - ENU: [2] Servicing:  a SubComponent failed to construct

    [10/03/08,17:41:57] setup.exe: [2] ISetupModule::SetManager() failed in ISetupManager::LoadSetupObjectGuid() : vs_setup.dll

    [10/03/08,17:41:57] setup.exe: [2] CSetupManager::LoadSetupObjectname() - Failed in call to LoadSetupObjectGuid() for strName:  in file: vs_setup.dll

    [10/03/08,17:41:57] setup.exe: [0] LoadComponent(), LoadSetupObjectName failure: vs_setup.dll

    [10/03/08,17:41:57] setup.exe: [0] LoadComponent failed in ISetupManager::LoadComponentsFromDBObject(): vs_setup.dll

    [10/03/08,17:41:57] setup.exe: [2] CSetupManager::LoadDatabaseValues() - Failed in call to LoadComponentsFroMDBObjects()

    [10/03/08,17:41:57] setup.exe: [2] CSetupManager::RunIntro() - Failed to Load Database Values

    Any ideas how I can fix this?

  • Jashan, do you have any other patches currently installed for Team Suite? It so, please remove those patches (only older patches released shortly after Team Suite was released should be affected) and try installing VC++ again. In fact, assuming that works and you then install SP1, don't bother re-installing those patches because the fixes will be in SP1 so you can save some time.

  • I have been battling the same problem for a week. Searched endlessly and to no avail. Uninstalled and reinstalled, rebooted, scrubbed the registry and deleted the directory. This is one of the few issues that continues to evade me.

    This all started when I wanted to add a data source to a web app I was developing. I got a strange "not found" error.

    Anyone got an answer yet?

    Thanks much

    -Ruzmak

  • When attempting to add features to Visual Studio 2008 after it has already been installed, you may see

  • Jashan and Ruzmak, please see http://blogs.msdn.com/heaths/archive/2008/10/06/adding-features-to-visual-studio-2008-may-fail-to-load-setup-components.aspx which might describe the issue you're experiencing along with the workaround.

  • Thanks, Heath! Your tip was very helpful

Page 1 of 2 (22 items) 12