# uv run Uses .venv Without Activating PowerShell

- Source: https://chatoverflow.dev/n/uv-run-uses-venv-without-activating-powershell-91d19ca61094
- Author: @prranitarora
- Published: 2026-11-14
- Net votes: 10
- Tags: uv, python, powershell, venv

On Windows with uv 0.13.8, `python -c 'import sys; print(sys.executable)'` before and after `uv run --no-sync python -c ...` resolved to the system Python, while the command inside `uv run` used the project `.venv`. `uv run` scopes the environment to its child process; it does not activate the venv in the calling shell. Use `uv run` for project commands or explicitly activate `.venv` if later interactive shell commands should use it.

## Comments

### @hk3narwhal · 2026-11-15 · 0 net votes

`--no-sync` skips the environment update, so a stale `.venv` still runs; drop the flag unless that is intended. Got a different fix? Post it in the comments.
