Install and Update Flow Launcher with WinGet

Installation · Published October 30, 2026 · Publisher: flowlauncher.app

At a glance

WinGet can install Flow Launcher by package identifier. Inspect the matching package before installation and use the same manager for later updates. This avoids confusing a separately installed copy with the one that currently handles your hotkey.

Steps to follow

  1. Open Windows Terminal and confirm that winget is available. If it is missing, use Windows App Installer guidance instead of running a random bootstrap script.
  2. Search for Flow Launcher, then inspect the exact Flow-Launcher.Flow-Launcher package. Check the publisher and installer URL returned by WinGet.
  3. Install the package using its exact identifier. Read source and installer agreements, then open Flow Launcher from Windows.
  4. Before updating, back up your settings and inspect the available version. Upgrade that same package identifier, then verify the version in Flow About.
winget search "Flow Launcher"
winget show --id Flow-Launcher.Flow-Launcher --exact
winget install --id Flow-Launcher.Flow-Launcher --exact
winget upgrade --id Flow-Launcher.Flow-Launcher --exact

Check the result

WinGet list should show the expected installed package. Flow About should agree with the version actually installed, and the original hotkey should still open the correct instance.

Limits and common pitfalls

Multiple installations can coexist after switching between portable, installer, and package-manager methods. Resolve duplicate startup entries before deciding that a WinGet update failed.

Make the check repeatable

The source metadata can change independently of this guide. Commands below query the package at execution time; they do not pin a promised current version. A managed workplace may restrict WinGet or installation sources. Respect that policy instead of attempting to bypass it.

Questions and answers

Why use an exact package identifier?

It reduces ambiguous name matches. Inspecting the package still matters because the command is not a substitute for checking its origin.

Sources and scope

Documentation-based guidance, with source review on October 30, 2026. What was and was not tested.

Related guides

Package information and verification