Installing VS build tools with out any prompt

Varma 1,385

I am using following script to VSbuild tools 2022, but what is happening it makes to go that folder and run manually even I have provided arguments in the below script which should not to prompt for window,

User's image

script:

Create the 'C:\software' directory if it doesn't exist

New-Item -ItemType Directory -Path 'C:\software' -Force

Change the current directory to 'C:\software'

Set-Location -Path 'C:\software'

Download the Visual Studio Build Tools installer

Invoke-WebRequest -Uri 'https://aka.ms/vs/17/release/vs_BuildTools.exe' -UseBasicParsing -OutFile 'c:\software\vs_installer.exe'

Display a message indicating the start of installation

Write-Host 'Starting installation with selected components...'

Define the installation arguments

$arguments = '--quiet --norestart --nocache --wait --noupdateInstaller --noweb --add "Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools" --add "Microsoft.VisualStudio.Workload.WebBuildTools" --add "Microsoft.VisualStudio.Workload.AzureBuildTools" --add "Microsoft.VisualStudio.Workload.DataBuildTools" --includeRecommended'

Run the installer with the specified arguments

Start-Process -FilePath 'c:\software\vs_installer.exe' -Wait -ArgumentList $arguments

Please suggest way to install without asking for any prompt.

Rich Matheisen 47,466 Reputation points

2024-04-21T14:33:17.62+00:00

Does it work if you run vs_installer.exe with the command line arguments in your example?

Why not add an appropriate "Visual Studio" to your question? That would, at least present your question to Visual Studio SMEs.
Varma 1,385 Reputation points

2024-04-21T15:15:37.33+00:00

Hi Rich,

I tried that, you can see it is still asking for prompt. Please see below and suggest the fix.

Looking Forword for your response.
Rich Matheisen 47,466 Reputation points

2024-04-21T21:28:43.0733333+00:00

If you're going to run the vs_installer.exe from the command line, you shouldn't be using a parameter named -ArgumentList (it's not a vs_installer.exe parameter). Also, the parameters shouldn't be a single-quote protected string.

You'd use that -ArgumentList parameter if you used Start-Process.
Varma 1,385 Reputation points

2024-04-21T22:37:15.66+00:00

Hi Rich,

I didn’t get you ,

can you give screenshot

Rich Matheisen 47,466

Screenshots aren't usually helpful.

c:\software\vs_installer.exe --quiet --norestart --nocache --wait --noupdateInstaller --noweb --add "Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools" --add "Microsoft.VisualStudio.Workload.WebBuildTools" --add "Microsoft.VisualStudio.Workload.AzureBuildTools" --add "Microsoft.VisualStudio.Workload.DataBuildTools" --includeRecommended

Assuming(!) all your parameters are correct, and the values properly protected (where necessary), that should work from the shell prompt.

Varma 1,385

HI RIch,Still not working

is it possible to test from your end once and share me the script?

New-Item -ItemType Directory -Path 'c:\software'
cd c:\software
Invoke-WebRequest -Uri '
https://aka.ms/vs/17/release/vs_BuildTools.exe' -UseBasicParsing -OutFile c:\software\vs_installer.exe
Write-Host 'Starting installation with selected components...'
#$arguments = '--quiet --norestart --nocache --wait --noupdateInstaller --noweb --add "Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools" --add "Microsoft.VisualStudio.Workload.WebBuildTools" --add "Microsoft.VisualStudio.Workload.AzureBuildTools" --add "Microsoft.VisualStudio.Workload.DataBuildTools" --includeRecommended'
Start-Process c:\software\vs_installer.exe '--quiet --norestart  --nocache --wait --noupdateInstaller --noweb --add "Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools" --add "Microsoft.VisualStudio.Workload.WebBuildTools" --add "Microsoft.VisualStudio.Workload.AzureBuildTools" --add "Microsoft.VisualStudio.Workload.DataBuildTools" --includeRecommended.'

Rich Matheisen 47,466 Reputation points

2024-04-22T15:03:54.6533333+00:00
Your previous comment showed you running the exe from the shell prompt, not from a cmdlet (Start-Process).

Let's go back to my original question to you: does running the exe from the shell prompt, using the parameter set in your original post, work as you would expect to.

You replied that it did not, but you used some odd mixture of Start-Process parameters and a protected string containing all the exe's parameters. To that I answered with how the exe and parameters should have been run from the shell prompt.

Now you're back at using Start-Process!

So, when you get around to running the exe from the shell prompt in the way I suggested (repeated below) go ahead and post the result of that. Just copy and paste this at a shell prompt:

c:\software\vs_installer.exe --quiet --norestart --nocache --wait --noupdateInstaller --noweb --add "Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools" --add "Microsoft.VisualStudio.Workload.WebBuildTools" --add "Microsoft.VisualStudio.Workload.AzureBuildTools" --add "Microsoft.VisualStudio.Workload.DataBuildTools" --includeRecommended

2 answers

Anna Xiu-MSFT 30,116 Reputation points Microsoft Vendor

2024-04-22T09:02:06.07+00:00

Hello @Varma,

I tried all the scripts you and Rich provided. None of the Visual Studio Installer prompts pop up when the scripts are run. The --quiet parameter prevents any user interface from being displayed when the script is executed.

If the installation is paused, please remove the --noweb parameter and try again.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Varma 1,385 Reputation points

2024-04-22T09:20:28.1366667+00:00

Hi Anna Xiu,

I tried exactly how you tried, but not sure I am not certain why I am not seeing VSBUild tools 2022 window and I am not able to see it from control panel as well. Please suggest further.

Varma 1,385 Reputation points

2024-04-22T10:56:08.0433333+00:00

Hi Anna ,

is there any way I can get latest version of https://aka.ms/vs/17/release/vs_BuildTools.exe%27

if yes could you please share the link for the latest so that I will verify with that..

Anna Xiu-MSFT 30,116 Reputation points Microsoft Vendor

2024-04-24T09:28:38.47+00:00

Hello, could you see it in the task manager when running the script?

The link (https://aka.ms/vs/17/release/vs_BuildTools.exe) is the latest version of Build Tools. You can try the script again provided by Rich.

Varma 1,385 Reputation points

2024-04-24T09:37:58.3966667+00:00

HI Anna,

We fixed it, We can close this issue.

Anna Xiu-MSFT 30,116 Reputation points Microsoft Vendor

2024-04-24T09:52:41.35+00:00

Glad your issue has been resolved, would you like to share the solution so that other users with similar issue can refer to it?

Varma 1,385 Reputation points

2024-04-24T09:59:21.5266667+00:00

Hi Anna,

Sure.

It is simple, I removed these argurments and it worked :)

--noupdateInstaller --noweb

you can convert this to answer so that I will mark it as answer.

Varma 1,385 Reputation points

2024-04-24T09:59:55.2866667+00:00

test123

Anna Xiu-MSFT 30,116 Reputation points Microsoft Vendor

2024-04-24T10:06:10.84+00:00

Sorry to say that the forum does not allow users to accept their own responses as answers currently.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Rich Matheisen 47,466 Reputation points

2024-04-24T15:24:02.7033333+00:00

Removing the --noupdateInstaller --noweb switches looks like it fixed your problem.

It seems that determining the need to use those two switches is not as simple as it seems:

https://stackoverflow.com/questions/62259223/visual-studio-2019-offline-layout-update-ignoring-noupdateinstaller

https://learn.microsoft.com/en-us/visualstudio/install/use-command-line-parameters-to-install-visual-studio?view=vs-2022
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via