You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
After upgrading to the latest version of OpenCode, it won't respond/open. Help!! #12598
I just updated to the latest version of OpenCode(v1.1.53),my os is win10, but now it won't launch. Clicking the icon does nothing, and there's no output when running the command in PowerShell or CMD. Any help would be appreciated!
Title: OpenCode crashes with STATUS_ILLEGAL_INSTRUCTION on older Intel CPUs (pre-Haswell)
Description:
OpenCode fails to run on systems with older Intel processors (Ivy Bridge and earlier) due to the use of CPU instructions not supported by these processors. The application crashes immediately without any error message or output.
Install OpenCode v1.1.53 on a system with an Intel Ivy Bridge (or older) processor
Run opencode --version or opencode
The application exits immediately with no output
Expected Behavior:
OpenCode should start normally or display a clear error message about CPU compatibility.
Actual Behavior:
The application crashes silently. When run from terminal, it returns exit code -1073741795 (0xC000007D = STATUS_INVALID_IMAGE_FORMAT) or -1073741510.
Windows Event Log Analysis:
Root Cause:
The exception code 0xc000001d (STATUS_ILLEGAL_INSTRUCTION) indicates that the binary contains CPU instructions not supported by the processor. This is likely due to the binary being compiled with AVX2 or other instruction set extensions introduced in Intel Haswell (4th gen, 2013) or later.
Workaround:
Downgrading to version v1.1.30 resolves the issue. This suggests that newer versions introduced compiler optimizations targeting modern CPUs.
Version Bisect:
• v1.1.30: ✅ Works
• v1.1.53: ❌ Crashes
Suggested Fix:
Consider one of the following approaches:
Compile release binaries with a baseline x86-64 instruction set (SSE2/SSE3) without AVX2
Provide separate binaries for legacy CPUs (e.g., opencode-windows-x64-legacy.zip)
Use runtime CPU feature detection to provide a meaningful error message
Additional Context:
• The binary is correctly identified as x64 PE format
• Visual C++ Redistributable 14.44 is installed
• WebView2 Runtime 144.0.3719.115 is installed
• The issue affects Scoop installations as well as direct downloads from GitHub releases
npm install -g [email protected],after install ,its version is 1.1.51,but after run opencode,exit,version auto upgrade to 1.1.53,run opencode no response again.
npm install -g [email protected],after install ,its version is 1.1.51,but after run opencode,exit,version auto upgrade to 1.1.53,run opencode no response again.
please edit the opencode.json in the folder ~/.config/opencode, insert the setting "autoupdate": false,, then it will not update again.
Activity
github-actions commentedon Feb 7, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
freewinder-tech commentedon Feb 7, 2026
D:\op-test>opencode run hello --print-logs
D:\op-test>
no response
Casperlet commentedon Feb 7, 2026
Me too.
Please rollback the opencode to the old version 1.1.51. It works again now.
Afonsojr commentedon Feb 7, 2026
Title: OpenCode crashes with STATUS_ILLEGAL_INSTRUCTION on older Intel CPUs (pre-Haswell)
Description:
OpenCode fails to run on systems with older Intel processors (Ivy Bridge and earlier) due to the use of CPU instructions not supported by these processors. The application crashes immediately without any error message or output.
Environment:
• OS: Windows 11 (Build 22631)
• CPU: Intel Core (Ivy Bridge, Family 6 Model 58) - 3rd Generation
• Architecture: x64 (AMD64)
• Shell: PowerShell 7.5.4
• OpenCode Version: v1.1.53 (affected), v1.1.30 (works)
Steps to Reproduce:
Expected Behavior:
OpenCode should start normally or display a clear error message about CPU compatibility.
Actual Behavior:
The application crashes silently. When run from terminal, it returns exit code -1073741795 (0xC000007D = STATUS_INVALID_IMAGE_FORMAT) or -1073741510.
Windows Event Log Analysis:
Root Cause:
The exception code 0xc000001d (STATUS_ILLEGAL_INSTRUCTION) indicates that the binary contains CPU instructions not supported by the processor. This is likely due to the binary being compiled with AVX2 or other instruction set extensions introduced in Intel Haswell (4th gen, 2013) or later.
Workaround:
Downgrading to version v1.1.30 resolves the issue. This suggests that newer versions introduced compiler optimizations targeting modern CPUs.
Version Bisect:
• v1.1.30: ✅ Works
• v1.1.53: ❌ Crashes
Suggested Fix:
Consider one of the following approaches:
Additional Context:
• The binary is correctly identified as x64 PE format
• Visual C++ Redistributable 14.44 is installed
• WebView2 Runtime 144.0.3719.115 is installed
• The issue affects Scoop installations as well as direct downloads from GitHub releases
freewinder-tech commentedon Feb 7, 2026
npm install -g [email protected],after install ,its version is 1.1.51,but after run opencode,exit,version auto upgrade to 1.1.53,run opencode no response again.
BassemN commentedon Feb 8, 2026
I am using Ubuntu 20.04.6 LTS. Opencode was running properly on version 1.1.51, but after upgrading to version 1.1.52 or 1.1.53, it no longer runs.
Casperlet commentedon Feb 11, 2026
please edit the
opencode.jsonin the folder~/.config/opencode, insert the setting"autoupdate": false,, then it will not update again.adamdotdevin commentedon Feb 12, 2026
@Afonsojr @BassemN @Casperlet @freewinder-tech can you upgrade to latest (1.1.64) and let me know if this is resolved?
BassemN commentedon Feb 12, 2026
@adamdotdevin Unfortunately, in my case, the issue is still there even in version 1.1.63.
adamdotdevin commentedon Feb 13, 2026
sorry, 1.1.64 any better?
Casperlet commentedon Feb 13, 2026
not work even 1.1.64
BassemN commentedon Feb 13, 2026
@adamdotdevin Good news! I can now access Opencode via the terminal after updating to version 1.1.65
BassemN commentedon Feb 13, 2026
@Casperlet, it worked for me after updating to version 1.1.65. Try updating like I did and see if it resolves the issue.
Casperlet commentedon Feb 13, 2026
@BassemN yes, the 1.1.65 works, thanks.
RobLoach commentedon Feb 13, 2026
Confirming 1.1.65 fixes it. Nice work!
fluidum commentedon Jun 26, 2026
v1.1.30 works with i7-4770, but not 1.1.65