none
Visual Studio 2017 Extensions and Update "cannot find setup engine instance".

    Question

  • After a new install of VS 2017, Tools->Extensions and Updates results in an error dialog "cannot find setup engine instance".

    At this point in time, VS 2017 is pretty unusable because of this.

    Monday, March 13, 2017 12:35 PM

All replies

  • Hi Tyler, 

    Which Edition of VS 2017 do you use ? 

    I've checked it in my VS 2017 community and it works fine. 

    But it seems some other people are also facing this issue, and someone has already submitted a report on develop community: 

    https://developercommunity.visualstudio.com/content/problem/25702/cannot-find-setup-engine-instance.html

    I think the engineers from Microsoft will evaluate it seriously and give us an response.

    Best regards,

    Fletch 



    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, March 14, 2017 4:07 AM
  • Hi all, I found out that if you delete the visualstudio folder in the ProgramData\Microsoft  folder you will get this error, I moved mine to a separate drive to save space and I got the error, after I restored it everything went back to normal
    Wednesday, March 15, 2017 9:12 PM
  • Is there a way to fix this without reinstalling it?
    Thursday, March 16, 2017 4:14 AM
  • Hi friend,

    Maybe you could refer to the following link with David Walker's reply.

    https://developercommunity.visualstudio.com/content/problem/3379/install-failed-and-cant-reinstal.html

    Sincerely,

    Oscar


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, March 16, 2017 7:59 AM
    Moderator
  • Hi Tyler,

    Could the reply from Duke and Oscar help you out?

    And there is a solution to this report now :

    https://developercommunity.visualstudio.com/content/problem/25702/cannot-find-setup-engine-instance.html

    Best regards,

    Fletch 


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 17, 2017 1:33 AM
  • Hi friend,

    Here is the suggestion given by Visual Studio Team:

       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 RTW

    Reference link:

    https://developercommunity.visualstudio.com/content/problem/28439/cannot-find-setup-engine-instance-1.html

    Best regards,

    Fletch


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 17, 2017 5:28 AM
  • Hi all, I found out that if you delete the visualstudio folder in the ProgramData\Microsoft  folder you will get this error, I moved mine to a separate drive to save space and I got the error, after I restored it everything went back to normal
    Hi. In my case, I only need to restore the '_Instances' folder (C:\ProgramData\Microsoft\VisualStudio\Packages_Instances) and the problem has gone.
    Saturday, March 25, 2017 1:52 AM
  • This "solution" will likely lead to a full reinstall, just like the comment on the referenced link said.
    Wednesday, April 25, 2018 9:11 PM
  • That first suggestion basically just uninstalls Visual Studio 2017 without any warning btw

    good job

    Sunday, May 13, 2018 3:16 PM
  • I should have read your post.   My install is now completely hosed.  :-(  

    straightener

    Monday, May 21, 2018 1:15 PM
  • This uninstalls visual studio. wtf mate. I don't have time to uninstall and reinstall visual studio when i have a product to deliver. a little warning please.
    Thursday, June 7, 2018 7:34 AM
  • I had same problem with my recent clean VS2017 installation on Windows 10. I used following steps and it helped me:

    1. Go to "uninstall programs" list of apps in the settings.
    2. Select VS2017 and click modify.
    3. After the window with features pops up just click modify again. The whole process will take like one minute.
    4. After installer has finished its job it will prompt with restart. I've restarted my PC, and after that I didn't see that "cannot find setup engine instance" error any more.
    • Proposed as answer by James Esh Monday, August 20, 2018 6:14 PM
    Wednesday, June 20, 2018 7:45 PM
  • I had same problem with my recent clean VS2017 installation on Windows 10. I used following steps and it helped me:

    1. Go to "uninstall programs" list of apps in the settings.
    2. Select VS2017 and click modify.
    3. After the window with features pops up just click modify again. The whole process will take like one minute.
    4. After installer has finished its job it will prompt with restart. I've restarted my PC, and after that I didn't see that "cannot find setup engine instance" error any more.

    Hello,

    thanks a lot for this, I faced the same issue and following this procedure has solved it. Just a little difference : the installer didn't prompt to restart, and I didn't restart my PC.

    Regards.

    Steve R.

    Tuesday, September 25, 2018 7:06 AM
  • I had the same problem. But when I opened Visual Studio Installer it showed error during the update. I clicked "retry" and when the update was finished, the problem with extensions was fixed.
    Monday, October 1, 2018 4:39 PM
  • This is not a good solution, it is the same as uninstalling visual studio and reinstalling. 
    Monday, October 15, 2018 8:32 AM
  • Next time, I will google before launch  any tool :) I didn't expect that InstallCleanup -full, would completely remove visual studio from PC. 
    • Edited by ShinShil5 Wednesday, November 14, 2018 8:52 AM
    Wednesday, November 14, 2018 8:51 AM
  • It's amazing that in 99% of the online forums, people try to find new ways to say "just uninstall and reinstall".. In fact, in the last 20 years of working with Windows and other Microsoft products, there really is no support, just reinstall.. You could get as creative on the reply as you want, but I wish the forums would go away completely, replaced by a banner that says "To fix your problem, you must uninstall and reinstall. Sorry.".

    I think the forums are there just to make people think if they search long enough, they can do something different. Even if they hack a file in to place and it works, you normally have to weed through about 1000 replies that talk about rebooting, reformatting windows, or reinstalling whatever product they are asking about.  Not your fault, just an observation.

    Dan Chase



    • Edited by Danny2004 Tuesday, November 20, 2018 2:57 AM
    Tuesday, November 20, 2018 2:56 AM
  • This seriously needs a proper warning of what exactly it's actually doing. Having people looking for solutions run something that simply uninstalls without it being obvious that that's what's happening is abusive and irresponsible.
    Sunday, January 13, 2019 2:54 AM