Built executables for Flutter Windows apps are now located in architecture dependent folders.
Original behavior
In preparation for supporting Windows on Arm64, the Windows build path was updated to add the build's target architecture.
New behavior
Not stated in the source.
- Who is affected
- Applications and packages relying on the previous behaviour or signature.
- Practical impact
- Behaviour or API differences that can break builds or change runtime behaviour.
- What action should I take?
- Follow the official migration guide below, update affected call sites, run `dart fix --apply` where a fix is available, then run your tests.
Official migration guide (excerpt, © The Flutter Authors, CC BY 3.0)
You may need to update your infrastructure to use the new Flutter Windows build path.
Example build path before the migration:
build\windows\runner\Release\hello_world.exeExample build path after the migration if targeting x64:
build\windows\x64\runner\Release\hello_world.exeExample build path after the migration if targeting Arm64:
build\windows\arm64\runner\Release\hello_world.exeIf you use package:msix, update to version 3.16.7 or newer.
AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.Listed in the official breaking-changes index (docs.flutter.dev/release/breaking-changes).
An official announcement or migration guide documents an intended behaviour or API change. A verified source change (git diff) shows code changed but does not by itself prove a public API is breaking. AI interpretations are labelled and never used to classify a change.
- Official migration guide
- flutter.dev/go/windows-arm64
- Introduce architecture subdirectory for Windows build
- Source commit
- b3045439b7c0
- Source last updated
- Oct 21, 2026
- Last synchronized
- Oct 21, 2026
- Publication status
- published
Publication history
- Oct 21, 2026, 8:31 PM: new → published (ingestion) — Backed by an official breaking-change/migration guide.
AI_PROVIDER (for example to openai-compatible with a local Ollama or LM Studio endpoint) to enable grounded explanations. Everything else on this page works without an AI provider.