Windows Background upgrade corruption issue #9162

Open
opened 2026-02-16 18:11:47 -05:00 by yindo · 1 comment
Owner

Originally created by @rtkelly13 on GitHub (Feb 12, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

I was developing on two different instances of opencode. One crashed, not sure why, so I restarted the session and got the following error.

spawnSync C:\Users\ryan.kelly\AppData\Roaming\fnm\node-versions\v24.13.0\installation\node_modules\opencode-ai\node_modules\opencode-windows-x64\bin\opencode.exe EFAULT

I resolved it by closing down the other opencode session and running the following

npm uninstall -g opencode-ai; npm install -g opencode-ai

Plugins

oh-my-opencode

OpenCode version

1.1.60

Steps to reproduce

I think this one might be hard to directly reproduce now that I've fixed it.

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

Windows Terminal

Originally created by @rtkelly13 on GitHub (Feb 12, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description I was developing on two different instances of opencode. One crashed, not sure why, so I restarted the session and got the following error. spawnSync C:\Users\ryan.kelly\AppData\Roaming\fnm\node-versions\v24.13.0\installation\node_modules\opencode-ai\node_modules\opencode-windows-x64\bin\opencode.exe EFAULT I resolved it by closing down the other opencode session and running the following ``` npm uninstall -g opencode-ai; npm install -g opencode-ai ``` ### Plugins oh-my-opencode ### OpenCode version 1.1.60 ### Steps to reproduce I think this one might be hard to directly reproduce now that I've fixed it. ### Screenshot and/or share link _No response_ ### Operating System Windows 11 ### Terminal Windows Terminal
yindo added the windowsbug labels 2026-02-16 18:11:47 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 12, 2026):

This issue might be a duplicate or related to existing issues. Please check:

  • #11648: [Windows] Upgrade embedded Bun runtime from v1.3.5 — LSP broken due to spawn segfault (similar EFAULT spawn error on Windows)
  • #10007: OpenCode start failed after upgrade (similar failure pattern after upgrade)
  • #12598: After upgrading to the latest version of OpenCode, it won't respond/open (similar post-upgrade issue on Windows)

The EFAULT error in your spawnSync suggests this might be related to the Bun runtime issue mentioned in #11648. If your issue persists, the upstream Bun segfault (oven-sh/bun#25798) may be involved.

@github-actions[bot] commented on GitHub (Feb 12, 2026): This issue might be a duplicate or related to existing issues. Please check: - #11648: [Windows] Upgrade embedded Bun runtime from v1.3.5 — LSP broken due to spawn segfault (similar EFAULT spawn error on Windows) - #10007: OpenCode start failed after upgrade (similar failure pattern after upgrade) - #12598: After upgrading to the latest version of OpenCode, it won't respond/open (similar post-upgrade issue on Windows) The EFAULT error in your spawnSync suggests this might be related to the Bun runtime issue mentioned in #11648. If your issue persists, the upstream Bun segfault (oven-sh/bun#25798) may be involved.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9162