Keypirinha Problems & Issues

Real user-reported problems, complaints, and limitations for Keypirinha. Based on analysis of 12 signals.

Overall score: 48/100

Issues by Category

support2 issues

Is Keypirinha dead? No update since November 2020

The latest release, v2.26, is dated 2020-11-08 in the official changelog and AlternativeTo now marks the app as discontinued. GitHub issues filed in 2025 and 2026 receive no maintainer reply.

Frequency: 9%Sentiment: -0.70/1003 sources
Impact
8

Author's 2023 'call for help' never led to a new version

In January 2023 the author pinned an issue saying he cannot keep up alone without being paid and listed Windows 11 support, GUI work and a newer Python as priorities. Users kept asking for progress in 2025 and 2026 with no visible answer.

Frequency: 7%Sentiment: -0.60/1002 sources
Impact
7
usability2 issues

Keypirinha hotkey stopped working (Alt+Space does nothing)

Users report custom hotkeys like Alt+Space or Right Alt silently stop responding, sometimes after a Windows 11 upgrade, and non-default hotkeys fail if the app starts under a non-Latin keyboard layout. Workarounds involve finding the conflicting app or proxying the key through AutoHotkey.

Frequency: 6%Sentiment: -0.60/1003 sources
Impact
7

Keypirinha not finding files or folders

By default the Apps package indexes Start Menu items, so files elsewhere don't appear. Users must add extra_paths with the ** wildcard, and a single * or trailing backslash limits what gets indexed.

Frequency: 6%Sentiment: -0.40/1002 sources
Impact
5
integrations2 issues

Microsoft Store (UWP) apps don't show up in Keypirinha

The most-discussed GitHub issue (42 comments, open since 2016) is that Store apps aren't cataloged natively. Users rely on the community WindowsApps package or shell:AppsFolder shortcuts.

Frequency: 7%Sentiment: -0.50/1002 sources
Impact
6

Built-in plugins break as other software changes

Open issues include the Bookmarks plugin failing to read Firefox profiles and Wikipedia web suggestions failing with a certificate error. With no releases, these stay unfixed.

Frequency: 3%Sentiment: -0.40/1002 sources
Impact
3
customization2 issues

Embedded Python 3.7 limits modern plugins

v2.25 upgraded the internal interpreter to Python 3.7.4 and nothing newer has shipped, so plugin authors are stuck on an old Python. The author lists a newer plugin language version among unfinished priorities.

Frequency: 4%Sentiment: -0.40/1002 sources
Impact
4

Limited theming and no calculation history

AlternativeTo reviewers mention very limited theming, and a request to save calculation history has stayed open since 2020.

Frequency: 3%Sentiment: -0.30/1002 sources
Impact
3
onboarding1 issue

Configured only through ini files, steep learning curve

There is no settings window: everything is edited in Keypirinha.ini and per-package ini files. AlternativeTo reviewers call it hard to configure and not intuitive, and the official FAQ says the minimal UI targets advanced users.

Frequency: 7%Sentiment: -0.40/1003 sources
Impact
5
reliability1 issue

Windows 11 glitches: icons missing, catalog not refreshing

Open 2022 issues report icons not displaying on Windows 11 and newly added commands not appearing after a catalog refresh. A maintainer said the icon bug is in the core and could take a while; neither has a fix.

Frequency: 4%Sentiment: -0.50/1002 sources
Impact
5
security1 issue

Closed source and unsigned executable flagged by CrowdStrike

A 2023 issue reports CrowdStrike flagging Keypirinha.exe for contacting a web service; the connection came from the community PackageControl plugin, and the report notes the exe has no valid signature. Only the plugins and Python API are open source.

Frequency: 3%Sentiment: -0.40/1002 sources
Impact
5
performance1 issue

Keypirinha lags after a long idle period

A March 2026 report describes the launcher freezing for several seconds on first use after an hour or more idle, possibly tied to sleeping drives. It has no response.

Frequency: 3%Sentiment: -0.40/1001 sources
Impact
4

Regret Patterns

Common reasons users regret choosing Keypirinha.

Investing in a config for a dead project

Users spend hours tuning ini files and plugins, then realize no fixes are coming when something breaks after a Windows update.

Frequency: 6%After the first Windows feature update that breaks something

Hotkey breaks with no one to ask

When the launch hotkey stops responding, GitHub issues get answers only from other users, so people fall back to AutoHotkey or switch launchers.

Frequency: 5%Months to years in

Store apps never show up

Users moving from the Start menu expect Store apps like Calculator or Windows Terminal to be found and need a community package or manual shortcuts.

Frequency: 5%First week

Learning curve with no settings window

New users expect a preferences dialog and find only ini files, which pushes many to Flow Launcher or PowerToys.

Frequency: 5%First day

Blocked by company security tools

An unsigned, closed-source exe making network calls through plugins can be flagged by EDR tools on work machines.

Frequency: 3%When installed on a managed PC

When Keypirinha Breaks Down

Specific scenarios where Keypirinha fails or underperforms.

Windows 11 upgrade

Reports include hotkeys that stop registering, icons that don't render and catalog changes that don't appear, with no maintainer fix.

Another tool grabs Alt+Space

PowerToys Run and other apps can bind the same global hotkey at OS level, leaving Keypirinha silent.

Non-Latin keyboard layout at startup

Custom hotkeys can fail with 'Malformed Run hotkey' if Keypirinha starts while a layout like Russian is active.

Package managers that strip files

A Chocolatey cleanup feature once deleted python\lib.zip and caused 'Initialization aborted' on every start.

Everything 1.5 alpha

Everything 1.5 alpha runs under a separate '1.5a' instance by default, which tools looking for the standard instance can miss.

Plugins needing modern Python

Packages depending on libraries that need newer Python than the embedded 3.7 can't run.