Microsoft Visual Studio 2008 Sp1 Does Not Seem to Be Installed Please Install It and Try Again

• Remove From My Forums

VS2008 SP1 Install Fail on Win7 RTM Ultimate x64

• Question

• I have been trying to install VS2008 Team Test Edition on Windows 7 x64.

  Initial install was fine, simply the SP1 install failed with log file entries:

  -----------------------------------------------------------------------------
  

  C:\Users\joe\AppData\Local\Temp\Microsoft Visual Studio 2008 SP1\VC_IA64Runtime.exe - Exe installer's log file/hint (%temp%\dd_VC_IA64Runtime*.txt|%temp%\..\dd_VC_IA64Runtime*.txt) does not exist or is invalid.
  Exe (C:\Users\joe\AppData\Local\Temp\Microsoft Visual Studio 2008 SP1\VC_IA64Runtime.exe) succeeded.
  

  Final Consequence: Installation failed with mistake code: (0x80070643), Fatal error during installation. ------------------------------------------------------------------------------

  This is what I did:

  one. Installed VS2008 Team Arrangement Exam Edition using MSDN Deejay 4403.

  2. Tried to install VS2008 SP1 using MSDN disk 4603.01 - failed

  3. Uninstalled Remote Debugger, per: http://world wide web.pieterdebruin.internet/2009/02/01/VisualStudio2008ServicePack1InstallationErrorOnX64.aspx

  three. Tried to install VS2008 SP1 using bootstrapper, per like issue in the forums:

  http://social.msdn.microsoft.com/Forums/en/vssetup/thread/a536932f-fac0-4cb9-a4e7-aa00b78e7b3f

  This failed as well with the same mistake.

  4.  I uninstalled VS2008 using UninstallTool.exe

  5. Reinstalled VS2008 using MSDN Deejay 4403

  half dozen. Repeated attempts #ii & #3 to a higher place - nevertheless failed with aforementioned error.

  Any ideas anyone?

Answers

