How to fix "the setup for this installation of Visual Studio is not complete"
Asked Answered
F

12

79

I have been using Visual Studio 2017 for several months on a development machine. This morning it says says setup incomplete. Am I missing something?

enter image description here

Fireboard answered 5/5, 2018 at 2:31 Comment(1)
For me running the installer as admin and reparing it worked.Schoolbag
B
22

VS 2017 (15.6.6) was fine for me on Friday 6/1/18 on Windows 10, but same issue as OP today after a restart.

As suggested by the dialog and Retired Ninja, I ran the Visual Studio Installer (to 15.7.3 after updating VS Installer) and that fixed it.

Note that the 15.7.3 update was a 7.73 GB download. Your download size may vary.

Bateau answered 4/6, 2018 at 18:52 Comment(0)
P
60

In this case you need to go to Control Panel => Programs and Features and choose Visual Studio and update it.

Pigment answered 15/5, 2019 at 20:11 Comment(1)
the best solution, thanks +1 voteArchean
B
23

This has happened to me for the last 3 upgrades in Visual Studio Enterprise 2017 (now again on upgrade to 15.9.21). The fastest fix (and I'm not sure why) is simple and doesn't bomb your settings or take for ever.

  1. In the Visual Studio Installer, click on Modify.

  2. Click "Modify" on the bottom right corner. Yes it says "Total space required 0 KB". Yes you didn't really change anything.

  3. It will then act like it is downloading something. (not sure what)

  4. It will then act like it is installing something. (again, not sure what)

  5. Open Visual Studio 2017 and it works.

Backstage answered 11/3, 2020 at 12:54 Comment(3)
Just to follow up, it seems like every update after this occurs still today I get the same occurrence stating the "Setup not complete".Backstage
We have seen this problem adho. While the cause is still not know. At least this was the best fix in our instance it did not involve any large download and resulted the issue in less than 1 minute. Many thanks.Aspergillosis
This answer is great as it does not require updating VS. Currently 17.4 has issues with older .NET versions and so sticking to the installed version is important. For me I needed to actually add a new feature, so I installed the TypeScript SDK, which is only 17MB.Sibship
B
22

VS 2017 (15.6.6) was fine for me on Friday 6/1/18 on Windows 10, but same issue as OP today after a restart.

As suggested by the dialog and Retired Ninja, I ran the Visual Studio Installer (to 15.7.3 after updating VS Installer) and that fixed it.

Note that the 15.7.3 update was a 7.73 GB download. Your download size may vary.

Bateau answered 4/6, 2018 at 18:52 Comment(0)
A
11

If you have an offline installation like me and can't simply re-run the Visual Studio Installer you can edit devenv.isolation.ini and change the last line to read SetupFinished=true. It will detect your trickery and complain, but at least it will launch again.

Edit: I ended up getting the Visual Studio Installer to fix the issue after choosing the "Download then Install" option. Maybe I was too impatient when I initially stopped the update? My above answer is useful when you need to get work done that isn't affected by the broken features, but you will likely encounter problems later on.

Algar answered 7/1, 2019 at 23:11 Comment(2)
Also adding SetupResult=1 into the file will remove any warnings. Hack solution, but might work as a final resort.Triptych
It worked by updating SetupFinished=trueManufactory
H
8

just had the same problem (without any reason with) vs 2019 prof, after googling and reading on that topic, just went to vsix, looked for some individual component to install/uninstall, randomly picked cloud explorer, uninstalled it and some dependent components and VS 2019 prof started normally

decided to leave this here. may be it helps somebody

Hordein answered 23/4, 2019 at 9:13 Comment(1)
This seems to just repeat the existing answers.Grayson
S
6

In my case did following steps:

  1. Clear temp files (you can %temp% in run command and Shift+Delete files)

  2. Restart your computer

  3. Open visual studio it will work properly.

Update: Faced problem again after couple of days, This time I go to C:\Program Files (x86)\Microsoft Visual Studio\Installer.

  • Click on retry.
  • Select one more feature which I had already installed on my Visual Studio
  • Click on modified and after installation it worked again.
Shackleton answered 1/3, 2019 at 14:17 Comment(0)
S
1

This happened to me after I canceled a plugin update.

I solved by going to this site that has the latest update of Visual Studio.

https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes

I downloaded and upgraded it.

After that, Visual Studio worked.

If your VS is already upgraded, there´s an option to "repair" on the installer.

Sennight answered 20/3, 2019 at 10:3 Comment(1)
Just a side note for the above which I was annoyed about in this scenario. IF you do a "repair" on visual studio, you will have to reapply your settings as it may reset things like "Show Output window when build starts", and "Line Numbers" will be reset.Backstage
F
1

For this problem, goto uninstall screen in control panel right-click visual studio and select option change, Installer page will open now, In that window without changing anything click modify. it will solve the problem. I'm using VS Professional 2017

Fizzy answered 1/9, 2019 at 16:18 Comment(1)
I did this and it gave me the option to repair whihc then restarted the installer.Funeral
B
0

I was using Vs 2019 professional 16.6 and happened to me this issue one morning. I modified the installation by adding Azure Development tools even though I was not using it. This fixed the issue.

Barretter answered 31/5, 2020 at 12:4 Comment(0)
S
0

Check for updates for Visual Studio Installer. If there are updates available, install them. If not, repair the installation.

Samurai answered 23/12, 2023 at 13:12 Comment(0)
S
0

Run the VS installer exe, add or remove any component, then this issue may be fixed. Looks like the installer re-running process fix this issue.

Shontashoo answered 19/2 at 7:30 Comment(0)
C
0

After everything else I tried failed, I was able to correct this in VS 2022, by running the VS installer, then choosing Modify. Once there, I switched to the "Individual Components" tab and checked a component I didn't have installed (You may also be able to remove a component that you no longer need). Once that install completed, I was able to launch VS 2022 again. After the successful launch, you can remove the added component, if you don't need it.

Chump answered 1/7 at 16:46 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.