how to set the default venv in windows PyCharm 2026.1

Created July 13, 2026 14:39

using win10/11; uv 0.9.8 (85c5d3228 2025-11-07); PyCharm 2026.1+

i have a master Venv residing in

C:\uv313\.venv\Scripts\python.exe
C:\uv313\.venv\Lib\site-packages

and my projects and code base resides in D:\uv313

i would like to learn how to setup pycharm so that for all new projects it defaults to this single .venv and for existing projects to automatically use the same master/single .venv instead of repeatedly resetting the interpreter from <no interpreter>

here is what i experience with PyCharm

when l open PyCharm and select an existing project i have to reset the interpreter due to this status: “no interpreter” So i go through the process of selecting a custom interpreter every time.
The second event that requires changing settings is when I create a new project. i select add new interpreter and see the next window which has:
interpreter type: select custom environment

Environment: Select existing
Type: dropdown only shows two entries: Python(system); conda
1. why is “uv” not listed in dropdown so i can select my master .venv?
Python path: this dropdown has two entries
1.Python 3.14 ( ~\AppData\Local\Programs\Python\Python314\python.exe) system

2.Python 3.13 (~\AppData\Roaming\uv\Python\cpython-3.13.9-windows-x86_64-none\python.exe) uv

and if i make a different choice and choose the following (second try)
Interpreter Type: uv
Python version: default
Path to uv: C:\Users\me\.local\bin\uv.exe
Location: show a path to a new project .venv
but the note from pycharm states: uv environment will be created in the project root
So this implies that pycharm will make another .venv which is what i do not want or need.

So i select browse and choose C:\uv313\.venv then pycharm warns me with this msg
Environment at “.venv” already exists. Choose: Override existing environment, or select existing interpreter. I choose select existing. But nothing happens. The msg doesn't disappear and the project is not created.

Please provide instructions how to set a default .venv rather than generating a new .venv for each project. Again, i am using a master single .venv for all projects and do not use .venv individually for every project. And the .venv resides on C: and code lives on a separate drive D:

1 comment

Mikhail Tarabrikov

Created July 13, 2026 15:36

Hi webscraper,

Your master venv at C:\uv313\.venv is a standard virtual environment, so the way to reuse it is to register it with PyCharm once as a regular Python interpreter, not through the uv type. The uv option in that dialog is for creating environments. That's why it always points to a new .venv in the project root and complains when the folder already exists

Registering takes a minute: open the interpreter selector in the status bar (or Settings | Python | Interpreter) and add a new interpreter. Choose "Select existing" and keep Type set to Python. The path dropdown only shows interpreters PyCharm found on its own, so your venv won't be in it. Click the browse button and point it at C:\uv313\.venv\Scripts\python.exe directly

From then on PyCharm knows the interpreter. For every existing project that opens with "no interpreter", click the same status bar selector and pick it from the list. For new projects, choose "Select existing" with the Python type in the wizard and pick the same interpreter. No extra .venv gets created. The venv sitting on C: while your code lives on D: is fine. Our KB article SUPPORT-A-4135 has more detail on this pattern

uv is missing from the Type dropdown because a venv made by uv venv is an ordinary virtual environment, and PyCharm files it under the Python type. The uv entries elsewhere in that dialog cover uv-managed installations. That's also where the uv-installed Python 3.13 in your path list comes from

The dead end you hit in the new project dialog, where "select existing interpreter" does nothing and the project is never created, looks like a bug on our side. That warning dialog in the uv flow has known problems. A related one, where the "Override existing environment" choice fails, is tracked in PY-89924. You can watch that issue for updates (see https://intellij-support.jetbrains.com/hc/en-us/articles/207241135). Until it's sorted out, the registration route above avoids that dialog entirely

If the interpreter still refuses to attach to one of your projects, tell us what you see and we'll take a closer look.

Please sign in to leave a comment.