Crash during startup in Windows

[ysfsmet]

Description

I installed it on my computer for the first time. The onboarding screen completed successfully. When I launch the program, it closes on its own after a few seconds. Before it closes, an orange border appears around the edges of all the windows on the desktop.

Reproduction

• Launch the program

Additional Context

• Cap version: 0.4.84.0
• Operating system, version: Win 11 25H2 26200.8246
• Device (optional):
• EventViewerLog: Faulting application name: Cap.exe, version: 0.4.84.0, time stamp: 0x69df9148
  Faulting module name: ntdll.dll, version: 10.0.26100.8246, time stamp: 0xf7576e9e
  Exception code: 0xc0000374
  Fault offset: 0x0000000000117555
  Faulting process id: 0xD970
  Faulting application start time: 0x1DCD897691AFE23
  Faulting application path: C:\Users\Yusuf\AppData\Local\Cap\Cap.exe
  Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
  Report Id: f904b768-f5b2-4c3b-9475-bc8f39f3e0a3
  Faulting package full name:
  Faulting package-relative application ID:

Not available logs folder in the AppData

[linear]

CAP-698

[tembo]

Some context that might help debug this:

The exception code 0xc0000374 is STATUS_HEAP_CORRUPTION, which typically indicates memory corruption in native code. The "orange border appearing around all windows" you're describing sounds like the Target Select Overlay UI that Cap displays when preparing to select a recording target.

Potentially Related Issues and PRs:

• PR #1377 addresses a similar pattern: C++ exceptions being thrown during Windows Graphics Capture API calls (specifically CreateForWindow on invalid HWND handles). That PR hasn't been merged yet but adds catch_unwind wrappers to handle these cases gracefully.
• Issue #1099 reported a similar "open and crash" behavior on Windows 11 with version 0.3.67.
• Issue #1234 mentions the Target Select Overlay taking a long time to load on Windows, which uses the same screen capture initialization path.

Relevant Code Paths:

• The main window/onboarding flow is in apps/desktop/src-tauri/src/lib.rs around line 3980, where after completing onboarding, the main window is shown.
• Screen capture initialization happens through scap-direct3d crate (crates/scap-direct3d/src/lib.rs) and scap-targets (crates/scap-targets/src/platform/win.rs).
• Thumbnail generation for displays/windows uses the capture API in apps/desktop/src-tauri/src/thumbnails/windows.rs - this could trigger during startup when populating the target selection UI.

Debugging Suggestions:

• The logs directory on Windows should be at %LOCALAPPDATA%\so.cap.desktop\logs (not in Roaming AppData). If that folder doesn't exist, the crash might be happening before logging is initialized (main.rs lines 53-72).
• Running Cap from a command prompt might show crash output before the logging system initializes.
• Windows 11 25H2 is a relatively recent version - there could be API behavior changes affecting the Windows Graphics Capture API.

The heap corruption combined with the overlay appearance suggests the crash might be happening during display enumeration or capture item creation for the target selection overlays.