- Home /
- Visual Studio /
This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn more
Report an issue
in Visual Studio Installer or Visual Studio
This allows diagnostic information about the program to be included in your report
1. Installer or Visual Studio
2. Report a Problem
3. Type and Submit
Available on Visual Studio 2017, Installer, and newer releases
Would you like to know more?
Update blew away VS2017
Started VS2017 got notification of update. Started update. Installer required an update, in the middle or after installer update system rebooted. Upon reboot VS Installer (not Updater) Opened. Selected Install for Enterprise version (which is what I had installed). Got error message that couldn't install in non empty ...\Enterprise directory. Renamed directory to Enterprise-old, tried reinstall didn't complain about directory just failed. Uninstalled VS2017 from Programs and Features and deleted everything under ...\2017 directory (parent to \Enterprise). Downloaded the Install bootstrapper. Ran bootstrapper, brought up Installer screen, selected install Enterprise version, installation failed. Now reporting.
Thank you for your feedback!
Please run collect.exe from http://aka.ms/vscollect and attach your %temp%\vslogs.zip.
Looks like you might have deleted folders incorrectly (we are separately investigating why a restart caused you to lose reference to installed instance). Please follow the cleanup steps and install VS.
- See if you have this file on your machine: "%programfiles(x86)%\Microsoft Visual Studio\Installer\resources\app\layout\InstallCleanup.exe"
- If so, please launch it from an admin command prompt with a -full param:
InstallCleanup.exe -full
- If not, please manually delete the "%programfiles(x86)%\Microsoft Visual Studio\Installer” folder
- Relaunch the newly downloaded vs_enterprise.exe (or vs_professional.exe or vs_community.exe…)
- Allow the first step to install the installer
- Once the installer comes up and you can see workload choices (.net desktop and the like), close it
- Go launch the same InstallCleanup.exe to clean up old build of VS
- Then relaunch vs_enterprise.exe and install VS
dd-setup-20170524165035-errors.logThank you for your response. The requested vslogs.zip was included with the previous post. I executed the InstallCleanup application with the -full parm. I then executed the installer bootstrap and it installed the VS installer. I selected the workflows I was interested in and clicked the install button. The installation failed. (attached is the install error log). It then changed the install button to a modify button of which I clicked the modify button and the installation failed again. I unfortunately did not capture that log.
Unable to repair or uninstall as well. Resharper doesnt show anymore.
same here for Professional, got the notification to update, did that, then during the update, encountered the blue screen of death. laptop restarts, cannot open anymore the vs2017 and suggest to reinstall, trying to re install but got prompted: "Sorry, the installation failed. Please try again. Please help
Thank you for your feedback, and we are sorry to hear about the issue you are having. From digging through your issue, the root cause is because a file we use for managing your installations has become corrupted. In your case, it is empty but we have seen cases where the file can be incomplete as well. The Visual Studio installer engine has made changes to be more resilient to cases that cause this state to occur. Unfortunately, machines already in this state are forced to clean up their installations and apply a fresh Visual Studio installation.
Please follow the cleanup steps and retry your VS install
- See if you have this file on your machine: "%programfiles(x86)%\Microsoft Visual Studio\Installer\resources\app\layout\InstallCleanup.exe"
- If so, please launch it from an admin command prompt with a -full param:
InstallCleanup.exe -full
- If not, please manually delete the "%programfiles(x86)%\Microsoft Visual Studio\Installer” folder
- Relaunch the newly downloaded vs_enterprise.exe (or vs_professional.exe or vs_community.exe…)
- Allow the first step to install the installer
- Once the installer comes up and you can see workload choices (.net desktop and the like), close it
- Go launch the same InstallCleanup.exe to clean up old build of VS
- Then relaunch vs_enterprise.exe and install VS
Matt, Thanks for the reply, but your canned response is not the solution. I have done every step of your solution multiple times and it does not fix the problem. This problem is long overdue for a solution (almost 4 months). At the least tell me what has to be manually removed so that the install thinks it is completely brand new. I hate to think that I will have to say on 2015 to get my work done. Also I opened this issue and I can not change the status back from this incorrect fixed status.
Still the same problem. Tried what you suggested. (Notice same thing tried back on May 25th.) Same results.
I am not the only one having this issue. It has been 3 months and no resolution.
Matt, please read before copy/paste-ing a duplicate of your previous post, which as comments indicate, did not work.
Hi Preston, Can you create a new report by using Report A Problem in Visual Studio (It's on the Help Menu under Send Feedback) since this issue has been closed for a long time? Thank you for your patience.
Roi,
I opened a separate issue a couple of days ago. My issue turned out to be our security department. :)
https://developercommunity.visualstudio.com/content/problem/167249/packageidmicrosoftservicehubpackageactioninstallre-4.html
I am really upset with Microsoft Support. They provided no help in a solution to this problem, and only copy pasted instructions that didn't work. Then marking this issue as Fixed when it wasn't. I have tried to reinstall every new version since the issue first occurred back in May. Saying that it is fixed in the latest release is a cop-out when reality is that some of us can no longer install 2017.
Thank you Microsoft for yet another reason to move to other technologies.
Phil, I'm not a MS employee, but did have a very similar issue, which I pretty much figured out myself using the logs.
I noticed in the dd-setup log that you attached back on May 25, that it references a component that failed to install, which ultimately caused the whole install to fail...
Package 'Microsoft.VisualStudio.MinShell.Msi,version=15.0.26424.2' failed to install.
In this section of the log file, if you scroll past all of the impacted workloads/components stuff, you will see a reference to another log file that is specific to the "Microsoft.VisualStudio.MinShell" component...
Log C:\Users\Phil\AppData\Local\Temp\dd_setup_20170524165035_005_Microsoft.VisualStudio.MinShell.Msi.log
For my issue, the answer to why the install was failing was located in the second log file, which gave the specific name and location of a file that could not be created due to a security policy.
If you can locate and post this file, I will take a look at it for you.
There is also the section right after this that lists some additional information...
Details ... Return code: 1714 Return code details: The older version of vs_minshellmsi cannot be removed. Contact your technical support group.
The return code details tells me that the uninstall of the old version of the package is failing and preventing the install of the newer version. I haven't looked at it closely, but there is another post that specifically addresses this issue...
The older version of vs_minshellmsi cannot be removed
Hope this helps!
175 People are following this
