Skip to content

How to Use uv on Windows ARM64

uv installs native ARM64 Python by default on Snapdragon and other Windows ARM64 machines. Keep that default unless a dependency lacks a win_arm64 wheel. In that case, use an explicit x86_64 interpreter for the project and let Windows run it under emulation.

Confirm you are on Windows ARM64

Open PowerShell and check the architecture:

$env:PROCESSOR_ARCHITECTURE

On a Snapdragon X Elite or other ARM-based Windows machine, you should see:

ARM64

If you see AMD64, follow How to install uv on Windows instead. The rest of this page only matters on ARM64.

Install the native ARM64 uv binary

The standalone installer detects the host architecture and downloads uv-aarch64-pc-windows-msvc.zip automatically. Run it from PowerShell:

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Open a fresh PowerShell window so the updated PATH takes effect, then verify:

uv self version

Look for aarch64-pc-windows-msvc in the build triple.

If that string says x86_64-pc-windows-msvc, you have the emulated build. Reinstall through the standalone installer to pick up the native one.

Use native ARM64 Python by default

Install Python without an architecture suffix:

uv python install 3.13

On a Windows ARM64 host, uv prefers cpython-3.13.x-windows-aarch64-none. Confirm the interpreter architecture:

uv run --python 3.13 python -c "import platform; print(platform.machine())"

You should see:

ARM64

Native ARM64 builds exist for Python 3.11 and newer.

To list every Windows ARM64 download uv knows about:

uv python list --all-arches

Without --all-arches, uv lists the native architecture and compatible installed interpreters instead of every available Windows download.

Check whether your dependencies have ARM64 wheels

Pure-Python wheels work on either architecture. Packages with compiled extensions need a compatible win_arm64 wheel or a working native source build. To check for wheels without installing anything, resolve against the Windows ARM64 platform and require binary distributions:

uv pip install --dry-run --verbose --only-binary :all: --target "$env:TEMP\uv-arm64-wheel-check" --python-platform aarch64-pc-windows-msvc --python-version 3.13 numpy pandas

The verbose resolver output includes the selected filenames. PyPI publishes win_arm64 wheels for NumPy and pandas, so both filenames end in win_arm64.whl. A resolution failure means at least one package has no compatible wheel. PyTorch does not publish a win_arm64 wheel.

If a package is missing a win_arm64 wheel, use an emulated x86_64 Python or choose another package. uv does not fall back across architectures within one environment; a .venv cannot mix aarch64 and x86_64 wheels.

Use x86_64 Python when a package requires it

Install an x86_64 interpreter with an explicit architecture request:

uv python install cpython-3.13-windows-x86_64

For one command, pass the same request to uv run:

uv run --python cpython-3.13-windows-x86_64 python -c "import platform; print(platform.machine())"

The emulated interpreter prints:

AMD64

For the current PowerShell session, select x86_64 independently of the project’s Python version:

$env:UV_PYTHON_ARCH = "x86_64"
uv sync

To keep the setting for future PowerShell windows, save it in the user environment:

[Environment]::SetEnvironmentVariable("UV_PYTHON_ARCH", "x86_64", "User")

To scope emulation to one project instead, pin the full request in its .python-version file:

uv python pin cpython-3.13-windows-x86_64

An explicit architecture in .python-version takes precedence over UV_PYTHON_ARCH.

Switch architectures cleanly

Changing the project’s Python architecture invalidates the existing virtual environment. Delete it before syncing the new architecture:

Remove-Item -Recurse -Force .venv
uv sync

uv sync recreates .venv against the selected architecture and resolves wheels for that platform.

Frequently asked questions

Is native ARM64 the default?

Yes. uv prefers native aarch64 Python on Windows ARM64, then falls back to x86_64 and 32-bit x86 when a native interpreter is unavailable. Set UV_PYTHON_ARCH=x86_64 or make an explicit cpython-...-windows-x86_64 request when a project needs emulation.

What does “tier 2 platform support” mean for uv on Windows ARM64?

Astral’s platform support policy lists Windows ARM64 as a Tier 2 target. uv ships official binaries and they are continuously built, but the test suite isn’t run on Windows ARM64 hosts, so individual edge cases can lag the Tier 1 platforms.

Can the standalone installer install the x86_64 uv build instead?

Yes, but there is little reason to. Wheel compatibility depends on the Python interpreter architecture, not the uv binary, so keep the native ARM64 uv unless you need to test the x86_64 build.

What if I see EXCEPTION_ACCESS_VIOLATION running native ARM64 Python?

This was reported in astral-sh/uv#19189 against uv 0.11.7 on Windows ARM64. Check that issue before assuming the crash is in your project.

Last updated on