Silent install command for Microsoft Foundry DevPack 0.1.0

The exact silent switches the Microsoft Foundry DevPack 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, user scope)

foundry-devpack-win-x64.exe install --channel winget

Run from the directory containing foundry-devpack-win-x64.exe. Download the installer from the Direct link below first.

Architecture	Scope	Type	Silent switches	Source
x64	user	EXE		Declared by publisher
arm64	user	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 Microsoft Foundry DevPack?

Microsoft Foundry DevPack uses EXE. After downloading the installer, run: foundry-devpack-win-x64.exe install --channel winget. The silent install switches are install --channel winget.

How do I deploy Microsoft Foundry DevPack via Intune or Configuration Manager?

Use winget for the cleanest path: winget install --id Microsoft.FoundryDevPack --exact 0.1.0 --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 Microsoft Foundry DevPack install page.