- Setup fails and "BITS job failed" error message is logged when you install Visual Studio 2015 Update 1
- "-2147205120" error code occurs when you setup Visual Studio
- 0x80200010, 0x80072efe, or 0x80072ee7 - Connectivity issue during download
- 0x80070005 - Access denied
- 0x80070643 - Installation cache or ISO is corrupted
- 0x800713ec - .NET Framework installation is in progress
- Multiple feature installation errors occur after warning about certificate updates is ignored
- Error 1606 with a message that references a \\psf folder
- SQL packages may fail when the local administrator account does not have certain rights
- Invalid entries passed to /FilterFeatureSelectionTree and /InstallSelectableItems switch
0x80200010, 0x80072efe, or 0x80072ee7 - Connectivity issue during downloadThis error typically occurs when the Visual Studio installer experiences issues that are caused by your Internet connection during the download of required components. If you receive this error, try to install Visual Studio again after your Internet connection improves. If you continue to see this error, try one or more of the following methods:
- Install Visual Studio from a different source. For example, if you were installing Visual Studio from VisualStudio.com or from the Microsoft Download Center, try downloading Visual Studio from MSDN instead.
- Install Visual Studio by using the "layout" switch or an ISO file. For more information about how to do this, see Installing Visual Studio on the Microsoft Developer Network (MSDN) website.
0x80070005 - Access DeniedThis error occurs when Visual Studio cannot access one or more of the required installation files. This error may occur for any of the following reasons:
- An outside process, such as an antivirus or antimalware application, locked a Visual Studio installation file while Visual Studio was trying to install the file. To work around this issue, coordinate with your system administrator or other IT professional to make sure that Visual Studio files are not locked by these processes.
- The user who is trying to install Visual Studio does not have administrator credentials on the computer. To successfully install Visual Studio, you must be logged in as an administrator.
- Permissions on some registry hives can prevent Visual Studio from installing successfully. To resolve this issue, see Solving setup errors by using the SubInACL tool on the MSDN website.
0x80070643 - Installation cache or ISO is corruptedThis error typically occurs when a file that is related to the installation becomes corrupted. You may experience this error when you install Visual Studio by using an ISO or DVD that was burned from ISO. You may also experience this error during a repair of Visual Studio.
0x800713ec - .NET Framework installation is in progressThis error typically occurs when an installation of the .NET Framework that is separate from Visual Studio is already in progress. Because many components of the Visual Studio installer depend on the .NET Framework, an attempt to install the .NET Framework while Visual Studio is being installed can cause unexpected behavior.
To work around this issue, wait for the .NET Framework installer to finish before you install Visual Studio.
Multiple feature installation errors in Windows 7When you install Visual Studio on a Windows 7-based computer, you may be prompted for missing resources, such as a setup package. This error occurs most often in Windows 7, but it can occur in other operating systems.
You may also receive the following warning message:
If you then click Continue to proceed with the Visual Studio installation, you may encounter the "Unable to locate package source errors" message about errors that are not resolved through the Download packages from the internet option. When the Visual Studio installation is complete, you receive the following message:
You are also shown a list of multiple features that could not be installed because the system could find the specified files. To resolve the issue, try the following methods:
- Method 1: Make sure that you are on a computer that is connected to the Internet. In some cases, Visual Studio can programmatically retrieve and apply the required certificate updates so that the affected features can be successfully installed.
- Method 2: Check the Group Policy setting on your computer that controls automatic certificate updates. To check the setting, open the Group Policy Editor (gpedit.msc). From the Local Group Policy Editor, under Computer Configuration, expand Administrative Templates, expand Internet Communication Management, and then click Internet Communication settings. The setting that controls automatic certificate updates is Turn off Automatic Root Certificates Update. For Visual Studio to automatically retrieve and apply the required certificates, this option should be set to Disabled.
Note We recommend that you contact your system administrator before you change any Group Policy setting.
- Method 3: If Methods 1 and 2 do not resolve the issue, you can also try to manually install the required certificate updates. For information about how to obtain Windows update root certificates, see How to get a Root Certificate update for Windows.
Note This error applies only to Windows 7 Service Pack 1 (SP1). By default, Windows 8 and later versions of Windows have these certificate updates installed.
Error 1606 with a message that references a \\psf folderWhen you install Visual Studio on a Mac that's running Parallels, this may trigger error 1606 and generate a message that references a \\psf folder. To address this issue, go to http://kb.parallels.com/en/115026 (or the older http://kb.parallels.com/en/114310), and then reinstall the “Parallels Tools” integration piece that is specific to Macs that are running Parallels.
SQL packages may fail when the local administrator account does not have certain rightsWhen you install Visual Studio on a locked-down desktop, this may trigger errors for the SQL packages. These errors may occur if the domain administrator has removed rights from the local administrators account to tighten desktop security. For more information about how to diagnose and address these errors, see SQL Server installation fails if the Setup account does not have certain user rights.
Invalid entries passed to /FilterFeatureSelectionTree and /InstallSelectableItems switchWhen you install a Visual Studio 2015 update, and the setup fails or cancels out, and then you try to run the same Visual Studio 2015 Update installer again, you receive the following error messages:
Invalid entries passed to /InstallSelectableItems switch. For more details, please see the setup log
This issue occurs when the initial failed or canceled setup did not persist the latest feed.xml. The next time the Visual Studio Update installer runs, it tries to use the outdated feed.xml that it detects from earlier Visual Studio install sessions.
To work around this issue, run the command that resembles the following:
VS2015.3.exe /overridefeeduri <Path to feed.xml>
The path of feed.xml can be a web link from the following table. Or, you can download files from the web link and save the feed.xml to your local disk, and then the "Path to feed.xml" will be your local path.
Note The feed.xml is language specific. Therefore, please select the feed.xml that matches the language version of your Visual Studio. If you have multiple languages installed, please select the one that you used to install Visual Studio at first.
For example, if you have CHS Visual Studio installed on the computer, then the command line to use would be as following:
VS2015.3.exe /overridefeeduri http://go.microsoft.com/fwlink/?LinkID=564093&clcid=0x804
Or, if you download the feed.xml from http://go.microsoft.com/fwlink/?LinkID=564093&clcid=0x804 to your local disk at d:\VisualStudio\feed.xml, then the command line to use would be as follows:
VS2015.3.exe /overridefeeduri d:\VisualStudio\feed.xml
You may also post your Visual Studio installation log file to the Visual Studio Setup and Installation forum and Microsoft Community for more help. To do this, follow these steps:
- Download the Microsoft Visual Studio and .NET Framework Log Collection tool (Collect.exe).
- Run Collect.exe from the directory in which you saved the tool. The tool saves a compressed cabinet file of all the Visual Studio and .NET logs to %TEMP%\vslogs.cab.
- Post the Vslogs.cab file to the forum, together with some descriptions of your issue.