"Unknown Error" when launching Visual Studio 2017 Community after installation

Visual StudioVisual Studio-2017

Visual Studio Problem Overview


I am getting an "Unknown Error" (shown below) alert when I try to launch Visual Studio 2017 Community after successful installation.

> enter image description here

UPDATE: After Force uninstall & reinstallation

>enter image description here

Visual Studio Solutions


Solution 1 - Visual Studio

remove this folder (or similar):

>%LocalAppData%\Microsoft\VisualStudio\15.0_db2a872f

  • folder name 15.0_db2a872f could be different in your machine eg. 15.0_XXXXXXX
  • found in the vs startup log that processing of Progression_NativePackage_Component_x86.pkgdef bailed out, indicating an inconsistent extension installation

Solution 2 - Visual Studio

I only had to rename(if you wan't to back it up)/delete the following file:

>privateregistry.bin > >or > >privateregistry.user.bin > >depending on Visual Studio version. > >%LocalAppData%\Microsoft\VisualStudio\15.0_\privateregistry.bin > >%LocalAppData%\Microsoft\VisualStudio\15.0_\privateregistry.user.bin

After restarting Visual Studio 2017 you may need to activate Tools or Extensions again.

Solution 3 - Visual Studio

Please check if the machine has Symantec Workspace Virtualization Agent installed. Removing the product from add\remove programs fixed the unknown error while launching VS 2017.

Here is the detail of the product. Product code: {785F9A4D-D113-43B3-AA1D-77AD777F0A2F} Package code: {32DB9767-3EF7-465A-ADF2-7ECFD25ABC12} Install date: 2015.05.21 Version: 6.4.1266 Publisher: Symantec

Solution 4 - Visual Studio

I ran it as Admin and it somehow booted up just fine after that. I was getting the same error even after making sure that all packages and SDKs were installed until I ran it as admin.

Basically, just go to the shortcut in Start or to the .exe in the files, then right click it and run as Admin or change it in the properties. Tbh, it seems like a temporary fix and I'd actually like to know the real source of the problem, but for now, I don't have to reinstall and repair over and over.

Same version: Visual Studio Community 2017 installed using the launcher

Solution 5 - Visual Studio

I have a same problem after update VS 2017 Enterprise to the build 26228.9.

Repair installation doesn't fix anything. Still I got "Unknown error" message immediately after start VS2017.

Fixing is possible by removing this folder:

"C:\Users\USER_NAME\AppData\Local\Microsoft\VisualStudio\15.0_xxxxxxx"

where xxxxxxxx is some hexadecimal number.

BUT AFTER THAT YOU LOSE ALL SETTINGS that you done on your installation of VS 2017 (except product license key appliance).

Sorry that I must say this, but:

Maybe will be better stuck on the VS2015 for now. Because MS still not has really fully functional build of VS for now.

VS 2017 is still ready for first experimenting only and not for real work.

It is same story like a was when VS2015 has been published. (after several days stop working).

Solution 6 - Visual Studio

I fixed it the same way as niclar by deleting folder 15_.*. It does however appear that renaming privateregistry.bin has same effect with less trouble.

As mentioned by Torbjorn, ReSharper and other Extensions can mess up, however no reinstall required.

Merely go to Tools > Extensions and Updates... > Scroll through list of Installed Extensions > Enable those that should be enabled.

Solution 7 - Visual Studio

I have a side by side installation with VS2015. After opening and closing VS2015 once, VS2017 ist starting again normally. Strange but helped in my case.

Solution 8 - Visual Studio

I only needed to delete or rename ApplicationPrivateSettings.lock within C:\users{your username}\AppData\Local\Microsoft\VisualStudio\15.0_c31ecfb9 folder.

Solution 9 - Visual Studio

I was experiencing this issue with Visual Studio Professional when not running as administrator. (It worked Ok as administrator) I used Niclar's solution of deleting the folders.

Solution 10 - Visual Studio

I found same issue after installing the extension and removing the folder "C:\Users\USER_NAME\AppData\Local\Microsoft\VisualStudio\15.0_xxxxxxx" solved my problem.

Solution 11 - Visual Studio

you can rename the Solution Name and reopen the Project it solved for me after repairing the VS Installation

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionAjay JadhavView Question on Stackoverflow
Solution 1 - Visual StudioniclarView Answer on Stackoverflow
Solution 2 - Visual StudioBruno BieriView Answer on Stackoverflow
Solution 3 - Visual Studiorathish rkView Answer on Stackoverflow
Solution 4 - Visual StudioSorralView Answer on Stackoverflow
Solution 5 - Visual StudioPokeView Answer on Stackoverflow
Solution 6 - Visual StudioEmil L.View Answer on Stackoverflow
Solution 7 - Visual StudiomartinossView Answer on Stackoverflow
Solution 8 - Visual StudioNick PainterView Answer on Stackoverflow
Solution 9 - Visual StudioKirstenView Answer on Stackoverflow
Solution 10 - Visual StudioRoh8SthaView Answer on Stackoverflow
Solution 11 - Visual StudioMohamed FarragView Answer on Stackoverflow