claude-code - 💡(How to fix) Fix [BUG] AVX detection issue on c7i.xlarge instance preventing execution [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52117Fetched 2026-04-23 07:36:11
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×5commented ×1

Error Message

Error Messages/Logs

Code Example

============================================================
Bun v1.3.13 (6db6c97b) Windows x64 (baseline)
Windows v.win10_rs5
Args: "C:\Users\Administrator.EC2AMAZ-MC579PT\.claude\downloads\claude-2.1.117-win32-x64.exe" "install" "latest"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) jsc no_avx2 no_avx spawn(2) standalone_executable yaml_parse claude_code 
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/posix" "node:path/win32" "node:perf_hooks" "node:process" "node:stream" "node:stream/consumers" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:vm" "node:zlib" "ws" "node:http2"
Elapsed: 481ms | User: 453ms | Sys: 171ms
RSS: 0.33GB | Peak: 0.33GB | Commit: 0.46GB | Faults: 82140 | Machine: 33.81GB

CPU lacks AVX support. Please consider upgrading to a newer CPU.
panic(main thread): Segmentation fault at address 0xE0

panic: Segmentation fault at address 0x0
panicked during a panic. Aborting.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Claude crashes complaining CPU lacks AVX support while the c7i.large instance being used clearly has such instructions.

What Should Happen?

Claude should start but instead crashes complaining about missing AVX instructions on a CPU that clearly has such instructions.

Error Messages/Logs

============================================================
Bun v1.3.13 (6db6c97b) Windows x64 (baseline)
Windows v.win10_rs5
Args: "C:\Users\Administrator.EC2AMAZ-MC579PT\.claude\downloads\claude-2.1.117-win32-x64.exe" "install" "latest"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) jsc no_avx2 no_avx spawn(2) standalone_executable yaml_parse claude_code 
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/posix" "node:path/win32" "node:perf_hooks" "node:process" "node:stream" "node:stream/consumers" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:vm" "node:zlib" "ws" "node:http2"
Elapsed: 481ms | User: 453ms | Sys: 171ms
RSS: 0.33GB | Peak: 0.33GB | Commit: 0.46GB | Faults: 82140 | Machine: 33.81GB

CPU lacks AVX support. Please consider upgrading to a newer CPU.
panic(main thread): Segmentation fault at address 0xE0

panic: Segmentation fault at address 0x0
panicked during a panic. Aborting.

Steps to Reproduce

Run Claude on a c7i.xlarge AWS instance with Windows Server 2022

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

claude-2.1.117

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

extent analysis

TL;DR

The issue can likely be resolved by ensuring the CPU architecture is correctly detected or by using a version of Claude that does not require AVX support.

Guidance

  • Verify that the c7i.large instance's CPU indeed supports AVX instructions and that the operating system and Claude Code version are correctly configured to utilize these instructions.
  • Check if there's an option or configuration in Claude Code to disable AVX requirement or to use a fallback for CPUs without AVX support.
  • Investigate if there's a known issue with CPU detection in the version of Claude Code being used (claude-2.1.117) and if there are any patches or updates available.
  • Consider testing Claude Code on a different environment or version to isolate if the issue is specific to the current setup or a regression in the software.

Example

No specific code example can be provided without more details on Claude Code's configuration options or internal workings.

Notes

The provided error message suggests a segmentation fault which could be related to the AVX support issue but might also indicate other problems. Without more specific details about Claude Code's internals or configuration, providing a precise fix is challenging.

Recommendation

Apply workaround: Given the information, trying to disable AVX requirement or using a different version of Claude Code that might not rely on AVX instructions could be a viable temporary solution until a more permanent fix is found.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] AVX detection issue on c7i.xlarge instance preventing execution [1 comments, 2 participants]