microsoft / microsoft/react-native-windows

Release builds are hard-coded to use x86 Hermes, even on ARM Windows

Open
#16,084 0 comments 0 reactions 1 assignee View on GitHub

@vineethkuttan is already working on this.

Since May 12, 2026.

bug Release0.85
Dominant language
C++
Stars
17.3k
Forks
1.2k
Avg merge
1d 13h
Merged PRs (30d)
33

Description

Problem Description

Although debug builds work, release builds on ARM Windows fail as follows:

× Build failed with message C:\Users\jamie\Downloads\MyApp123\node_modules\react-native-windows\PropertySheets\Bundle.Common.targets(22,5): error MSB3075: ???? "C:\Users\jamie.nuget\packages\microsoft.javascript.hermes\0.0.0-2511.7001-d7ca19b3\tools\native\release\x86\hermes.exe -emit-binary -out "C:\Users\jamie\Downloads\MyApp123\windows\MyApp123\Bundle\index.windows.bundle.hbc" "C:\Users\jamie\Downloads\MyApp123\windows\MyApp123\Bundle\index.windows.bundle" -O -output-source-map" ???? 5 ???????????????????????????????????????? [C:\Users\jamie\Downloads\MyApp123\windows\MyApp123\MyApp123.vcxproj]. Check your build configuration.

This is probably because PropertySheets/Bundle.props is hard-coded to use x86\hermes.exe rather than taking the architecture into account. There appears to be an x64\hermes.exe available beside it (so the full set of supported architectures is x86 and x64).

https://github.com/microsoft/react-native-windows/blob/3d64f71ed8495da6a0dcfc1f97bcb8f761986594/vnext/PropertySheets/Bundle.props#L74

Steps To Reproduce

On an ARM Windows device (e.g. an ARM Mac running Windows through a VM), attempt a release build:

rnc-cli run-windows --arch=ARM64 --release
Expected Results

Release builds should work.

CLI version

20.1.3

Environment
System:
  OS: Windows 11 10.0.26100
  CPU: (4) x64 Apple Silicon
  Memory: 1.87 GB / 7.99 GB
Binaries:
  Node:
    version: 22.20.0
    path: C:\Users\jamie\AppData\Local\Volta\tools\image\node\22.20.0\node.EXE
  Yarn:
    version: 1.22.22
    path: C:\Users\jamie\AppData\Local\Volta\tools\image\yarn\1.22.22\bin\yarn.CMD
  npm:
    version: 10.9.3
    path: C:\Users\jamie\AppData\Local\Volta\tools\image\node\22.20.0\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK:
    AllowDevelopmentWithoutDevLicense: Enabled
    AllowAllTrustedApps: Enabled
    Versions:
      - 10.0.19041.0
      - 10.0.22621.0
IDEs:
  Android Studio: Not Found
  Visual Studio:
    - 17.11.35312.102 (Visual Studio Community 2022)
Languages:
  Java: Not Found
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli":
    installed: 20.1.3
    wanted: latest
  react:
    installed: 19.1.0
    wanted: 19.1.0
  react-native:
    installed: 0.81.5
    wanted: 0.81.5
  react-native-windows:
    installed: 0.81.15
    wanted: 0.81.15
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

info React Native v0.85.2 is now available (your project is running on v0.81.5).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.85.2
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.81.5&to=0.85.2
info For more info, check out "https://reactnative.dev/docs/upgrading?os=windows".
Community Modules

None

Target React Native Architecture

New Architecture (WinAppSDK) Only

Target Platform Version

None

Visual Studio Version

Visual Studio 2022

Build Configuration

Release

Snack, code example, screenshot, or link to a repository

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.