microsoft / microsoft/react-native-windows

WindowsAppSDK 1.7.x breaks React Native Windows build (LNK1104 – win10- path bug)

Open
#15,562 9 comments 0 reactions 1 assignee View on GitHub

@vineethkuttan is already working on this.

Since Jan 27, 2026.

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

Description

Problem Description

React Native Windows build fails due to an invalid library path generated by
Microsoft.WindowsAppSDK 1.7.x.

The build system resolves this path incorrectly:
lib\win10-\Microsoft.WindowsAppRuntime.Bootstrap.lib

Architecture value is missing (win10- instead of win10-x64),
which causes a linker failure.

Downgrading WindowsAppSDK to 1.6.x fixes the issue.

Steps To Reproduce

Steps To Reproduce *

Create new project
npx react-native init RNWinTest

Add Windows support
npx react-native-windows init-windows

Build
npx react-native run-windows --arch x64

Build fails with LNK1104 error.

Expected Results

Build should complete successfully and launch the app.

Expected correct path:
lib\win10-x64\Microsoft.WindowsAppRuntime.Bootstrap.lib

CLI version

@react-native-community/cli: 20.0.0

Environment
OS: Windows 11 (x64)

Node: v22.x (via NVM)

Yarn: latest

React Native: 0.81.5

React Native Windows: 0.81.2

Windows App SDK (NuGet): 1.7.250401001

Windows App Runtime (system): 1.8.4 (x64)
Community Modules

react-native-gesture-handler

react-native-reanimated

react-navigation

axios

react-native-screens

Target React Native Architecture

New Architecture (WinAppSDK) Only

Target Platform Version

= 10.0.26100

Visual Studio Version

Visual Studio 2022

Build Configuration

Debug

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

Minimal repro:
npx react-native init RNWinTest npx react-native-windows init-windows npx react-native run-windows --arch x64

Error:
LINK : fatal error LNK1104: lib\win10-\Microsoft.WindowsAppRuntime.Bootstrap.lib

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.