You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/install/install-visual-studio-versions-side-by-side.md
+25-3Lines changed: 25 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Install Visual Studio Versions Side-by-Side
3
3
description: Learn how to install Visual Studio on a computer that has an earlier or later version of Visual Studio already installed.
4
4
ms.custom: vs-acquisition
5
-
ms.date: 08/25/2025
5
+
ms.date: 04/24/2026
6
6
ms.subservice: installation
7
7
ms.topic: concept-article
8
8
helpviewer_keywords:
@@ -18,7 +18,6 @@ ms.author: rosemalcolm
18
18
19
19
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.
20
20
21
-
22
21
::: moniker range=">=vs-2022"
23
22
24
23
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:
35
34
36
35
## Install different editions of the same major Visual Studio version side-by-side
37
36
38
-
39
37
::: moniker range="vs-2022"
40
38
41
39
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:
93
91
94
92
You can't start the installer programmatically from the same directory that the installer resides in.
95
93
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**).
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
+
96
118
## .NET Framework versions and side-by-side installations
97
119
98
120
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