Visual Studio 2015 Community Nightmare

The nightmare hit me hard…


First I was unable to register ‘free’ ‘community’ edition – with error

we could not download a licence. please check your network connection or proxy settings.

After countless reinstalls from 2 different web installers provided on microsoft pages (sic!) and even installing it from iso image. I narrow the problem to be in wrong delegation setting in AD which end up being SAMBA4 bug and upgrade did help – The registration error message didn’t help with this, only adding “new account” yield at me about wrong delegation.

After successful registration and unlocking community version after 30days of trial use I hit another problem probably because I deleted one reg more than I should and installer was dumb enough to not recreate it (they need to improve installer or stop hide options in it)

'Code analysis package' package did not load correctly.

- and -

Project <name> could not be opened because the Microsoft Visual C# 2015 compiler could not be created. Please reinstall Visual Studio

I reinstall VS2015 more than few times even changing path, cleaning folder, regs. I end up digging thru forums/support pages to find those tips:

To uninstall the visual studio totally, we could try to use /uninstall /force command, it will remove the shared components, please take the following steps:

  1. Run installer (.exe) with /uninstall /force – those will clean alot more, first time I uninstall VS cleaner app found 11k files not deleted (sic!)“”
  2. Delete registry key (or rename it) HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0
  3. Delete %AppData%\Roaming\Microsoft\VisualStudio\ and %AppData%\Local\Microsoft\VisualStudio\14.0\ComponentModelCache

Only after this steps I was able to reinstall VS2015 with success and no more pop-up Errors.

4 thoughts on “Visual Studio 2015 Community Nightmare”

  1. 4 years later, same crap.
    Plenty of IDEs out there which you don’t spend half a day trying to simply login too. Never use Visual Studio to learn, because you’ll spend half the time trying to get it running.

  2. If your account is using multifactor authentication – disable it – then it will work. That was the case for me anyway and this was instructed from Microsoft technical support.

    1. Your probably right, but also if my memory sever me right, 2015 didn’t had those account things ‘yet’

Leave a Reply

Your email address will not be published. Required fields are marked *