Skip to content

Commit 7927822

Browse files
Merge pull request #15310 from jasonchlus/sxs-default-launch-version
Add instructions for changing default Visual Studio version in SxS in…
2 parents af5e130 + 0dd84c9 commit 7927822

1 file changed

Lines changed: 25 additions & 3 deletions

File tree

docs/install/install-visual-studio-versions-side-by-side.md

Lines changed: 25 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Install Visual Studio Versions Side-by-Side
33
description: Learn how to install Visual Studio on a computer that has an earlier or later version of Visual Studio already installed.
44
ms.custom: vs-acquisition
5-
ms.date: 08/25/2025
5+
ms.date: 04/24/2026
66
ms.subservice: installation
77
ms.topic: concept-article
88
helpviewer_keywords:
@@ -18,7 +18,6 @@ ms.author: rosemalcolm
1818

1919
You can install Visual Studio on a computer that has an earlier or later [major version](/visualstudio/productinfo/release-rhythm#determining-your-product-edition-version-and-channel) of Visual Studio already installed. This article describes how to install multiple versions of Visual Studio.
2020

21-
2221
::: moniker range=">=vs-2022"
2322

2423
Before you install versions side-by-side, review the following conditions:
@@ -35,7 +34,6 @@ Before you install versions side-by-side, review the following conditions:
3534

3635
## Install different editions of the same major Visual Studio version side-by-side
3736

38-
3937
::: moniker range="vs-2022"
4038

4139
Each installation of Visual Studio must have a unique combination of major version, edition, and [update channel](/visualstudio/install/update-visual-studio?view=vs-2022&preserve-view=true#configure-source-location-of-updates-1). For example, you can install Visual Studio 2022 Enterprise Preview ([preview channel](/visualstudio/productinfo/release-rhythm)) alongside Visual Studio 2022 Enterprise (release channel) alongside Visual Studio 2019 Professional (release channel) alongside Visual Studio 2019 Professional (custom layout channel).
@@ -93,6 +91,30 @@ To install by using the installer that's already on the client machine:
9391

9492
You can't start the installer programmatically from the same directory that the installer resides in.
9593

94+
## Change which Visual Studio version launches by default
95+
96+
When you have multiple versions of Visual Studio installed side-by-side, Windows commands like **Win+R** > `devenv` use the **App Paths** registry key to determine which version of `devenv.exe` to launch. By default, this key points to the most recently installed version, which might not be the version you prefer.
97+
98+
You can change the default version by updating the App Paths registry entry, or by using alternative launch methods.
99+
100+
### Update the App Paths registry entry
101+
102+
1. Open **Registry Editor** (press **Win+R**, type `regedit`, and then press **Enter**).
103+
1. Navigate to the following key:
104+
105+
```
106+
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\devenv.exe
107+
```
108+
109+
1. The **(Default)** value shows the full path to the `devenv.exe` that Windows launches. Change this value to point to the version of Visual Studio you want to use as the default. For example:
110+
111+
- **Visual Studio 2022**: `C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\devenv.exe`
112+
- **Visual Studio 2019**: `C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.exe`
113+
114+
Replace *Enterprise* with *Professional* or *Community* to match your installed edition.
115+
116+
1. Close the Registry Editor. The change takes effect immediately for new **Win+R** commands.
117+
96118
## .NET Framework versions and side-by-side installations
97119

98120
Visual Basic, Visual C#, and Visual F# projects use the **Target framework** option in the **Project Designer** to specify the version of the .NET Framework that they use. For a C++ project, you can manually change the target framework by modifying the *.vcxproj* file. For more information, see [Version compatibility in the .NET Framework](/dotnet/framework/migration-guide/version-compatibility).

0 commit comments

Comments
 (0)