- 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
- Shortcuts - Some shortcut names still indicate Preview after a newer version is installed
0x80200010, 0x80072efe, or 0x80072ee7 - Connectivity issue during downloadThis error typically occurs when the Visual Studio installer experiences issues that affect your Internet connection during the download of required components. If you receive one of these error messages, try again to install Visual Studio after your Internet connection improves. If you continue to see this error, try the following methods:
- Install Visual Studio from a different source. For example, if you installed Visual Studio from VisualStudio.com or from the Microsoft Download Center, try downloading Visual Studio from MSDN.
- 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 MSDN site.
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, has locked a Visual Studio installation file at the same time that Visual Studio is 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, reference Solving setup errors by using the SubInACL tool on the MSDN site.
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 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 occur after warning about certificate updates is ignoredWhen you installed Visual Studio on Windows 7, you encountered the following warning:
- Ensure that you are on a computer that is connected to the internet.
In some cases, Visual Studio is able to programmatically retrieve and then apply the required certificate updates so that the affected features can be successfully installed.
- 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 setting should be Disabled.
Note We recommend that you contact your system administrator before you modify any group policy setting.
- If the above steps do not resolve the issue, you can also try to manually install the required certificate updates. For information on 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). Windows 8 and later versions of Windows have these certificate updates installed by default.
Shortcuts - Some shortcut names still indicate Preview after a newer version is installedIf you installed Visual Studio 2013 Preview and then installed a newer version of Visual Studio 2013 without first uninstalling Preview, some Visual Studio shortcut names are not correctly updated to indicate that a new version is installed. While the name is incorrect, the shortcuts correctly point to the newer Visual Studio installation, so it is not necessary to take any action. However, if you prefer to fix the shortcut names, you can try the following:
- Uninstall Visual Studio 2013. To uninstall, open Programs and Features (appwiz.cpl). From the Programs and Features window, right-click Visual Studio 2013 and select Change, and then click Uninstall.
- Manually delete any shortcuts that have been left behind.
- Open an elevated command prompt.
- At the command prompt, type the following command, and then press Enter:
rmdir /S "%PROGRAMDATA%\Microsoft\Windows\Start Menu\Programs\Microsoft Visual Studio 2013"
- Enter Y to confirm that you want to delete the folder and its contents.
- Reinstall the latest version of Visual Studio.
Or, you may post your Visual Studio installation log file to the Visual Studio Setup and Installation forum and Microsoft Community for further helps.
To do this, follow these steps:
- Download the Microsoft Visual Studio and .NET Framework Log Collection tool (collect.exe).
- Run the collect.exe tool from the directory where you saved the tool.
- The utility creates a compressed cabinet file of all the VS and .NET logs to %TEMP%\vslogs.cab.
- Post the vslogs.cab file with some descriptions of your issue to the forum.
Article ID: 2899270 - Last Review: Dec 24, 2014 - Revision: 1