Update Visual Studio while on a servicing baseline
We update Visual Studio often during its product lifecycle. There are two types of updates:
- Minor release updates—for example, 16.0 to 16.1—that include new features and components.
- Servicing updates—for example, 16.0.4 to 16.0.5—that include only targeted fixes for critical issues.
Enterprise administrators can choose to keep their clients on a servicing baseline. A servicing baseline is supported with servicing updates for a year past the release of the next servicing baseline.
The servicing baseline option gives developers and administrators more flexibility to adopt the new features, bug fixes, or components included in new minor updates. The first servicing baseline is 16.0.x. For more information, see Support options for enterprise and professional customers.
How to get onto a servicing baseline
To start using a servicing baseline, download a fixed-version Visual Studio installer bootstrapper from My.VisualStudio.com. The bootstrappers have links to the product configurations, workloads, and components for that specific version.
Be careful to distinguish between the fixed-version bootstrapper and the standard bootstrappers. The standard bootstrappers are configured to use the latest available release of Visual Studio. The standard boostrappers have a number in the file name (for example, vs_enterprise__123456789-123456789.exe) when they're downloaded from My.VisualStudio.com.
During installation, enterprise administrators must configure their clients to prevent the clients from updating to the latest release. There are several ways to do this:
- Change the
channelUrisetting in the response configuration file to use a channel manifest in the layout or local folder.
- Modify the channelUri through command-line execution to use a nonexistent file.
- Set policies on the client system to disable updates, to prevent clients from self-updating.
Install a servicing baseline on a network
Administrators who use a network layout installation should modify the
channelUri value in the response.json file in the layout to use the channelmanifest.json file that's in the same folder. For the steps to take, see Control updates to network-based Visual Studio deployments. Changing the
channelUri value enables clients to look for updates in the layout location.
Install a servicing baseline via the internet
For an internet-based installation, add
--channelUri with a non-existent channel manifest to the command-line used to launch setup. This disables Visual Studio from using the latest available release for an update. Here's an example:
vs_enterprise.exe --channelUri c:\doesnotexist.chman
Use policy settings to disable clients from updating
Another option to control updates on a client is to turn off update notifications. Use this option if the channelUri value was not changed on installation. It will disable the client from receiving links to the latest available release. A fixed-version bootstrapper is still necessary to update to a specific version on the client.
How to stay on a servicing baseline
When an update for a servicing baseline is available, fixed-version bootstrapper files are made available for the servicing update at My.VisualStudio.com.
For administrators who deploy by using a network layout install, the administrator should update the layout location. Clients that installed from the location will receive update notifications. If the update must be deployed to clients, follow these instructions. When you modify the 'response.json' for an update, do not add additional workloads, components, or languages. Managing these settings must be done as a 'modify' deployment after the product has been updated.
For an internet-based installation, run the new fixed version bootstrapper with the
--channelUri parameter pointing to a non-existent channel manifest on the client. If the update is deployed in quiet or passive mode, use two separate commands:
Update the Visual Studio installer:
vs_enterprise.exe --quiet --update
Update the Visual Studio application itself:
vs_enterprise.exe update --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise" --quiet --wait --norestart --channelUri c:\doesnotexist.chman
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 an installation 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.
- Install Visual Studio
- Visual Studio administrator guide
- Use command-line parameters to install Visual Studio
- Tools for detecting and managing Visual Studio instances
- How to define settings in a response file
- Control updates to network-based Visual Studio deployments
- Visual Studio product lifecycle and servicing