Precompiled mod download failure leaves the install modal stuck at "Installing..." with no error
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- backend, observability
Research direction
Start by tracing the precompiled mod download path and how its result reaches the install modal; the issue does not name the relevant files or tests. Reproduce with a precompiled mod download failure, then check whether the failure is logged and reported to the UI and the modal exits "Installing...". The issue describes the expected behavior but leaves the timeout and error-handling details to determine.
Written by the indexing model from the issue text.
Description
Windhawk version: 1.7.3 (UI 1.74.2, commit d2c422c) Windows version: Windows 11 25H2 (build 26200) Affected mods: windows-11-taskbar-styler 1.10, taskbar-labels 1.5.1
Steps to reproduce
Open the page of a mod from the Windhawk repository and click "Install".
Accept the warning ("Accept risk and install").
The modal keeps showing "Installing..." and never completes.
Expected behavior
If the precompiled mod download fails, the installation should time out and report an error (and log it), instead of leaving the modal open indefinitely.
Actual behavior
The modal stays open forever; no error is shown to the user.
Nothing is written to renderer.log or exthost.log.
The extension host is idle: 0% CPU, no open sockets.
Two TCP connections to mods.windhawk.net:443 open and close within about 0.5 s (the DLL and versions.json requests), and then nothing happens.
No DLL is written to C:\ProgramData\Windhawk\Engine\Mods\64 and no registry entry is created.
The same URLs return HTTP 200 with a standard HTTP client on the same machine:
https://mods.windhawk.net/mods/windows-11-taskbar-styler/1.10_64.dll
(2.3 MB)
https://mods.windhawk.net/mods/windows-11-taskbar-styler/versions.json
(1.2 KB)
Workaround
Enabling Settings → "Always compile mods locally" lets the installation succeed: clang++ compiles the mod for about 47 seconds and it is installed and injected normally. This suggests that the problem is specific to the precompiled-binary download path or to how failures of that path are handled.
Suggestion
Add a timeout and surface (and log) the failure in the UI, so that a failed download does not leave the installation in an indefinite "Installing..." state.
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 246
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ramensoftware/windhawk
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ramensoftware/windhawk#1164 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ramensoftware/windhawk#1156 · 2 comments ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ramensoftware/windhawk#1089 · 3 comments ·
-
bug info-needed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ramensoftware/windhawk#1046 · 2 comments ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ramensoftware/windhawk#382 · 3 comments · 2 reactions ·
All issues in ramensoftware/windhawk
Similar issues
-
ai_p2 bug comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ClickHouse/ClickHouse#128306 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area:cli bug priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day