Visualstudio-docs: Install error on Visual Studio 2019 - Found setup instance but not in launchable state

[leniel]

These are the last lines of the log:

Found setup instance 883a9c0e but not in launchable state.
Install Error : System.InvalidOperationException: Cannot find setup engine instance.

I managed to install it by installing "Visual Studio extension development" workload as suggested here: https://stackoverflow.com/a/56001724/114029.

If "Visual Studio extension development" is necessary... it should be mentioned @ the documentation.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: eee67c1d-5856-93e0-e2d3-e9551436aabc
• Version Independent ID: b756aa96-bbb1-40e8-34ca-97f9939bf7e9
• Content: Install FxCop analyzers - Visual Studio
• Content Source: docs/code-quality/install-fxcop-analyzers.md
• Product: visual-studio-windows
• Technology: vs-ide-code-analysis
• GitHub Login: @Mikejo5000
• Microsoft Alias: mikejo

[Mikejo5000]

@leniel For context, you were trying to install the analyzers using VSIX, and you ran into this issue?

[leniel]

@Mikejo5000 exactly... using the VSIX package.

[Mikejo5000]

@mikadumont Mika, do you know whether the "Visual Studio extension development" workload is required to install the analyzers using the VSIX? If so, I can update this.

[Mikejo5000]

I tested this (no VS extension development workload installed), but no repro. Seems to have installed OK. Likely a product issue.

[Gopichandar]

Im having the similar issue when I tried to install "ML.NET Model builder" into my VS2019 community Edition 16.4.2

[mavasani]

Note that we are soon planning to deprecate Microsoft Code Analysis VS2019 VSIX (aka FxCop analyzers VSIX): https://github.com/dotnet/roslyn-analyzers/issues/3314. It is strongly recommended to install the analyzers through the NuGet package right now.

[msebolt]

Closing this issue now, if problems persist please comment below to re-open the issue.

Also consider using the Report a problem or Suggest a feature options in Visual Studio community where feedback can be solicited directly from the product team.

[ManniAT]

I had the same Issue with VS2017 - "PowerShell Tools for VS" and "Redgate SQL Change Automation" got an update today - and didn't install with this error message.
I uninstalled the feature "VS-Extension Developement workload" - and reinstalled it - after that it worked.