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
Failed to stop native Windows recording: Error: Timed out waiting for native Windows capture to stop. Output path: C:\Users\andy\AppData\Roaming\openscreen\recordings\recording-1782409289180.mp4. Output: {"event":"ready","schemaVersion":2}
{"event":"cursor-capture","schemaVersion":2,"requested":true,"applied":true}
{"event":"cursor-capture","schemaVersion":2,"requested":true,"applied":true}
{"event":"recording-started","schemaVersion":2}
Recording started
at Timeout. (file:///C:/Program%20Files/Openscreen/resources/app.asar/dist-electron/main.js:2571:9)
at listOnTimeout (node:internal/timers:605:17)
at process.processTimers (node:internal/timers:541:7)
@Andy-0614 Thanks for the report — sorry you're hitting this.
We dug in and figured out what's happening: when you click Stop, OpenScreen's recording helper does a few cleanup steps internally before it can finalize the file. On your Windows 10 machine, one of those steps is taking longer than 15 seconds, so OpenScreen gives up and the recording is lost. The 15-second timeout is too short (the macOS version uses 30 seconds) — we'll fix that — but we don't yet know which of those steps is the slow one on your hardware. Once we know, we can ship a proper fix instead of just guessing.
What we need from you
We put together a small tool that records for 30 seconds, sends Stop, and saves a report file we can read. Running it on your machine tells us exactly where the slowdown is.
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 Jun 26, 2026
@Andy-0614 Thanks for the report — sorry you're hitting this.
We dug in and figured out what's happening: when you click Stop, OpenScreen's recording helper does a few cleanup steps internally before it can finalize the file. On your Windows 10 machine, one of those steps is taking longer than 15 seconds, so OpenScreen gives up and the recording is lost. The 15-second timeout is too short (the macOS version uses 30 seconds) — we'll fix that — but we don't yet know which of those steps is the slow one on your hardware. Once we know, we can ship a proper fix instead of just guessing.
What we need from you
We put together a small tool that records for 30 seconds, sends Stop, and saves a report file we can read. Running it on your machine tells us exactly where the slowdown is.
cmd, and press Enter. A black terminal window will open.openscreen-diagnostic-<numbers>.jsonin the same folder — to this issue.If anything goes wrong or the download link doesn't appear yet, just reply here and we'll help you through it.
Thanks for sticking with us — once we have the report we should be able to ship a real fix in the next release.
fix(wgc): capture per-step stop timing, bump timeout, add diagnostic …
github-actions commentedon Jun 26, 2026
Fixed by #36 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 Jun 28, 2026
@Andy-0614 did you have a chance to test this :
#34 (comment)
fix(recording): stop a webcam finalize from discarding the screen cap…
fix(recording): stop a webcam finalize from discarding the screen cap…
fix(recording): stop a webcam finalize from discarding the screen cap…