Set defaults for enterprise deployments of Visual Studio
You can set registry policies that affect the deployment of Visual Studio. These policies are global for the new installer and affect:
- Where some packages shared with other versions or instances are installed
- Where packages are cached
- Whether all packages are cached
You can set some of these policies using command-line options, set registry values on your machine, or even distribute them using Group Policy across an organization.
There are several locations where you can set enterprise defaults, to enable their control either through Group Policy or directly in the registry. Visual Studio looks sequentially to see if any enterprise policies have been set; as soon as a policy value is discovered in the order below, the remaining keys are ignored.
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\Setup(on 64-bit operating systems)
If you do not set the
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\VisualStudio\Setup key and instead set one of the other keys, you should set both other keys on 64-bit operating systems. This issue is addressed in a future product update.
Some registry values are set automatically the first time they are used if not set already. This practice ensures that subsequent installs use the same values. These values are stored in the second registry key,
You can set the following registry values:
||%ProgramData%\Microsoft\VisualStudio\Packages||The directory where package manifests and, optionally, payloads are stored. For more information, see the Disable or move the package cache page.|
||1||Keep package payloads even after they are installed. You can change the value anytime. Disabling the policy removes any cached package payloads for the instance you repair or modify. For more information, see the Disable or move the package cache page.|
||%ProgramFiles(x86)%\Microsoft Visual Studio\Shared||The directory where some packages shared across versions of instances of Visual Studio are installed. You can change the value any time, but it will only affect future installs. Any products already installed to the old location must not be moved or they might not function correctly.|
If you change the
CachePath registry policy after any installations, you must move the existing package cache to the new location and make sure it's secured so that
Administrators have Full Control and that
Everyone has Read access.
Failure to move the existing cache or securing it might cause problems with future installs.
Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshoot Visual Studio installation and upgrade issues for step-by-step guidance.
We also offer a live chat (English only) support option for installation-related issues.
Here are a few more support options:
- Report product issues to us via the Report a Problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE.
- Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.
- Use your GitHub account to talk to us and other Visual Studio developers in the Visual Studio conversation in the Gitter community.