Flow Launcher with Chocolatey: Setup and Updates

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

At a glance

Chocolatey is another package-manager route documented by Flow Launcher. Review the package details and source, install it through your existing Chocolatey environment, and verify the resulting application version. Do not assume the newest project release is already available in every package repository.

Steps to follow

  1. Use your established Chocolatey installation and check the configured package sources. On work PCs, use the approved internal source where required.
  2. Inspect Flow-Launcher package metadata with choco info. Compare the listed version and download origin with the project release information.
  3. Install the package, reading the prompts rather than automatically accepting an unexpected script or permission request.
  4. For updates, close Flow after backing up UserData, upgrade the same package, and reopen the launcher to confirm its version and settings.
choco info Flow-Launcher
choco install Flow-Launcher
choco upgrade Flow-Launcher

Check the result

The Chocolatey package version and the running app version should correspond. Test that only one Flow process starts at sign-in and responds to your shortcut.

Limits and common pitfalls

Package publication and upstream release publication are separate events. A repository lag is not a reason to install an unreviewed package with a similar name.

Make the check repeatable

Keep the distinction between a package manifest and the executable it retrieves. Check both when troubleshooting an installation. If changing from a manual copy, preserve your data first and identify which shortcuts or startup entries belong to each copy before removing either one.

Questions and answers

Does this command always install the version shown on this site?

No. Your configured Chocolatey source determines the available package. Inspect its metadata at the time of installation.

Sources and scope

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

Related guides