Download Vs_setup.msi For Visual Studio 2010
Some users are reporting that when installing Visual Studio 2010 SP1 they are prompted for MSI files as shown in the following example screenshot. These prompts for source are most common during rollback on failed install attempts and uninstall since original RTM files need to be put back on the machine and may not have been cached by Windows Installer.
May 24, 2010 Visual Studio 2010 Web Deployment Projects provide additional functionality to build and deploy Web sites and Web.
This includes, but is not limited to, the following MSI files. vsintshellenu.msi.
vssetup.msi I will update this list of files customers are commonly seeing as I’m made aware. If you are seeing this with other MSI files when installing VS2010 SP1, please comment below. How to work around this issue The solution varies depending on what you are being prompted for.
I will update this entry with common prompt issues for VS2010 SP1 as I’m made aware. If you’re running into this issue with other MSI files when installing VS2010 SP1, please comment below. Vsintshellenu.msi This workaround also may apply to any other language for the, and the instructions are similar for through the download location and file names will be different. Download for the language required, as described by in the file name required (ex: vsintShell enu.msi is for English). Open a command prompt (you can elevate when opening it now, or accept the prompt later when extracting below).
Run the comnand: vsintshell.exe /extract:”%TEMP% vsintshell”. Change directories or browse to the%TEMP% vsintshell folder: cd “%TEMP% vsintshell”. Rename the MSI file name as required by the prompt: rename vssetup.msi vsintshellenu.msi. Return to the prompt dialog, click the Browse button, and type the following into the File name: text box:%TEMP% vsintshell. Select vsintshellenu.msi (the file name must match) and click Open to continue. Back in the prompt dialog, click OK to continue.
Vssetup.msi If the title of the source prompt dialog contains “Express”, please see section 2.2.5 in the; otherwise, the following instructions should help you provide the right source and continue installation. Locate your original installation media for the product and language listed in the source prompt dialog caption. If the name of the language is cut off, the language the dialog text is displayed in should help identify the proper source.
Insert or attach your original installation media or network location for the product referenced in the caption. Return to the prompt dialog, click the Browse button, and browse to the root of the installation media above. Select vssetup.msi (the file name must match) and click Open to continue.
Back in the prompt dialog, click OK to continue. Description of the issue In general, during patch install occur because a file installed by a product is missing or in an unexpected state. Requires the original source to get these files. If it can’t find it automatically (for example, the original media isn’t in the drive or the previous network location), Windows Installer prompts the user for this source to continue.
Updated (3/16/2011): Added description for vssetup.msi, as well as a note that these prompts are most common during rollback or uninstall. @Michael Bate, Silverlight is installed by default with several SKUs, but it seems what you're being prompted for is the SP1 package for Silverlight SDK. Reference the one that corresponds to the language(s) of Visual Studio 2010 you have installed, using the table below. For example, if you're installing SP1 on the English version of Visual Studio 2010, reference the silverlightsdk.msi file under the Silverlight41033 directory. LCID Name DisplayName —- —- ———– 1028 zh-TW Chinese (Taiwan) 1031 de-DE German (Germany) 1033 en-US English (United States) 1036 fr-FR French (France) 1040 it-IT Italian (Italy) 1041 ja-JP Japanese (Japan) 1042 ko-KR Korean (Korea) 1049 ru-RU Russian (Russia) 2052 zh-CN Chinese (People's Republic of China) 3082 es-ES Spanish (Spain). I submitted the following to Microsoft e-mail support: —————————————————————————————————————————————— I attempted to install VS2010 SP1, but it rolled back (Rolling back NDP40-KB2468871.exe).
Visual Studio 2010 Sp3 Download
I attempted this several times, read blogs, etc. I finally uninstalled VS 2010, and tried to start from scratch. With each attempt, I check option to send install experience to Microsoft. I have finally been able to reinstall VS 2010 Pro, but keep getting erros trying to install the Windows Phone Development tools, and the Jan 2011 Patch, and the VS10-KB2486994-x86.exe I am running Windows 7 Ultimate with all updates installed. I have been totally unable to work on my Windows Phone app for over a week. Can someone help me totally start VS 2010 over from scratch, and re-install the Windows 7 Dev Tools, and the Jan 2011 update?
And then, help me install VS 2010 SP1 I am attaching a word doc containing the error log I got when attempting VS 2010 SP1 installation which started all my problems. —————————————————————————————————————————————— Attempting to install VS 2010 SP1 and the various attempts to reinstall, uninstall of the SP, and the Windows Dev Tools, and finally the uninstall of VS 2010 Pro, and subsequent reinstall of everything has left my Windows Phone Development at a total standstill. Can anyone there help???? Thanks, Heath I did attempt to uninstall SP1, but was unsuccessful. I did manually uninstall VS 2010 by removing all instances of VS 2010 products ( – Thanks Aaron Stebner @ Microsoft.com) In all my attempts, I installed VS2010 from my user account with Admininstrator previleges, and it installed successfully. The I decided to try to install VS2010 SP1 by logging on as Administrator, and SP1 installed successfully.
I then logged onto my user account, and tried unsuccessfully to setup the Windows Phone Development Tools (and the January update) So I went through the whole uninstall process. Again This time I logged onto my local Administrator account, and installed as follows: Installed VS 2010 Installed Windows Phone Development tools – with the error, not all components were installed: could not install Silverlight for Windows Phone Toolkit. I downloaded the msi for that (Silverlight for Windows Phone Toolkit.msi) and installed that. Installed the January update (the 2 step process) Installed VS2010 SP1 -FINALLY SUCCESSFULLY! After a LONG and TEDIOUS process all is working as it was before I attempted my first installation of VS 2010 SP! Thanks Heath for you response, and I will be following you blog for all the great and helpful information.
This has to be THE. I started searching the web for the various.msi files that it was asking me for. But after a while i just gave up and hit cancel. I waited for 30 minutes for it to roll back not willing to kill the process since that would probably end up killing my existing installation. Now it's asking me for every MSI under the sun. Sql 2008 MSIs, F# MSIs dotfuscator, vsint, phone SDK, sharepoint. So now i have to sit here hitting cancel every few minutes.
Hi Heath, Here is a Log file for the install that keeps FAILING for 'RiaServices.msi'. I hope this helps. Martin (HCamper) over on IIS.net Forum Site has been helping me and directing me to various resources. I am very greatful for that and willing to help. Very Best Regards, Crysta Installation LogMessage Types: Errors Verbose Messages Message Details: Date Time © 2009 Microsoft Corporation. All rights reserved. Terms of Use.
I had the same problem with VS2010 Shell (Integrated), but the link to the redistributable didn't work (nor was it called vssetupenu.exe), neither did pointing to the root of the VS2010 installation media. I solved it by starting SQL Server 2012 setup, which extracted to a folder named with a large number on the root of my hard drive.
I copied this to another folder, then quit the setup, then pointed the VS2010 SP1 uninstall to the folder it was looking for in this copy. The uninstall then finished without error.
I've also got a lot of these prompt windows upon the rollback execution, from the ones specified in the article, to other ones already mentioned in the comments. Just to add to the list: Microsoft Visual Studio Team Explorer – ENU – vssetup.msi. I've installed directly from the iso, as mounted by a software application to the effect. It took about 3.5 hrs, prompting several times for these.msi files, and then the execution finished on a fatal error. Still the application asked to reboot my PC.
Gonna do that now. Hi, I just posted something here but it doesn’t look like it has come through successfully. You say that I need to look at the attached readme file (2.2.5) if you are uninstalling it for C# Express (the vssetup.msi file). There are a few problems with this file.
The syntax for Step 5 should be: cd /d d:vcsexpress. I am however having a problem with Step 7, the syntax currently is: ixpvcs.exe /x:'%TEMP%ixpvcs'. This is wrong though, as ixpvcs.exe is a file name, not a command. Am I also right in thinking that x: should be c: as I don’t have an x drive??? Please can someone correct/help me on this? HI, Could you help me for god sakes i dont know more what to do.
In my case i am stuck at the same screen but with this error VSsetup.msi 'appdatalocaltempsit21278.tmp' I have tried copy the content of DVD image to desktop, not worked, tried to install from inside this folder.same error. What am i doing (or not) wrong, why this is happening anyways? I am sorry but i am not so good at this commands that you mentioned could you explain where do i have to type it if this solution applies to me as well.
For those arriving from Goo–sorry, Bing: What fixed it for me was this amazingly useful, hard-to-find utility: I stumbled across it in a non-MS forum after pulling out half my hair. Run the fix-it and choose 'I'm having trouble installing a program'. Choose whichever item the install is choking on. In my case, it was Visual Studio 2010 Tools for Office Runtime, aka vstor40x64.msi. After the fix runs, try installing SP1 for VS2010 again. That component should now succeed.
You may need to repeat for other components, but in my case it was just the one. Microsoft, please keep posts like this up-to-date! Not all of us get to run the latest and greatest Visual Studio; there are these things called legacy systems. The Internet is often our only source for answers. We shouldn't have to stumble across them in a third-party forum.