Share via


Using command line to silently upgrade just the installer in Visual Studio 2017 (15.2)

Question

Tuesday, September 5, 2017 5:29 PM

Hello,

We've been deploying this version via SCCM and it's working fine.  However we had to quickly upgrade from 15.2 to 15.3 to try to fix a non-admin issue under windows 7.   What I'm finding is the first thing it wants to do is upgrade the installer located in the folder:

C:\Program Files (x86)\Microsoft Visual Studio\Installer

before being able to actually use it to update/add/modify any of the actual VS 2017 (15.2) product.  Once it's upgraded, the silent installers work like a charm.  My issue is, there is no way that I can see to do that initial upgrade of the installer without actually using the GUI, which is not feasible when we're talking 100+ computers.

There is a new switch --noUpdateInstaller but in this case it looks like a update of the installer is required and therefore will not continue according to the switch's description.

Is there any way to get just the installer to upgrade itself in a silent manner?

Thanks,
Guy

All replies (1)

Wednesday, September 6, 2017 6:07 AM âś…Answered

Hi Guy,

Thank you for posting in MSDN forum.

Usually, Update Visual Studio 2017 to the most recent release explains the two ways of updating VS.

>>Is there any way to get just the installer to upgrade itself in a silent manner?

Giving that you need a silent update VS installer for more than 100 computers, please refer to

Update a network-based installation of Visual Studio :

Administrators can update client deployments of Visual Studio without any user interaction with two separate commands:

  • First, update the Visual Studio installer:
    vs_enterprise.exe --quiet --update

  • Then, update the Visual Studio application itself:
    vs_enterprise.exe update --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise" --quiet --wait --norestart

See also:

Best Regards,

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].