uv backend stuck with x86 or nonexistent interpreter name

[ynkdir]

Current Behavior

When selecting x86 interpreter name or nonexistent name, nox command stuck.

Expected Behavior

Run with x86 interpreter. Fails with error message for nonexistent name.

Steps To Reproduce

With x86 interpreter name.

import nox

@nox.session(venv_backend="uv", python=["cpython-3.14-windows-x86"])
def tests(session):
    pass

> nox
nox > Running session tests-cpython-3.14-windows-x86
...stuck

With nonexistent interpreter name.

import nox

@nox.session(venv_backend="uv", python=["badname"])
def tests(session):
    pass

> nox
nox > Running session tests-badname
...stuck
``

### Environment

```Markdown
- OS: Windows11
- Python: 3.14.0
- Nox: 2025.10.16

Anything else?

No response

[henryiii]

I get:

$ nox -f tmp.py
nox > Running session tests-cpython-3.14-windows-x86
error: Failed to install cpython-3.14.0-windows-x86-none
  Caused by: failed to symlink file from python3.14 to /Users/henryfs/.local/share/uv/python/.temp/.tmphdiNzQ/python/bin/python: No such file or directory (os error 2)
nox > Missing interpreters will error by default on CI systems.
nox > Session tests-cpython-3.14-windows-x86 skipped: Python interpreter cpython-3.14-windows-x86 not found (took a second)

and

$ nox -f tmp2.py
nox > Running session tests-badname
error: `badname` is not a valid Python download request; see `uv help python` for supported formats and `uv python list --only-downloads` for available versions
nox > Missing interpreters will error by default on CI systems.
nox > Session tests-badname skipped: Python interpreter badname not found.

If I disable Python download,

$ nox -f tmp2.py --download-python=never
nox > Running session tests-badname
nox > Missing interpreters will error by default on CI systems.
nox > Session tests-badname skipped: Python interpreter badname not found.

[ynkdir]

Perhaps you are testing with unix like system? I got similar result with WSL environment. I am using Powershell on Windows Terminal.

[henryiii]

Okay, I'll have to retry on Windows when I'm around a Windows machine eventually.