Skip to content

After upgrading to the latest version of OpenCode, it won't respond/open. Help!! #12598

Closed

Description

@freewinder-tech

Question

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!

Activity

  1. github-actions commented on Feb 7, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    Feel free to ignore if none of these address your specific case.

  2. freewinder-tech commented on Feb 7, 2026

    @freewinder-tech
    Author

    D:\op-test>opencode run hello --print-logs

    D:\op-test>
    no response

  3. Casperlet commented on Feb 7, 2026

    @Casperlet

    Me too.

    Please rollback the opencode to the old version 1.1.51. It works again now.

  4. Afonsojr commented on Feb 7, 2026

    @Afonsojr

    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:

    1. Install OpenCode v1.1.53 on a system with an Intel Ivy Bridge (or older) processor
    2. Run opencode --version or opencode
    3. 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:

    1. Compile release binaries with a baseline x86-64 instruction set (SSE2/SSE3) without AVX2
    2. Provide separate binaries for legacy CPUs (e.g., opencode-windows-x64-legacy.zip)
    3. 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

  5. freewinder-tech commented on Feb 7, 2026

    @freewinder-tech
    Author

    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.

  6. BassemN commented on Feb 8, 2026

    @BassemN

    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.

  7. Casperlet commented on Feb 11, 2026

    @Casperlet

    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.

  8. adamdotdevin commented on Feb 12, 2026

    @adamdotdevin
    Member

    @Afonsojr @BassemN @Casperlet @freewinder-tech can you upgrade to latest (1.1.64) and let me know if this is resolved?

  9. BassemN commented on Feb 12, 2026

    @BassemN

    @adamdotdevin Unfortunately, in my case, the issue is still there even in version 1.1.63.

  10. adamdotdevin commented on Feb 13, 2026

    @adamdotdevin
    Member

    @adamdotdevin Unfortunately, in my case, the issue is still there even in version 1.1.63.

    sorry, 1.1.64 any better?

  11. Casperlet commented on Feb 13, 2026

    @Casperlet

    not work even 1.1.64

  12. BassemN commented on Feb 13, 2026

    @BassemN

    @adamdotdevin Good news! I can now access Opencode via the terminal after updating to version 1.1.65

  13. BassemN commented on Feb 13, 2026

    @BassemN

    @Casperlet, it worked for me after updating to version 1.1.65. Try updating like I did and see if it resolves the issue.

  14. Casperlet commented on Feb 13, 2026

    @Casperlet

    @BassemN yes, the 1.1.65 works, thanks.

  15. RobLoach commented on Feb 13, 2026

    @RobLoach

    Confirming 1.1.65 fixes it. Nice work!

  16. fluidum commented on Jun 26, 2026

    @fluidum

    v1.1.30 works with i7-4770, but not 1.1.65

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions