You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Windows] HUD toolbar is visible but completely unclickable after launch (click-through state never clears) #1105
After installing OpenScreen 2.0.0 on Windows 10 and launching it for the first time, the HUD overlay toolbar appears on screen but does not respond to any mouse clicks — it behaves as if it is in click-through mode. Hovering over the buttons shows no highlight. Tray icon and keyboard shortcuts (e.g. Ctrl+Shift+O) also do not respond. The language prompt dialog renders normally, but clicking "Keep current language" or "Switch to 简体中文" does nothing.
Restarting the app does not help — the issue happens every time.
Environment
OS: Windows 10 Pro 22H2, build 19045.6466 (x64)
OpenScreen version: 2.0.0 (installed from GitHub Releases .exe)
CPU: Intel Core i5-13600KF (no iGPU)
GPU: NVIDIA RTX 4060 Ti (driver 32.0.15.6094)
RAM: 32 GB
Displays: 2 physical monitors (AOC Q27G2SD 2560x1440 + Huion Kamvas Pro 19), scaling is 100% on both
Steps to Reproduce
Install OpenScreen 2.0.0
Launch the app
Try to click anything on the HUD toolbar → no response
Expected behavior
The HUD toolbar should become interactive after launch.
Actual behavior
The toolbar stays permanently in a click-through / non-interactive state, although it renders correctly.
Sorry, I accidentally closed this issue while editing my comment — reopened it.
To summarize: the test confirms the content protection on the HUD window is what blocks mouse input on this machine. Test results and log are above. Happy to test a fix build whenever you have one.
This change is assigned to the Next Release release milestone and is not necessarily available in the latest downloadable desktop release yet. It is currently marked as status: pending release until a packaged release containing it is published.
Activity
EtienneLescot commentedon Oct 10, 2026
Thanks for the detailed report. Could you try this from
cmdto confirm the cause:Is the bar clickable then? Please attach
openscreen.logeither way. Also: does a right-click on the tray icon open its menu?homeyang02 commentedon Oct 10, 2026
Results of the test:
OPENSCREEN_DISABLE_CONTENT_PROTECTION=1, the HUD toolbar is fully clickable — all buttons respond normally and hover works.So the content protection applied to the HUD window is what eats the mouse input on this machine.
Log attached. Happy to test a fix or any other experiment you need.
openscreen.log
homeyang02 commentedon Oct 10, 2026
Sorry, I accidentally closed this issue while editing my comment — reopened it.
To summarize: the test confirms the content protection on the HUD window is what blocks mouse input on this machine. Test results and log are above. Happy to test a fix build whenever you have one.
docs: document the Windows 10 workaround for an unclickable recording…
EtienneLescot commentedon Oct 10, 2026
Thanks @homeyang02, that confirms it. A fix is on its way for the next release. Until then the workaround is in the FAQ, for both the installer and the Store version: https://getopenscreen.com/docs/faq#why-cant-i-click-the-recording-bar-on-windows-10
github-actions commentedon Oct 10, 2026
Fixed by #1109 and merged into
main.This change is assigned to the
Next Releaserelease milestone and is not necessarily available in the latest downloadable desktop release yet. It is currently marked asstatus: pending releaseuntil a packaged release containing it is published.EtienneLescot commentedon Oct 10, 2026
@homeyang02 here is a test build with the fix (#1109): https://github.com/getopenscreen/openscreen/actions/runs/38085096429. Download the
openscreen-windows-x64artifact (you need to be signed in to GitHub). The installer isn't signed, so SmartScreen will ask: More info → Run anyway.Please launch it normally, without the
OPENSCREEN_DISABLE_CONTENT_PROTECTIONvariable, and check two things:homeyang02 commentedon Oct 10, 2026
Tested the build from the Actions artifact - both checks pass:
OPENSCREEN_DISABLE_CONTENT_PROTECTION.The fix works on my machine (Windows 10 22H2, 19045.6466, RTX 4060 Ti, 2 displays). Thanks a lot for the quick turnaround!
EtienneLescot commentedon Oct 15, 2026
Moved into
v2.1.0as part of the pre-release cut.docs(website): align the site with OpenScreen 2.1.0