Multiple Errors Installing Visual Studio 2015 Comm

Question

When installing Visual Studio 2015 Community Edition on Windows 10, using the web installer, everything runs fine, however, the following packages fail to install:

• Team Explorer for Visual Studio 2015 -> Fatal Error
• Microsoft NuGet - Visual Studio 2015 -> Package Failed
• Microsoft Visual Studio Connected Services -> Packages Failed
• Azure AD Authentication Connected Services -> Packages Failed
• Microsoft Azure Mobile Services Connected Service -> Package Failed
• Microsoft Azure Storage Connected Service -> Packages Failed
• Microsoft.VisualStudio.Office365 -> Package Failed

I have attempted a few work around including uninstalling every Visual Studio Version on my system, manually deleting the files in C:\ProgramData\Program Cache, and even gone as far as to uninstall my Antivirus (AVG) having attempted to disable it and see if that works before hand. I even ran the command fsutil behavior set SymlinkEvaluation L2L:1 L2R:1 R2L:1 R2R:1

I have even tried to use the ISO but ran into the same issue.

Since I don't use either Azure or Team Explorer any solutions which mean I won't have access to them will suffice.

The log file that was generated by the Installer can be found here as it was over 65,000 characters long (just scroll to the bottom for all the fun).

Answer 1

This was killing me as well, I must have re-installed visual studios a thousand times before Stack Overflow helped me! First is began with a Windows update problem While installing Visual Studio 2015 the Update flagged me that it needed - the update KB2919355. Went to the Windows update and saw several failed updates. No matter how I tried did not work. The Error code that were cited was 80070543 did some research found nothing worked until I encountered this advice http://www.dell.com/support/article/us/en/04/SLN293803/en Having followed those instructions did the Windows update again and it worked. Went back to to do the Visual Studios update got the same error again! So I decided to research KB2919355 and was frustrated until I found this site http://www.eightforums.com/windows-updates-activation/45441-update-kb2919355-finally-successful-after-multiple-fails.html

followed the instruction precisely about loading other updates and they worked. KB2919355 was finally updated so I tried again and a different error came up involving language packs. “Fatal Installation error”. After going through a series of frustrating reinstallations, uninstallations light broke through of the advice of that came this (the above) Stack Overflow entry “repairing the C++ Redistributables” which involves: Going to Start -> Control Panel -> Programs and Features Right mouse-clicks on each the redistributables (from the bottom up) and click repair for all. If any ask for a “Restart” do it immediately right then and there! Then I did the Visual Studio installations….finally after days and days of trying….it worked.

Answer 2

Also you can find log files in %Temp% folder about exact problem, in my case the problem was with symlinks.

if with "fsutil behavior query SymlinkEvaluation" you get message .."is currently controlled by group policy" check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Filesystems\NTFS or simply search throug registry for "Symlink".

Answer 3

If no other option in this thread works, you can try the steps given in this guide (see below): https://blogs.msdn.microsoft.com/heaths/2015/07/14/how-to-install-visual-studio-to-another-directory-when-a-pre-release-is-installed/

1. Download and install http://psmsi.codeplex.com (Note: new site https://github.com/heaths/psmsi) These are general-purpose PowerShell cmdlets I created for all sorts of development and troubleshooting operations for Windows Installer-based installs. You do not need to elevate to install them, though if you pre-elevate you can install them per-machine (by default they are per-user).

2. Open an elevated PowerShell command prompt and run the following to discover which products have installed the key shared component:

   get-msicomponentinfo '{777CBCAC-12AB-4A57-A753-4A7D23B484D3}' | get-msiproductinfo

3. If you’re fine with uninstalling all the listed products (especially given that you’re probably going to install RTM next), run the following:

   get-msicomponentinfo '{777CBCAC-12AB-4A57-A753-4A7D23B484D3}' | get-msiproductinfo | uninstall-msiproduct -properties IGNOREDEPENDENCIES=ALL

Personally, this worked for me. I forgot that I had some old files laying around on an old drive, which appearantly later on messed something up in the registry (I think..?). Anyway, with everything clean, it installed just fine!

Note: if you have issues with importing the PSMSI-tools in PowerShell, check this out: https://msdn.microsoft.com/en-us/library/dn568022.aspx

In summary, you may need to run the command Set-ExecutionPolicy RemoteSigned to be allowed to import the software.

Hope this helps someone in need!

Answer 4

I did the redistributable repair thing, but for me it worked after I installed Office365.

(for me it also was the last failing package on the list).

Answer 5

After the failed install you have to repair the 2015 vc redistributables and restart the visual studio installer.

The redistributable installer is messed up, it mixes up 64bit and 32bit dll's. You can check if you have this problem by looking at the vcruntime140.dll file size. Search your windows folder for vcruntime140 you should see 4 files (64 and 32 bit in both release & debug versions). If any files have the same size, you need to run a repair on the redistributable.

On my system the 32-bit dll is 83,3KB, the 64 bit is 86,6KB (release versions).