User Guide
12.1 · Troubleshooting

Common Issues

Quick reference for the problems users most often report. Hotkey conflicts have their own page (see 12.2); crash reporting is covered in 12.3.

SymptomLikely causeFix
App won't launchx64-only binary; .NET 8 runtime is bundled but the executable may be missing or blockedConfirm Tex.Wpf.exe exists at the installed path; reinstall if missing. The app will not run on 32-bit Windows
Hotkeys don't fireAnother app owns the combination, or the OS is blocking itSee 12.2
OCR first-use is slowLazy Tesseract init takes 2-5 seconds on the first call per sessionExpected; subsequent OCR requests are fast. Leave the app running between captures
Capture is blank or blackDRM'd video, some games, and other protected content are intentionally blocked by WindowsNot a Tex bug. Use the target app's built-in share/record feature instead
Tray icon disappearedWindows Explorer restarted (or crashed) and dropped the icon handleExit Tex from Task Manager and relaunch
Hotkey / theme / notification change ignoredThese apply immediately and should not need a restartIf an immediate change is not visible, re-open the Settings window to force a re-bind
Other settings change ignoredSome settings are read once at startup (e.g. UI.StartMinimized, UI.StartWithWindows, installed OCR language packs)Restart Tex for these to take effect
Recording fails to startHardware encoder (NVENC / QuickSync / AMF) is unavailable or busyIn Settings > Recording, set Recording.UseHardwareEncoding to false to fall back to software encoding
  • 12.2 — Hotkey conflicts
  • 12.3 — Crash reports and logs
  • 10 — Settings and Preferences (for the full settings schema)