Silent install command for WingetPathUpdater 1.3

The exact silent switches the WingetPathUpdater installer accepts, plus a one-line command you can paste into a script, Intune Win32 app, or Configuration Manager package.

One-line silent install (x64, machine scope)

PowershellStub.exe Silent https://raw.githubusercontent.com/jazzdelightsme/WingetPathUpdater/v1.3/WingetPathUpdaterInstall.ps1 90BD0E9FB53F5D7CB3AB81D57846BF13E8EC0A3230645D880463148FA0BAB41A

Run from the directory containing PowershellStub.exe. Download the installer from the Direct link below first. Run an elevated terminal (Run as Administrator) for machine-scope installs.

Architecture	Scope	Type	Silent switches	Source
x64	machine	EXE		Declared by publisher

Declared by publisher means the switches come straight from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs.
Default for {type} means the manifest doesn't specify silent switches, so the framework's standard switches are shown (e.g. /S for NSIS, /quiet /norestart for MSI).

Frequently asked questions

What is the silent install command for WingetPathUpdater?

WingetPathUpdater uses EXE. After downloading the installer, run: PowershellStub.exe Silent https://raw.githubusercontent.com/jazzdelightsme/WingetPathUpdater/v1.3/WingetPathUpdaterInstall.ps1 90BD0E9FB53F5D7CB3AB81D57846BF13E8EC0A3230645D880463148FA0BAB41A. The silent install switches are Silent https://raw.githubusercontent.com/jazzdelightsme/WingetPathUpdater/v1.3/WingetPathUpdaterInstall.ps1 90BD0E9FB53F5D7CB3AB81D57846BF13E8EC0A3230645D880463148FA0BAB41A.

How do I deploy WingetPathUpdater via Intune or Configuration Manager?

Use winget for the cleanest path: winget install --id jazzdelightsme.WingetPathUpdater --exact 1.3 --silent --accept-package-agreements --accept-source-agreements. If winget isn't viable in your environment, package the publisher's installer directly using the silent switches above.

Where do these silent switches come from?

The switches marked "Declared by publisher" come from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs. Switches marked "Default for EXE" come from the installer framework's documented defaults.

Prefer the winget route? See the full WingetPathUpdater install page.