Start Flow Launcher with Windows and Avoid Duplicate Copies

Appearance and settings · Published October 30, 2026 · Publisher: flowlauncher.app

At a glance

Flow Launcher must be running for its activation shortcut to work. Configure startup through the supported app or Windows settings, then test a fresh sign-in. Use one startup method for one installation to avoid two copies competing for the same hotkey or writing different profiles.

Steps to follow

  1. Identify the installation you intend to keep and verify its executable path and active UserData folder.
  2. Review Flow’s startup option and the Windows startup-app entry for that copy. Avoid adding an extra manual shortcut when startup is already configured.
  3. Sign out and back in when convenient, then check whether Flow is running and whether its hotkey works.
  4. If an old portable or package-manager copy also starts, remove only the obsolete startup registration after preserving its data.

Check the result

One intended Flow instance starts after sign-in, responds to the selected hotkey, and uses the expected profile.

Limits and common pitfalls

An app may start hidden in the tray. A missing search window at sign-in is not proof that startup failed; inspect the tray or process before changing settings.

Make the check repeatable

Keep startup troubleshooting separate from search troubleshooting. A launcher that starts correctly but returns no files needs an index or plugin check, not another startup task. Record whether the failure happens before sign-in, immediately after it, or only when another utility launches.

Questions and answers

Why does the shortcut work only after opening Flow manually?

The app may not be starting automatically, or a different copy may be registered. Check the startup entry and its path.

Sources and scope

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

Related guides

Appearance and settings

Back Up and Restore Flow Launcher Settings

Back up the active UserData folder after closing Flow Launcher. That folder contains the configuration and plugin data associated with the instance you.

Package information and verification