Repository navigation
[Bug]: v2.0.0 — HUD/language prompt accepts no input on first launch (Windows 10, both .exe and Store builds); #385 rescue doesn't fire #1203
Description
Search existing issues
- I have searched the existing issues
Describe the bug
On first launch, the "Use your system language?" HudNotice renders over the HUD bar. Neither its two buttons nor any other HUD control responds to clicks, even after 3+ minutes. The app must be killed via Task Manager. 100% reproducible on every launch, on both the .exe installer and the Microsoft Store build
Expected behavior
Clicking "Switch to 繁體中文" / "Keep current language" should dismiss the prompt and apply the choice; all HUD buttons should respond to clicks.
To Reproduce
- Install OpenScreen 2.0.0 (.exe or Store build) on Windows 10
- Launch the app (system language: Traditional Chinese)
- The language prompt appears over the HUD bar
- Click either button — nothing responds
Screenshots
No response
OS
Windows
OS Version
Windows 10
Other OS
No response
Browser
None
Browser Version
No response
Other Browser
No response
Device Type
Desktop
Other Device
No response
Additional context
nstallers: Openscreen.Setup.2.0.0.exe (SHA-256 verified f5a8b877…33c899c55) + Microsoft Store build, identical failure
Display scaling 100%
Click-through test confirmed: clicks pass through the HUD overlay window to windows behind; the window is stuck input-transparent
Matches #385's exact config (Win10 + Store/MSIX), closed as fixed. The #385 cursor-poll rescue exists in the v2.0.0 tag (verified in source) but never fires here. Suspect #385 incompletely fixed or regressed.
Activity
solodimekuro commentedon Oct 16, 2026
Same thing happens to me (Spanish system language, Windows 10). Already tried with .exe and Store build. I can't control nor interact withing the HUD and I have to force close the program.
airobotnews commentedon Oct 17, 2026
I fixed this problem using the agent. The submission has been made and the explanation has been provided. #1247
EtienneLescot commentedon Oct 19, 2026
Thanks for the precise report and for checking the source. On Windows 10 before 11 22H2, a content-protected window stays input-transparent, so the click-through HUD never took a click again, and the #385 rescue could not help. v2.1.0 turns the HUD's content protection off on those builds (#1109). Please update to v2.1.2 (the Store updates by itself) and tell us if the language prompt now responds. @solodimekuro the same applies to you.
solodimekuro commentedon Oct 19, 2026
Updated to v2.1.0 and everything works as intended. Thanks for the heads up, @EtienneLescot