(run on target offline build server):

C:\vs2022_buildtools_offline\vs_buildtools.exe The UI will open, but all packages are loaded from the local layout – no internet required. | Argument | Effect | |----------|--------| | --quiet | No UI, no prompts. | | --passive | Shows progress bar but no interaction. | | --wait | Process exits only after installation completes. | | --norestart | Suppress automatic reboots. | | --installPath <path> | Target directory (default: Program Files). | | --add <ID> | Install specific workload/component. | | --remove <ID> | Uninstall a workload. | | --includeRecommended | Include recommended components. | | --includeOptional | Include optional components (rarely used). | Part 5: Maintaining and Updating Your Offline Layout The biggest challenge with offline installers is keeping them patched. Microsoft releases updates monthly (security fixes, new SDKs, toolchain improvements). Updating an Existing Layout Run the same layout command on the machine that holds the original layout (the one with internet access):

vs_buildtools.exe --config config.vsconfig --quiet Here are essential IDs for Build Tools 2022 (latest as of 2024–2025):

C:\BuildTools\MSBuild\Current\Bin Or use full path in scripts. Build Tools 2022 does not support Windows 8.1 or older. Upgrade OS. Part 9: Comparison with Alternative Approaches | Method | Pros | Cons | |--------|------|------| | Online installer each time | Always latest patches | Slow, network-dependent, unreproducible | | Offline layout (this article) | Reproducible, air-gap capable, fast deployment | Requires manual updates, large initial download | | Chocolatey / winget | Easy scripting | Still requires internet per install | | Pre-built VM image with tools baked in | Extremely fast | Heavy, less flexible |

(run on internet-connected machine):

vs_buildtools.exe --layout C:\vs2022_buildtools_offline --lang en-US This downloads all available Build Tools workloads and components for English (en-US). It will take a long time (10–100+ GB) and considerable bandwidth. To save space and time, specify only the workloads you actually need. Use --add to include workloads or individual components.

FROM mcr.microsoft.com/windows/servercore:ltsc2022 COPY ./vs2022_buildtools_offline C:/vs_layout RUN C:/vs_layout/vs_buildtools.exe --quiet --wait --norestart --installPath C:/BuildTools --add Microsoft.VisualStudio.Workload.VCTools Use --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 instead of full workload for smaller container size. 3. Generating a Bootstrapper for Distribution You can create a self-contained vs_buildtools.exe that references your layout:

$layoutPath = "D:\vs2022_buildtools_offline" $bootstrapper = "vs_buildtools.exe" if (-not (Test-Path $bootstrapper)) Invoke-WebRequest -Uri "https://aka.ms/vs/17/release/vs_buildtools.exe" -OutFile $bootstrapper Create minimal C++ + .NET layout & .$bootstrapper --layout $layoutPath --add Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools --add Microsoft.VisualStudio.Workload.VCTools --add Microsoft.VisualStudio.Component.Windows11SDK.22621 --lang en-US ` --includeRecommended