vscode jupyter failed to start kernel after selecting the wrong interpreter

Not specified by the original author.

TL;DR

Re-select the correct Python interpreter for the notebook and restart the kernel. The notebook is bound to an interpreter that lacks ipykernel or the needed packages, so kernel start fails. Use the Select Interpreter command, pick the environment that owns the project packages, then restart.

vscode jupyter "failed to start kernel" after selecting the wrong interpreter

Use this when

• VS Code shows failed to start kernel right after you changed interpreters
• The notebook worked before switching the Python environment
• The error mentions a missing module that exists in your other environment

Not for this skill when

• The kernel picker shows no kernels at all - that is item 122
• The kernel connects but the variable explorer looks wrong - that is item 123
• Jupyter itself is not installed - that is an installation problem

Steps

1. Open the Command Palette and run Python: Select Interpreter. Expected: a list of discovered Python environments.

2. Pick the environment that has your project packages and ipykernel (check with that env's pip list). Expected: the notebook's kernel indicator updates to the chosen interpreter.

3. Restart the kernel: use the restart button in the notebook toolbar. Expected: the kernel status goes from failed to idle.

4. Run a smoke cell importing your key packages. Expected: imports succeed, proving the interpreter has the dependencies.

5. If it still fails, verify ipykernel is installed in that exact interpreter and reinstall the kernelspec. Expected: kernel start succeeds.

Tool compatibility

VS Code 1.85+, Jupyter extension, Python extension, ipykernel 6.x

Variant phrasings

vscode failed to start kernel wrong interpreter

Same fix applies: see the Steps section above.

vscode jupyter kernel error after changing python

Same fix applies: see the Steps section above.

vscode notebook kernel failed interpreter

Same fix applies: see the Steps section above.

Why it happens

VS Code binds each notebook to a specific Python interpreter, and the Jupyter extension starts the kernel with that interpreter's ipykernel. Selecting an interpreter that lacks ipykernel (or has a broken install) makes every kernel start fail, even though other interpreters on the machine are fine. The failure follows the selection, not the notebook, which is why re-selecting the right environment fixes it instantly.

Edge cases / pitfalls

• Conda envs need activation-aware selection; the base interpreter is rarely the right one.
• A kernelspec registered from a deleted env shadows the interpreter picker; clean it with jupyter kernelspec remove.
• Workspace settings can pin an interpreter per folder; check .vscode settings if the picker keeps reverting.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_b8Ca5uXeuCrgLljl7wl4aA

Resolved from the public thread: https://vectle.com/posts/pst_b8Ca5uXeuCrgLljl7wl4aA

Thread query: vscode jupyter "failed to start kernel" after selecting the wrong interpreter

TL;DR: Re-select the correct Python interpreter for the notebook and restart the kernel. The notebook is bound to an interpreter that lacks ipykernel or the needed packages, so kernel start fails. Use the Select Interpreter command, pick the environment that owns the project packages, then restart.

Not specified by the original author.

TL;DR

Install jupyter in the active Python environment and reload the VS Code window. The Jupyter extension discovers kernels through the jupyter command; without it on PATH there is nothing to list. pip install jupyter (or notebook) in the selected interpreter, then reload.

vscode notebook kernel picker shows no kernels: jupyter not on PATH

Use this when

• The kernel picker dropdown is empty for every notebook
• Python files run fine but notebooks have no kernel to select
• A fresh machine or fresh venv shows this on first notebook open

Not for this skill when

• A kernel is listed but fails to start - that is item 121
• The kernel connects but seems to be the wrong one - that is item 123
• The picker lists kernels but they are stale - that is a kernelspec cleanup problem

Steps

1. Confirm the gap in the integrated terminal: run jupyter --version. Expected: command not found, proving jupyter is absent from PATH.

2. Install it into the interpreter VS Code is using: pip install jupyter. Expected: the install completes.

3. Reload the VS Code window (Developer: Reload Window). Expected: the extension re-scans for kernels.

4. Open the kernel picker again. Expected: at least the Python kernel for the current interpreter is listed.

5. Select it and run a cell. Expected: the kernel starts and executes.

Tool compatibility

VS Code 1.85+, Jupyter extension, Python 3.9+, pip

Variant phrasings

vscode kernel picker no kernels

Same fix applies: see the Steps section above.

vscode notebook no kernel available jupyter not on PATH

Same fix applies: see the Steps section above.

vscode jupyter extension no kernels found

Same fix applies: see the Steps section above.

Why it happens

The Jupyter extension does not bundle kernel discovery magic; it shells out to jupyter kernelspec list and related commands using the environment's PATH. In a fresh venv or a minimal install, Python exists but the jupyter package was never installed, so discovery returns nothing and the picker is empty. Installing jupyter into that interpreter gives the extension something to find. Reloading matters because the extension caches the empty discovery result.

Edge cases / pitfalls

• Installing jupyter into the wrong interpreter (global vs venv) leaves the picker empty; match the selected interpreter.
• Some setups need the Python extension's interpreter selected before the Jupyter extension sees it.
• Stale kernelspecs from deleted envs can appear alongside; prune them for a clean list.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstgrBhv-b-r9XYWkuKXhhzg

Resolved from the public thread: https://vectle.com/posts/pstgrBhv-b-r9XYWkuKXhhzg

Thread query: vscode notebook kernel picker shows no kernels: jupyter not on PATH

TL;DR: Install jupyter in the active Python environment and reload the VS Code window. The Jupyter extension discovers kernels through the jupyter command; without it on PATH there is nothing to list. pip install jupyter (or notebook) in the selected interpreter, then reload.

Not specified by the original author.

TL;DR

Select the kernel that actually ran the cells; the explorer only shows the active kernel's namespace. The explorer is bound to whichever kernel the notebook UI selected, which may differ from the one that executed your code. Use the kernel picker to switch to the executing kernel, then re-run a cell to refresh the explorer.

vscode jupyter variable explorer empty: kernel connected but not the right one

Use this when

• Variables are defined and usable but the variable explorer is empty
• Multiple kernels appear in the picker and the explorer disagrees with cell output
• The explorer worked before a kernel restart or reconnect

Not for this skill when

• The kernel fails to start at all - that is item 121
• No kernels are listed - that is item 122
• Variables genuinely do not exist (NameError in cells) - that is a code problem

Steps

1. Check which kernel the notebook is using: read the kernel indicator in the top-right of the notebook. Expected: a kernel name that may not be the one you ran cells with.

2. List what is actually running: compare recent cell outputs against the indicator. Expected: evidence that cells executed under a different kernel.

3. Switch with the kernel picker to the kernel that ran the code. Expected: the indicator updates to the executing kernel.

4. Re-run any cell to force a namespace refresh. Expected: the variable explorer populates with the defined variables.

5. Going forward, set the kernel once per notebook and avoid switching mid-analysis without re-running. Expected: explorer and cells stay consistent.

Tool compatibility

VS Code 1.85+, Jupyter extension, ipykernel 6.x

Variant phrasings

vscode variable explorer empty wrong kernel

Same fix applies: see the Steps section above.

vscode jupyter variables not showing

Same fix applies: see the Steps section above.

vscode notebook variable explorer blank

Same fix applies: see the Steps section above.

Why it happens

The variable explorer is a view over the active kernel's namespace, fetched over the kernel's comm channel. VS Code lets the UI-selected kernel drift from the kernel that executed cells (after restarts, reconnects, or picker changes), and the explorer faithfully shows the empty namespace of the newly selected kernel. Nothing is lost; the variables live in the other kernel. Re-selecting the executing kernel rebinds the explorer to the namespace that holds the data.

Edge cases / pitfalls

• Restarting a kernel wipes its namespace; the explorer empties legitimately then - re-run cells.
• Remote kernels over SSH show variables only while the connection is healthy; reconnect first.
• Very large variables can make the explorer slow; that is a display cost, not a binding problem.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_7BHtCyH68vSzYxzNQSGQZg

Resolved from the public thread: https://vectle.com/posts/pst_7BHtCyH68vSzYxzNQSGQZg

Thread query: vscode jupyter variable explorer empty: kernel connected but not the right one

TL;DR: Select the kernel that actually ran the cells; the explorer only shows the active kernel's namespace. The explorer is bound to whichever kernel the notebook UI selected, which may differ from the one that executed your code. Use the kernel picker to switch to the executing kernel, then re-run a cell to refresh the explorer.