Silent install command for LocalFlow 0.2.6

The exact silent switches the LocalFlow 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)

msiexec.exe /i localflow-v0.2.6-x64.msi /quiet /norestart /norestart

Run from the directory containing localflow-v0.2.6-x64.msi. 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	MSI WiX	Custom: /norestart	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 LocalFlow?

LocalFlow uses MSI (WiX). After downloading the installer, run: msiexec.exe /i localflow-v0.2.6-x64.msi /quiet /norestart /norestart. The silent install switches are /quiet /norestart.

How do I deploy LocalFlow via Intune or Configuration Manager?

Use winget for the cleanest path: winget install --id localflow-app.LocalFlow --exact 0.2.6 --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 MSI (WiX)" come from the installer framework's documented defaults.

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