Flow Launcher with Scoop: Install and Maintain

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

At a glance

Scoop is one of the installation methods listed by the Flow Launcher project. Use an existing, trusted Scoop setup, inspect the Flow-Launcher manifest, and keep updates within that setup. A successful package install should be followed by a normal app and hotkey check.

Steps to follow

  1. Confirm that Scoop is already installed and working for your Windows account. Do not paste an unfamiliar installer script just to follow a launcher guide.
  2. Run scoop search Flow-Launcher. Inspect the result and the bucket that supplies it; available buckets depend on your own Scoop configuration.
  3. Read the package information, then install Flow-Launcher from the expected source. Launch the application from its installed shortcut.
  4. Back up UserData before updating, run the package update, and confirm that your shortcut launches the updated copy rather than an old portable folder.
scoop search Flow-Launcher
scoop info Flow-Launcher
scoop install Flow-Launcher
scoop update Flow-Launcher

Check the result

Check Scoop package information and Flow About. Test the same application search and hotkey before and after an update so that results are comparable.

Limits and common pitfalls

If the package cannot be found, do not invent a bucket URL or choose a look-alike package. Check the project installation references and your configured Scoop sources.

Make the check repeatable

A package manager is responsible for locating and installing a release, while Flow maintains its user settings separately. Preserve both facts in your notes: which manager owns the app and where the active profile lives. This makes rollback and removal much less confusing.

Questions and answers

Can I mix Scoop updates with manual installer updates?

Avoid mixing methods for one installation. Choose a single managed copy and migrate deliberately when changing deployment methods.

Sources and scope

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

Related guides