locked
VS2010 fails to install RRS feed

  • Question

  • Trying to install VS 2010 Premium on Win7.  It falls over at the first step:

    [11/11/10,13:40:08] VC 9.0 Runtime (x86): [2] Error: Installation failed for component VC 9.0 Runtime (x86). MSI returned error code 1603
    [11/11/10,13:40:11] VS70pgui: [2] DepCheck indicates VC 9.0 Runtime (x86) is not installed.
    [11/11/10,13:40:11] VS70pgui: [2] DepCheck indicates VC 10.0 Runtime (x86) was not attempted to be installed.

    etc etc

    Read loads of forum posting which mostly result in a complete machine rebuild - I'd prefer not to go down this route...

    I've tried the following:

    - removing VC 9.0 Runtime which was there for VS 2008

    - cleaned the registry

    - uninstalled everything from VS 2008

    - applied latest OS patches

    I've looked at the log and found the following which may be relevant:

    [11/11/10,15:28:47] VC 9.0 Runtime (x86): (MsiRetryHelper) calling MsiInstallProduct() now.
    [11/11/10,15:28:59] VC 9.0 Runtime (x86): MSI Record result detail: Error 1935.An error occurred during the installation of assembly 'Microsoft.VC90.ATL,version="9.0.30729.4974",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x8007042D.
    [11/11/10,15:28:59] VC 9.0 Runtime (x86): MSI Record result detail error code: 1935
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): Action returned 1603/1935 - Retry counters:
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1618: 0/100
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603: 1/0
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1303: 0/2
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1306: 0/2
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1308: 0/2
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1309: 0/2
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1310: 0/2
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1311: 0/2
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1329: 0/2
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1330: 0/2
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1335: 0/2
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1406: 0/2
    [11/11/10,15:29:01] VC 9.0 Runtime (x86): 1603/1706: 0/2
    [11/11/10,15:29:02] VC 9.0 Runtime (x86): 1603/1719: 0/2
    [11/11/10,15:29:02] VC 9.0 Runtime (x86): 1603/25543: 0/2
    [11/11/10,15:29:02] VC 9.0 Runtime (x86): Will not retry.
    [11/11/10,15:29:02] InstallReturnValue: GFN_MID Chained VC 90 Runtime for x86, 0x643
    [11/11/10,15:29:02] Setup.exe: GetGlobalCustomProperty - Property: {B7D05DBA-FC13-4B6C-B30E-28967A0FFF4E} - PropertyName: Reboot Count - Value: 1
    [11/11/10,15:29:02] VC 9.0 Runtime (x86): Reboot Counter = 1
    [11/11/10,15:29:02] VC 9.0 Runtime (x86): This component HAS already request a reboot prior to installation.
    [11/11/10,15:29:02] Setup.exe: AddGlobalCustomProperty
    [11/11/10,15:29:02] Setup.exe: AddGlobalCustomProperty
    [11/11/10,15:29:02] VC 9.0 Runtime (x86): ***ERRORLOG EVENT*** : Error: Installation failed for component VC 9.0 Runtime (x86). MSI returned error code 1603
    [11/11/10,15:29:02] Setup.exe: GetGlobalCustomProperty - Property: {BBE1827C-F2FD-4FDA-A6D6-C83B62FFFDCA} - PropertyName: compfailed - Value: 0
    [11/11/10,15:29:02] VC 9.0 Runtime (x86): CBaseComponent::LaunchWatson() - Obtained CSetupWatson instance

     

    Thursday, November 11, 2010 5:09 PM

Answers

  • Sorry for the belated response.

    From the error message, the problem was happening to the VC runtime installation, and the error indicated a service did not start due to a logon failure.

    So try to ensure you run the installer with admin priviledge and "run as Admin" to pass UAC. Or it could also be blocked by some AVs on the machine.

    Thanks.


    Figo Fei
    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact msdnmg@microsoft.com 


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by Figo Fei Thursday, November 18, 2010 6:04 AM
    Tuesday, November 16, 2010 5:53 AM

All replies

  • Does anyone at Microsoft who watches these forums have an answer to this issue before I reinstall Windows 7? 

    Friday, November 12, 2010 4:21 PM
  • Ah well, looks like no-one from MS can answer this one...sadly it's a common issue with loads of inconclusive posts.  I've got my Windows 7 Install disk ready to do some machine rebuilting.  Drastic, but it appears to be the only solution to the problem.
    Monday, November 15, 2010 3:20 PM
  • Sorry for the belated response.

    From the error message, the problem was happening to the VC runtime installation, and the error indicated a service did not start due to a logon failure.

    So try to ensure you run the installer with admin priviledge and "run as Admin" to pass UAC. Or it could also be blocked by some AVs on the machine.

    Thanks.


    Figo Fei
    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact msdnmg@microsoft.com 


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by Figo Fei Thursday, November 18, 2010 6:04 AM
    Tuesday, November 16, 2010 5:53 AM
  • I am running setup.exe with "run as administrator," but the VC90 ATL component mentioned above still fails to install. I have even uninstalled all versions of the 2005 and 2008 runtimes, and still get the error. I've also tried first installing the 2008 SP1 runtime from downloads, but it still fails on this install.

    Specifically, it starts the install, pretty quickly tells me "you have to reboot to continue" (with no option to click "reboot later") and after reboot, vc90 runtime fails to install.

    VC 9.0 Runtime (x86): [2] Error: Installation failed for component VC 9.0 Runtime (x86). MSI returned error code 1603


    XNA/DirectX MVP 2006-present
    Monday, December 6, 2010 3:09 AM
  • I had the same problem (Windows 7 x64 Pro). Enabled pretty much all of the Microsoft Services (msconfig) and ran setup as Administrator and then it worked.
    Thursday, February 24, 2011 8:37 PM