[Windows] App crashes before window creation on startup - DuckDB node-bindings missing, 403 on artifact server

### Is there an existing issue for this? - [x] I have searched the tracker for existing similar issues and I know that duplicates will be closed ### Describe the Issue ## Environment - Postman version: 12.9.7 - OS: Windows 11 (win32-10.0.26200), x64 - Also reproduced on: Windows 10 (second machine, same account) - Hardware: Intel i7-1165G7, NVIDIA GTX 1650 Ti + Intel Iris Xe (dual GPU) - WSL: active - Docker Desktop: 4.72.0 (installed, not running during tests) ## Description Postman starts (visible in Task Manager), but **never creates a visible window** (`MainWindowHandle = 0`). No Error/Critical entries in Windows Event Viewer. App must be killed via Task Manager. Reproducible 100% of the time after login. ## Root Cause (investigated) The app crashes during DuckDB singleton initialization, **before BrowserWindow is created**. Log always terminates after: - [PerformanceTestV2] [DuckDBService] Using centralized DB path: C:\Users...\duckdb\results.db - [PerformanceTestV2] [DuckDBService] Created new singleton instance with global guard ASAR analysis confirms the app requires `@duckdb/node-bindings-win32-x64` (via `PKG_BINDING_MAP`), but this native `.node` addon is **not bundled** in the installation and is not present anywhere under `app-12.9.7/`. The artifact download server returns **HTTP 403** for all requests: - `https://performance-test-artifacts.getpostman.com/` → 403 - All guessed duckdb paths → 403 This creates a **chicken-and-egg problem**: DuckDB bindings require auth to download, but the app crashes before the auth/login flow can complete. ### Steps To Reproduce 1. Fresh install of Postman 12.9.7 on Windows 11 2. Clear all AppData (Roaming + Local) including duckdb folder 3. Launch Postman.exe 4. App appears in Task Manager, no window is shown 5. Killing and relaunching shows same behavior ### Screenshots or Videos _No response_ ### Operating System Windows ### Postman Version 12.9.7 ### Postman Platform Postman App ### User Account Type Signed In User ### Additional Context? - Behavior is identical whether logged in or not (tested with `--new-window` flag) - `NODE_TLS_REJECT_UNAUTHORIZED=0` has no effect - `--disable-gpu` flags have no effect - `POSTMAN_DUCKDB_PATH` env variable is ignored at runtime - Reverting to Postman 11.x resolves the issue (no DuckDB dependency) - `Resolve-DnsName performance-test-artifacts.getpostman.com` resolves correctly ## Expected Behavior DuckDB bindings should either be bundled with the installer, or the app should gracefully handle missing bindings (disable Performance Testing feature) instead of crashing before window creation. ## Workaround Downgrade to Postman 11.x (last confirmed working: 11.94.0).