[Bug] Tabby Portable 1.0.234 startup hang on Windows 10 22H2 — crashpad initialization fails with ERROR_FILE_NOT_FOUND (0x2)

<!-- # READ CAREFULLY: * **ENGLISH ONLY** - this issue tracker is English-only. Please respect the people who take time to help you with your problems. * Search existing issues first: https://github.com/Eugeny/tabby/issues * Test with the latest Tabby version: https://github.com/Eugeny/tabby/releases * Disable third-party plugins. --> **Describe the problem**: ### Description Tabby Portable 1.0.234 fails to start on Windows 10 Professional 22H2. The application window appears but remains stuck on the loading screen indefinitely. ### Environment - **Tabby Version:** 1.0.234 (Portable) - **OS:** Windows 10 Professional 22H2 - **Installation Type:** Portable (extracted from release archive) ### Steps to Reproduce 1. Extract `tabby-1.0.234-portable.zip` to `D:\Tools\Tabby\` 2. Double-click `Tabby.exe` to launch 3. Application window opens but stays on the loading screen 4. Check Task Manager: only 1 `Tabby.exe` process initially 5. Force-close via Task Manager, relaunch → 3 processes 6. Force-close again, relaunch → 5 processes (accumulating) ### Expected Behavior Application should complete initialization and show the main terminal interface. ### Actual Behavior - Window stuck on loading screen - Process count increases by 2 with each restart (main + renderer/GPU processes not cleaning up) - `debug.log` shows crashpad initialization error ### Debug Log ``` [0521/110723.198:ERROR:third_party\crashpad\crashpad\util\win\registration_protocol_win.cc:108] CreateFile: 系统找不到指定的文件。 (0x2) ``` ### Additional Context - Tried running as Administrator → same result - Tried `--disable-gpu` and `--no-sandbox` flags → same result - No antivirus interference detected (Windows Defender only) - `crashpad_handler.exe` exists in the Portable directory - Clearing `%TEMP%\Tabby*` and `%TEMP%\crashpad*` did not resolve ### Possible Cause Crashpad (Electron crash reporter) fails to initialize its registration protocol on Windows 10 22H2, possibly due to named pipe creation failure or missing runtime dependencies. The error blocks the main process initialization instead of gracefully disabling crash reporting. ### Workarounds Attempted - Setting `ELECTRON_DISABLE_CRASHPAD=1` → **not yet tested** (will update) - Moving to different directory → **not yet tested** --- **Labels:** `bug`, `windows`, `crash`, `portable`