## Summary
The Kimi desktop app (GUI) on Windows crashes immediately on launch (flashes the window and exits) as long as the **GameViewer Virtual Display Adapter** is present on the system. The app never reaches the main UI. Removing / disabling the virtual display adapter makes Kimi start normally, so the root cause is an incompatibility between Kimi’s rendering/windowing layer and this virtual display adapter — not a Kimi account or network issue.
## Environment
- OS: Windows 11 专业版, build 26200 (10.0.26200)
- Kimi Desktop: 3.1.3 (Windows, installed from official source)
- Conflicting driver: GameViewer Virtual Display Adapter, driver 15.6.5.199 (dated 2026-02-28), manufacturer/provider “GameViewer”
- Source of the driver: NetEase “UU远程” (UU Remote) v4.33.0.8907 installs and enables this adapter automatically.
- Other GPU: AMD Radeon™ Graphics (driver 31.0.21924.61) — the physical adapter works fine; only the GameViewer virtual adapter triggers the crash.
- Reproduces on every launch while the adapter is enabled; reproducible 100%.
## Steps to reproduce
1. Install NetEase UU远程 (or any product that ships the GameViewer Virtual Display Adapter). Confirm it appears under Settings → System → Display adapters / Device Manager as “GameViewer Virtual Display Adapter”.
2. Launch Kimi Desktop 3.1.3.
3. Observed: the Kimi window briefly appears and then the process exits (crash to desktop). No error dialog from Kimi; no main UI is reachable.
4. Disable the GameViewer Virtual Display Adapter in Device Manager (or uninstall UU远程), then launch Kimi again.
5. Observed: Kimi starts and runs normally.
## Expected behavior
Kimi Desktop should tolerate a virtual display adapter being present and fall back to the primary physical display, instead of crashing. Other Electron/Chromium-based apps on the same machine run fine alongside this adapter.
## Actual behavior
Kimi crashes during startup while the GameViewer virtual adapter is active. The only workaround is to disable/uninstall the adapter, which forces the user to choose between Kimi and UU远程 — not acceptable for users who need both.
## Likely cause (guess)
Kimi’s display enumeration / GPU selection at startup probably assumes a real adapter or fails to handle a virtual display adapter’s reported modes/edid, and an unhandled exception during window creation terminates the process. A defensive fallback (“skip adapters that fail to initialize, use the primary monitor”) should resolve it.
## Request
Please treat virtual display adapters (GameViewer and similar — these are increasingly common with remote‑desktop / game‑streaming products) as a supported environment and add a graceful fallback so Kimi can launch without requiring the user to disable them. A crash log / minidump would help — happy to provide one if you point me at where Kimi writes crash dumps on Windows.
Thank you!