• Hi Joe,

  Give thanks you for your electronic mail.

  From the log file Microsoft Visual Studio 2008 SP1_20100319_153928163-Microsoft Visual Studio Team System 2008 Test Edition - ENU-MSP0.txt, I found some error snippet as the post-obit:

  MSI (s) (B0:88) [15:48:23:855]: Executing op: ComponentRegister(ComponentId={4633C17C-4BFC-4BE9-9379-071EA5D11841},KeyPath=C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\1033\Microsoft.VisualStudioUI.dll,Land=3,,Deejay=i,SharedDllRefCount=0,BinaryType=0)
  MSI (s) (B0:88) [15:48:23:858]: WIN64DUALFOLDERS: Substitution in 'C:\Program Files (x86)\Microsoft Visual Studio ix.0\Common7\IDE\1033\Microsoft.VisualStudioUI.dll' folder had been blocked by the 1 mask statement (the folder pair's iSwapAttrib member = 0).
  MSI (s) (B0:88) [fifteen:48:23:858]: Executing op: ComponentRegister(ComponentId={9987F81F-9487-48C6-BADD-7D7712F75088},KeyPath=<\Microsoft.VisualStudio.Designer.Interfaces,version="ane.0.5000.0",publicKeyToken="b03f5f7f11d50a3a",fileVersion="1.1.4322.573",culture="neutral",Country=3,,Deejay=1,SharedDllRefCount=0,BinaryType=0)
  MSI (s) (B0:88) [fifteen:48:23:863]: Verifying accessibility of file: microsoft.visualstudio.designer.interfaces.dll
  MSI (southward) (B0:88) [fifteen:48:23:864]: Using source file security for destination.
  MSI (south) (B0:88) [15:48:23:864]: Note: ane: 1310 2: 5 3: C:\Config.Msi\5489d1.rbf
  MSI (s) (B0:88) [15:48:23:894]: Product: Microsoft Visual Studio Team System 2008 Examination Edition - ENU -- Error 1310.Error writing to file: C:\Config.Msi\5489d1.rbf. System mistake 5.  Verify that you take access to that directory.

  Based on the fault message, it seems that the installation was blocked since the rights is not enough for accessing the specific file or folder.

  Please try using the SubInACL tool to repair file and registry permissions http://blogs.msdn.com/astebner/archive/2006/09/04/739820.aspx
  SubInACL tool is most useful when a setup package fails with error lawmaking 5 or 0x5 or 0x80070005.  All of these error codes hateful Access Denied, and this blazon of mistake code is often acquired by missing ACLs for the Administrators group or the built-in Arrangement account.

  If it doesn't work, you tin try to proceed your organization upwardly to appointment to see if that resets any of the permissions on your organisation and helps fix any of these errors.

  Hope this helps! If you have any business concern, please feel free to allow me know.

  Best regards,
  Yichun Chen
  MSDN Subscriber Support in Forum
  If y'all have whatsoever feedback on our back up, please contact msdnmg@microsoft.com

  ---

  Please recall to mark the replies as answers if they assist and unmark them if they provide no assistance.
  Welcome to the All-In-One Code Framework! If you have any feedback, please tell usa.

  • Marked as reply by Thursday, Apr 1, 2010 3:16 AM

• Thank you for the ideas - but that did not work either.  I tried to reinstall later setting the permissions on the Config.msi equally you specified, and I also tried reinstalling after deleting the config.msi directory.  In both cases the installation failed with the same fault as before.  It appears as if the c:\config.msi\ directory is recreated during each install attempt.  The permissions on that binder indicate that the administrator account (of which my user is a member) has full command of that directory and should be able to write to that directory.  It seems like during the installation, the rbf files which cannot be written to are somehow set either as read-only or gear up with the wrong permissions in spite of the permissions I assault the parent directory prior to installation.

  I'd like to thank everyone for trying to help me out - only after 10+ attempts to install VS2008 SP1 on this machine, I take determined that it will be easier to buy a new difficult bulldoze, perform a make clean install Windows vii from scratch and try again.  At this betoken I am hoping that something is simply wrong with the registry and/or various system files, and that a clean install will fix it.  Interestingly, when I was running Windows 7 RC on this machine, that SP1 installed fine and so.  It'south only after I did the make clean install of Windows 7 RTM that I had the bug.  Hopefully a 'new' clean install will let this work.  I remember I'll install VStudio and SP1 earlier anything else this time.

  Fortunately, I have ii other machines which took SP1 fine that I can work from in the acting.

  Once this is complete (hopefully I can go to this past mid-April) I will post one more than time to permit everyone know the terminal outcome.

  Thanks once again for all the help, and to anyone from the future and are reading this trying to troubleshoot the same problems, I wish you the best of luck!

  • Marked as answer by YiChun Chen Tuesday, March xxx, 2010 5:14 AM

• Hullo Joe,

  Thank you for your reply.

  I'd similar to thank anybody for trying to aid me out - but after ten+ attempts to install VS2008 SP1 on this machine, I take determined that it volition be easier to buy a new hard bulldoze, perform a clean install Windows vii from scratch and endeavour over again.  At this bespeak I am hoping that something is simply wrong with the registry and/or diverse organization files, and that a make clean install volition gear up it.  Interestingly, when I was running Windows seven RC on this car, that SP1 installed fine then.  It'south only later I did the clean install of Windows 7 RTM that I had the bug.  Hopefully a 'new' make clean install will let this work.  I recall I'll install VStudio and SP1 before annihilation else this fourth dimension.
  

  Firstly, performing the make clean install of Windows 7 to start from scratch could be helpful for the scenario that you came beyond. Then install Visual Studio 2008 and Visual Studio 2008 SP1 in order.
  Before the installation, please update your OS and ensure that you lot install VS2008 with Administrator Privilege.
  During the installation, you might check the installation tips mentioned here: http://social.msdn.microsoft.com/forums/en-United states of america/vssetup/thread/60f71a54-506e-4c70-be98-e993ce6d1ddf/ to make the installation smooth.

  I've marked your reply as reply. If you have any further concern, we can continue our word here. I'm willing to help you on that!

  The last but not the least, thank you for your patience and kindly sharing of installation experience advanced. I hope that our discussion here will benefit other community members as well.

  Wait forward to your adept news. Have a overnice 24-hour interval!

  Best regards,
  Yichun Chen
  MSDN Subscriber Support in Forum
  If you have any feedback on our support, delight contact msdnmg@microsoft.com

  ---

  Please recollect to marking the replies equally answers if they aid and unmark them if they provide no help.
  Welcome to the All-In-One Code Framework! If you have any feedback, please tell united states of america.

  • Marked as reply by YiChun Chen Thursday, Apr ane, 2010 3:15 AM

• Incidentally,  I had the Verbal aforementioned trouble on this car occur again - just this time it was when I was trying to install Office 2010.  I would go a number of errors where the installation process could not write a file to c:\config.msi.  The culprit turned out to exist iDrive - an automated backup program which I have installed on my PC.

  And so information technology may be possible that iDrive was besides causing the VS2008 installation to fail.  IDrive was installed during each installation failure.  IDrive was Not installed when I sucessfully installed VS2008.  Please note - if yous use iDrive, you may exist able to simply plow off the iDriveE Service, practice your install, and then turn it dorsum on.  Information technology worked for me on the Office 2010 install.

  • Marked as answer by YiChun Chen Friday, Apr xxx, 2010 8:18 AM

daughertyharioned49.blogspot.com

Source: https://social.msdn.microsoft.com/Forums/vstudio/en-US/4720b9d1-7398-40b4-9418-c5214207f599/vs2008-sp1-install-fail-on-win7-rtm-ultimate-x64?forum=vssetup

Share this post