Update blew away VS2017

Phil Deibel reported May 23, 2017 at 11:02 PM

Show comments 6

Add comment

Raja Rajarethinam [MSFT] May 24, 2017 at 12:48 AM

Phil Deibel May 25, 2017 at 11:02 AM

dd-setup-20170524165035-errors.log (14.6 kB)

Joseph Aug 18, 2017 at 03:23 PM

Aniceto Liwanag Jr. Aug 31, 2017 at 01:22 AM

Matt Cavallari [MSFT] Sep 13, 2017 at 10:48 PM

Phil Deibel Sep 14, 2017 at 08:16 PM Matt Cavallari [MSFT]

Add comment

Any update on this issue? I still can not re-install my VS 2017.

Add comment

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

Add comment

Phil Deibel Aug 31, 2017 at 09:33 PM

Preston, David Dec 13, 2017 at 03:47 PM

Roi Chen [MSFT] Dec 15, 2017 at 06:08 AM Preston, David

Preston, David Dec 15, 2017 at 01:57 PM Roi Chen [MSFT]

Add comment

This issue has been fixed and is now available in our latest update. You can download the update via the in-product notification or from here: https://www.visualstudio.com/vs/ Thanks to all who provided feedback and votes for this problem.

Add comment

Phil Deibel Dec 15, 2017 at 02:14 PM

Preston, David Dec 15, 2017 at 03:16 PM Phil Deibel

Add comment

Developer Community

Get help from our community supported forum

Update blew away VS2017

Add comment

Solutions

Add comment

Add comment

Add comment

Developer Community

Get help from our community supported forum

Update blew away VS2017

Add comment

Solutions

Solution

Add comment

Solution

Add comment

Solution

Add comment

Related Problems