Windows AMD64 native binary crashes with STATUS_ILLEGAL_INSTRUCTION

Service

Floci CLI — Windows AMD64 native executable

AWS API Action

Not applicable. The CLI crashes during startup before an AWS API operation is executed.

Expected behavior

The Windows AMD64 native executable should start normally and execute CLI commands such as:

floci.exe version

It should return the Floci CLI/server version information.

Likewise, an unsupported command or argument should result in a normal CLI error/help response rather than a Windows process-level crash.

Actual behavior

The native Windows AMD64 executable exits immediately without producing any output.

Running:

floci.exe version

returns to the PowerShell prompt with the following exit code:

-1073741795

This corresponds to:

0xC000001D
STATUS_ILLEGAL_INSTRUCTION

The same behavior occurs with:

floci.exe --version

No Floci error message, stack trace, help output, or version information is displayed.

The failure appears to occur during native application startup, before normal CLI argument processing.

Reproduction

Install Floci using the official Windows installer:

iwr https://floci.io/install.ps1 | iex

Then run:

floci.exe version
$LASTEXITCODE

Result:

-1073741795

Equivalent Windows status:

0xC000001D
STATUS_ILLEGAL_INSTRUCTION

The executable was also invoked directly rather than through PATH, so this does not appear to be a PATH-related issue.

The same result occurs with:

floci.exe --version
$LASTEXITCODE

Environment

• Floci version / image tag: Windows AMD64 native release
• Floci CLI: floci-io/floci-cli
• Operating system: Windows 11 Pro 64-bit
• CPU: Intel Pentium G3250 @ 3.20 GHz
• CPU architecture: x86-64 / AMD64
• Java SDK version (if applicable): Not applicable — testing the native executable
• How you're running Floci: Windows native executable installed using the official PowerShell installer

Additional information

The system correctly reports the processor as a 64-bit x86-64/AMD64 CPU:

Intel(R) Pentium(R) CPU G3250 @ 3.20GHz
Manufacturer: GenuineIntel
Architecture: x86-64 / AMD64
AddressWidth: 64

The executable is successfully downloaded by the installer and can be launched by Windows, but terminates immediately with STATUS_ILLEGAL_INSTRUCTION.

This may indicate that the published Windows AMD64 native executable was built with a CPU instruction-set requirement that is not available on this processor.

Could the Windows native-image build configuration and CPU compatibility baseline be checked?

In particular:

• What minimum x86-64 CPU/instruction-set level is required by the Windows AMD64 binary?
• Is the binary expected to support Haswell-era Intel processors?
• Are any GraalVM Native Image CPU-specific build options enabled?
• Could the Windows AMD64 release be built against a more broadly compatible CPU baseline?
• Could native Windows binaries be tested against older x86-64 processors as part of the release process?

If newer CPU instructions are intentionally required, documenting the minimum CPU requirements for the Windows AMD64 release would also be helpful.

Related links

• Floci: https://github.com/floci-io/floci
• Floci CLI: https://github.com/floci-io/floci-cli
• Windows installer: https://floci.io/install.ps1