Windows 11: OpenCode Desktop crashes on launch with repeated GPU process failures (0x80000003)

[mrcgvr]

I cannot launch OpenCode Desktop normally on my Windows 11 PC. The application starts, but the window disappears before it becomes usable. The log shows the GPU child process crashing repeatedly with exit code -2147483645 (0x80000003).

Environment
OpenCode Desktop: 1.18.26.0, updated from 1.18.25
Windows 11 Pro 64-bit, build 26200.9278
AMD Ryzen 5 8600G with Radeon 760M Graphics
AMD driver: 32.0.31041.1004, dated 2026-08-17
Plugins: none
The normal reproduction uses the Windows shortcut, not a terminal
Steps to reproduce
Close any existing OpenCode process.
Launch OpenCode Desktop from the normal Windows shortcut, without command-line flags.
Wait for the application window.
The window disappears or never becomes usable.
The log shows a GPU process crash with exitCode: -2147483645.
Expected behavior
OpenCode Desktop should open a stable and usable window.

What I tried
I updated the application, cleared OpenCode caches, tested a clean profile, tried disabling GPU acceleration, and temporarily closed background overlay applications. None of these produced a reliable normal launch.

The only command that consistently opened a window was:

--no-sandbox --disable-gpu --disable-gpu-compositing

I stopped using it because disabling the sandbox reduces security. The OpenCode CLI server works on 127.0.0.1, but I need the Desktop application.

Related issues
I agree this may be a duplicate of #36383, which has the same GPU crash code on Windows. It also appears related to #37906, although that issue describes a different user-profile situation.

My system uses an AMD Radeon 760M, and the problem continued after updating to OpenCode 1.18.26. If this report should be tracked in #36383 instead, please close this issue and I will add these details there.

[github-actions]

Thanks for updating the issue! The report now includes the key details (environment, version, symptoms, and error code) needed to investigate. We appreciate you taking the time to revise it.

[mrcgvr]

Hey everyone, wanted to share how I finally got the desktop app working on Windows 11 after running into the silent crash / blank window.

Like others in this thread, my first instinct was to check the GPU because the logs kept pointing to:
Child process crashed (type: 'GPU', exitCode: -2147483645) followed by GPU process isn't usable. Goodbye.

Turns out the GPU is a complete red herring (my Radeon 760M / drivers are totally fine). The exit code -2147483645 is actually 0x80000003 (STATUS_BREAKPOINT). On recent Windows 11 builds with VBS/HVCI on, Chromium's sandbox trips up on child process initialization, crashes 5 times, and Chromium then gives up and blames the GPU process.

However, just passing --no-sandbox wasn't enough on its own—the app opened to a blank/invisible window. After digging into app.asar, I found the real blocker:

In the root package.json, "type": "module" is set. But out/preload/index.js was compiled using CommonJS (require("electron")). Because of the ESM declaration, Node throws:
ReferenceError: require is not defined in ES module scope

This kills the preload bridge before window.electron gets exposed, so the frontend hangs, ready-to-show never triggers, and the window stays hidden forever.

Here is the quick patch that got it running 100% for me:

1. Unpacked resources/app.asar using npx asar extract app.asar app_extracted.
2. Created an out/preload/package.json with { "type": "commonjs" } and renamed/copied index.js to index.cjs.
3. Updated out/main/index.js to point the preload to ../preload/index.cjs and added app.commandLine.appendSwitch("no-sandbox") at the start of index.js.
4. Repacked the asar (npx asar pack app_extracted app.asar).

After repacking, the app launches instantly with full hardware acceleration enabled and no issues opening or closing.

Hope this helps anyone stuck on this, and hopefully the team can adjust the preload build target (e.g. outputting .cjs or scoping its package.json) in the next release!