From ae8995298f28fb07ab2e1eef817cbeea20dde1b6 Mon Sep 17 00:00:00 2001 From: "Angenendt, Markus" Date: Mon, 16 Mar 2026 15:15:33 +0100 Subject: [PATCH 1/5] Add note about offline layout path behahior --- .../create-an-offline-installation-of-visual-studio.md | 7 +++++-- docs/install/deploy-a-layout-onto-a-client-machine.md | 4 ++++ 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/install/create-an-offline-installation-of-visual-studio.md b/docs/install/create-an-offline-installation-of-visual-studio.md index 5791358d627..c8d38d2e16a 100644 --- a/docs/install/create-an-offline-installation-of-visual-studio.md +++ b/docs/install/create-an-offline-installation-of-visual-studio.md @@ -59,7 +59,6 @@ Here are some common local layout creation examples. More examples can be found vs_enterprise.exe --layout c:\localVSlayout ``` - ::: moniker range=">=vs-2022" > [!NOTE] @@ -87,7 +86,6 @@ When you install Visual Studio from a local layout, the Visual Studio Installer For example, if you created a local installation layout with the following command: - ::: moniker range=">=vs-2022" ```shell @@ -102,6 +100,11 @@ c:\localVSlayout\vs_enterprise.exe --noWeb --add Microsoft.VisualStudio.Workload ::: moniker-end +> [!IMPORTANT] +> When Visual Studio is installed from an offline layout, the installer records the layout path in the `C:\ProgramData\Microsoft\VisualStudio\Packages\_Instances\\state.json` file. +> Future Updates or component additions expect the layout to remain at the same path. +> If the layout is moved to a different location, the installer may no be able to find the required packages. + > [!IMPORTANT] > If you're using Visual Studio Community, you might be prompted to sign in within 30 days of installation, but it won't impact your ability to use the product. diff --git a/docs/install/deploy-a-layout-onto-a-client-machine.md b/docs/install/deploy-a-layout-onto-a-client-machine.md index 10b1b8da36b..9105cd43605 100644 --- a/docs/install/deploy-a-layout-onto-a-client-machine.md +++ b/docs/install/deploy-a-layout-onto-a-client-machine.md @@ -112,6 +112,10 @@ You need to make sure that any [offline client machines have the right certifica When you install from a layout, the installer on the client always looks for the Visual Studio packages in the layout's location. However, if the installer tries to install components that are *not* included in the layout, then it will attempt to acquire the Visual Studio packages from the [update source](update-visual-studio.md#configure-source-location-of-updates-1), which administrators often configure to [point back to itself](automated-installation-with-response-file.md#configure-the-response-file-used-when-installing-from-a-layout). +> [!IMPORTANT] +> Remember that the layout location should remain the same for each Visual Studio instance. +> For more details, see [Install Visual Studio from the local layout](create-an-offline-installation-of-visual-studio.md#step-3---install-visual-studio-from-the-local-layout) + If you want to explicitly prevent the Visual Studio Installer from attempting to download any missing content from Microsoft hosted servers on the web, you can use the [`--noWeb` parameter](use-command-line-parameters-to-install-visual-studio.md#layout-command-and-command-line-parameters). If `--noWeb` is used and the layout is missing a component that is selected to be installed, then the setup will fail. Also, if `--noWeb` is used and the layout is hosted on your intranet web servers as opposed to a file network share, then the setup will fail. Using the `--noweb` switch often fixes the error message "A product matching the following parameters can't be found". From 86f7d03ebd77316ad2a2db7496646f0ef40b71e0 Mon Sep 17 00:00:00 2001 From: Markus Angenendt Date: Mon, 16 Mar 2026 20:22:25 +0100 Subject: [PATCH 2/5] create-an-offline-installation-of-visual-studio.md aktualisieren Correct Copilot suggestions --- .../create-an-offline-installation-of-visual-studio.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/install/create-an-offline-installation-of-visual-studio.md b/docs/install/create-an-offline-installation-of-visual-studio.md index c8d38d2e16a..cefb1d841d9 100644 --- a/docs/install/create-an-offline-installation-of-visual-studio.md +++ b/docs/install/create-an-offline-installation-of-visual-studio.md @@ -101,9 +101,9 @@ c:\localVSlayout\vs_enterprise.exe --noWeb --add Microsoft.VisualStudio.Workload ::: moniker-end > [!IMPORTANT] -> When Visual Studio is installed from an offline layout, the installer records the layout path in the `C:\ProgramData\Microsoft\VisualStudio\Packages\_Instances\\state.json` file. +> When Visual Studio is installed from a local layout, the installer records the layout path in the `C:\ProgramData\Microsoft\VisualStudio\Packages\_Instances\\state.json` file. > Future Updates or component additions expect the layout to remain at the same path. -> If the layout is moved to a different location, the installer may no be able to find the required packages. +> If the layout is moved to a different location, the installer may not be able to find the required packages. > [!IMPORTANT] > If you're using Visual Studio Community, you might be prompted to sign in within 30 days of installation, but it won't impact your ability to use the product. From bccd7fbe07334045b9610e391f0842801dfaa862 Mon Sep 17 00:00:00 2001 From: Markus Angenendt Date: Mon, 16 Mar 2026 20:23:26 +0100 Subject: [PATCH 3/5] deploy-a-layout-onto-a-client-machine.md aktualisieren Correct Copilot suggestions --- docs/install/deploy-a-layout-onto-a-client-machine.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/install/deploy-a-layout-onto-a-client-machine.md b/docs/install/deploy-a-layout-onto-a-client-machine.md index 9105cd43605..ed008734060 100644 --- a/docs/install/deploy-a-layout-onto-a-client-machine.md +++ b/docs/install/deploy-a-layout-onto-a-client-machine.md @@ -114,7 +114,7 @@ When you install from a layout, the installer on the client always looks for the > [!IMPORTANT] > Remember that the layout location should remain the same for each Visual Studio instance. -> For more details, see [Install Visual Studio from the local layout](create-an-offline-installation-of-visual-studio.md#step-3---install-visual-studio-from-the-local-layout) +> For more details, see [Install Visual Studio from the local layout](create-an-offline-installation-of-visual-studio.md#step-3---install-visual-studio-from-the-local-layout) . If you want to explicitly prevent the Visual Studio Installer from attempting to download any missing content from Microsoft hosted servers on the web, you can use the [`--noWeb` parameter](use-command-line-parameters-to-install-visual-studio.md#layout-command-and-command-line-parameters). If `--noWeb` is used and the layout is missing a component that is selected to be installed, then the setup will fail. Also, if `--noWeb` is used and the layout is hosted on your intranet web servers as opposed to a file network share, then the setup will fail. From 65ede708cf31d1450e8d2ac1c803372fa7dbd146 Mon Sep 17 00:00:00 2001 From: Markus Angenendt Date: Mon, 16 Mar 2026 20:24:31 +0100 Subject: [PATCH 4/5] deploy-a-layout-onto-a-client-machine.md aktualisieren Correct Copilot suggestions --- docs/install/deploy-a-layout-onto-a-client-machine.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/install/deploy-a-layout-onto-a-client-machine.md b/docs/install/deploy-a-layout-onto-a-client-machine.md index ed008734060..870a5b7ab73 100644 --- a/docs/install/deploy-a-layout-onto-a-client-machine.md +++ b/docs/install/deploy-a-layout-onto-a-client-machine.md @@ -114,7 +114,7 @@ When you install from a layout, the installer on the client always looks for the > [!IMPORTANT] > Remember that the layout location should remain the same for each Visual Studio instance. -> For more details, see [Install Visual Studio from the local layout](create-an-offline-installation-of-visual-studio.md#step-3---install-visual-studio-from-the-local-layout) . +> For more details, see [Install Visual Studio from the local layout](create-an-offline-installation-of-visual-studio.md#step-3---install-visual-studio-from-the-local-layout). If you want to explicitly prevent the Visual Studio Installer from attempting to download any missing content from Microsoft hosted servers on the web, you can use the [`--noWeb` parameter](use-command-line-parameters-to-install-visual-studio.md#layout-command-and-command-line-parameters). If `--noWeb` is used and the layout is missing a component that is selected to be installed, then the setup will fail. Also, if `--noWeb` is used and the layout is hosted on your intranet web servers as opposed to a file network share, then the setup will fail. From f7473d8ff5611fe4d4974d053016e52486e50e83 Mon Sep 17 00:00:00 2001 From: Markus Angenendt Date: Mon, 16 Mar 2026 20:27:02 +0100 Subject: [PATCH 5/5] create-an-offline-installation-of-visual-studio.md aktualisieren Correct Copilot suggestions --- docs/install/create-an-offline-installation-of-visual-studio.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/install/create-an-offline-installation-of-visual-studio.md b/docs/install/create-an-offline-installation-of-visual-studio.md index cefb1d841d9..34e3dd6e472 100644 --- a/docs/install/create-an-offline-installation-of-visual-studio.md +++ b/docs/install/create-an-offline-installation-of-visual-studio.md @@ -103,7 +103,7 @@ c:\localVSlayout\vs_enterprise.exe --noWeb --add Microsoft.VisualStudio.Workload > [!IMPORTANT] > When Visual Studio is installed from a local layout, the installer records the layout path in the `C:\ProgramData\Microsoft\VisualStudio\Packages\_Instances\\state.json` file. > Future Updates or component additions expect the layout to remain at the same path. -> If the layout is moved to a different location, the installer may not be able to find the required packages. +> If the local layout is moved to a different location, the installer may not be able to find the required packages. > [!IMPORTANT] > If you're using Visual Studio Community, you might be prompted to sign in within 30 days of installation, but it won't impact your ability to use the product.