On a reference machine with the perfect VS setup, run:
Open PowerShell or CMD and run:
--nickname "DevOps Build Agent 2022" Here’s how you’d use this in a Windows container:
vs_enterprise.exe --export config.vsconfig silent install visual studio
vs_enterprise.exe --layout C:\VS2022_Layout \ --add Microsoft.VisualStudio.Workload.NativeDesktop \ --add Microsoft.VisualStudio.Workload.Universal \ --includeRecommended --lang en-US Then, from the target machine, run the silent install from the layout:
$exitCode = Start-Process -Wait -PassThru vs_enterprise.exe -ArgumentList "--quiet --wait --norestart --add Microsoft.VisualStudio.Workload.NetWeb" if ($exitCode -eq 0) { Write-Host "Success!" } elseif ($exitCode -eq 3010) { Write-Host "Success, but reboot required." } else { Write-Host "Failed with code: $exitCode" }
vs_enterprise.exe --quiet --wait --norestart --config config.vsconfig This ensures 100% parity across your team. Need to install on machines without internet? Create a local network layout first. On a reference machine with the perfect VS
FROM mcr.microsoft.com/windows/servercore:ltsc2022 COPY vs_enterprise.exe /installer/vs.exe COPY config.vsconfig /installer/config.vsconfig
RUN C:/installer/vs.exe --quiet --wait --norestart --config C:/installer/config.vsconfig && del /f /q C:/installer Visual Studio is a massive tool, but it doesn't have to be a massive distraction. Silent installation turns a 45-minute manual process into a 5-minute scripted one.
Download the bootstrapper, run --help , and build your perfect response file today. Have a nightmare silent install story? Or a clever script? Let me know in the comments below! FROM mcr
Let’s be honest: watching the Visual Studio Installer run interactively is like watching paint dry—except the paint has 15 different workloads, three SDKs, and keeps asking you to reboot.
Enter .