PENDING VS Build Tools 2022 Install Triggering Unwanted Restart in SCORCH Task Sequence

[Jshizzle]

I've created a VS Build Tools 2022 layout which can be deployed through SCCM without issue. The package program is also flagged to be installed from the Install Package task sequence without being deployed.

The command line for installation is:

vs_BuildTools.exe --wait --noUpdateInstaller --noWeb --norestart --quiet --in CustomInstall.json

My problem is that as part of the Install Additional Packages task sequence of a server build SCORCH runbook process, this triggers a reboot which then kills the TS.

It seems the switch --norestart is being ignored for some reason and I can't see why. The message in SCCM for this step shows:

Installation completed with exit code 0x80070bc2. Installation successful, reboot required. Setting TSEnv variable 'SMSTSRebootRequested'='HD'

I believe that exit code is just flagging that a reboot is required.

The strange thing is that I also have a VS Build Tools 2019 package that uses the same deployment process/command, obviously with the relevant version values, but this installs during build without issue or trying to trigger a reboot.

Any ideas on why this is ignoring the no restart switch or how I can suppress this?

 

[AhmedLS]

not sure why microsoft says this "the --norestart parameter will delay any necessary reboot". delay and not prevent or stop.
i would put a restart step on my task sequence after the step you run this command and see if it will bring the process back up again.