Repository navigation
[Bug]: Desktop IPC handler failed — Server process exited with code 3221225785 (0xC0000005) on Windows 10 #51280
Description
Description
Upon launching the OpenCode Desktop app, a "Something went wrong" error screen immediately appears stating that an error occurred while starting the local server. The underlying server process exits with code 3221225785 (0xC0000005 Access Violation), preventing the app from starting.
To Reproduce
Launch OpenCode Desktop on Windows 10.
The splash/loading screen fails to connect to the backend sidecar.
The error screen appears with Desktop IPC handler failed.
Error Logs
Plaintext
Error: Desktop IPC handler failed
at Kt (oc://renderer/assets/main-CPcOeTnu.js:2:30447)
at Gt (oc://renderer/assets/main-CPcOeTnu.js:2:30115)
at MessagePort. (oc://renderer/assets/main-CPcOeTnu.js:2:29120)
────────────────────────────────────────
Caused by:
{
"name": "UnknownError",
"message": "An error occurred in Effect.tryPromise",
"cause": {
"name": "Error",
"message": "Server process exited with code 3221225785"
}
}
Troubleshooting Steps Tried (None Resolved the Issue)
Full System Reset: Completely reset the PC and performed a fresh install of OpenCode Desktop.
Visual C++ Redistributable: Installed/repaired the latest Microsoft Visual C++ Redistributable (x64 v14.51.36247).
Directory Recreation: Manually created the missing %USERPROFILE%.local\share and cleared app data (%APPDATA%\OpenCode, %LOCALAPPDATA%\opencode-desktop, .cache, .config).
Permissions & Antivirus: Executed the setup installer (opencode-desktop-win-x64) as Administrator and temporarily disabled Windows Defender Real-time Protection.
GPU Hardware Acceleration: Added the --disable-gpu flag to the desktop shortcut executable target.
Desktop Environment:
OS: Windows 10 Home/Pro (Version 1709 / Build 16299.1127)
Architecture: x64
Installer Version: opencode-desktop-win-x64.exe
Additional Context
The crash code 3221225785 corresponds to 0xC0000005 (Access Violation), indicating that the bundled local server sidecar binary fails to execute on this specific Windows release build or CPU instruction set during initialization.
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Activity
github-actions commentedon Sep 25, 2026
This issue might be a duplicate of existing issues. Please check:
alexschultze commentedon Oct 16, 2026
I have similar issue, but only on a constrained PC on OpenCode 2. Which version are you on?
opencodejr commentedon Oct 28, 2026
Thanks for the detailed report and for listing everything you've already tried.
One correction that may help: exit code
3221225785is0xC0000139(STATUS_ENTRYPOINT_NOT_FOUND), not0xC0000005. It usually means a program needs a function in a Windows system DLL that this Windows version doesn't have. Your build (Windows 10 1709 / 16299) is from 2017, so the OS version may well be the cause.To narrow it down, could you share:
npm i -g @opencode/cli) and runopencode --versionandopencode servefrom a terminal. Tell us whether it starts, or paste the error or any Windows pop-up about a missing entry point or DLL.You can reply here with the details or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know when you're done.
Related issue (not the same exit code):
0xC0000005on v1.15.x, closed as staleopencodejr commentedon Oct 31, 2026
We're closing this for now because we haven't heard back. We still need the OpenCode Desktop version, the server's error output, and whether
opencode servefrom the CLI fails the same way.The exit code
3221225785(0xC0000139, entry point not found) suggests the server may need a Windows feature that Windows 10 1709 doesn't have, but we can't confirm that without those details. If you can share them, or try a newer Windows 10 build, please comment here or open a new issue and link #51280. Thanks for the report!