I ran into this too. I was able to work around it by switching the Jupyter extension to the pre-release version (which was a suggestion in a different question that I can't find anymore).
Answer from Alex Trzyna on Stack OverflowI ran into this too. I was able to work around it by switching the Jupyter extension to the pre-release version (which was a suggestion in a different question that I can't find anymore).
solved downgrading to previous version (November 2022) then updating to latest version again. Running same Python and Jupyter version. Good luck
VS Code doesn't load any jupyter notebook file
python - Jupyter notebook not opening in VS Code - Stack Overflow
VS Code select Existing Jupyter Server stopped working
I am installing the jupyter extension on my VsCode and its failing with a Vscode version error.
Error which I see after toggling Developer mode.
Please help!
Check the required extensions installed in vscode.
install jupyter and ipython packages in your python venv using pip:
pip install jupyter pip install ipythonIf its still not working try to change the python kernal in the top right corner of ipynb notebook.
This is due to running jupyter without first activating the environment for Python 3.7. This was fixed in the 2018.12.0 release of the extension.
Hi,
I have a Jupyter notebook file that VS Code is not loading. An option on the top right came to select the kernel from the marketplace, which I installed then its not working and get an error, below is the process.
-
select kernel from marketplace (Jupyter by Microsoft)
-
get an error: "Extension activation failed, run 'DeveloperL Toggle Developer Tools' command for more information
Edit: Also installed the python extension and the file is stuck in the loading stage. For test reason as well, I created a random `.ipynb` and I couldn't run any python code but the cells were present.
I have 2 kernels locally on my linux (python 2 and 3), that work fine from Jupyter. I looked online by couldn't find any fix to this, any help is appreciated, thank you!
OS: Manjaro KDE
I tried installing code and upgrading to insiders (AUR) using pacman and did not get Python to install in vscode because of the Jupyter error. I tried installing Jupyter vsix manually and this also failed.
I ended up getting Python in to vscode by installing code using snap. https://snapcraft.io/code
If python/other extension on VS Code is unable to be installed, then:
You should uninstall VS code first, then clear the temp and prefetch file.
After that, go to
C:\Users\<username>\AppData\Roamingand delete Code folder there.Now Restart your PC and install VS Code Again.
Thats It. Done.
Hey everyone,
I'm running into a persistent issue with the Jupyter extension in VS Code and I'm hoping someone can point me in the right direction.
I'm trying to run a simple Python cell in a .ipynb notebook, but I can't execute anything because the Jupyter extension fails to start. As you can see in the screenshot, I keep getting the error notification: Extension activation failed, run the 'Developer: Toggle Developer Tools' command for more information.
What I've Tried So Far:
-
Reinstalling: I have completely uninstalled and reinstalled the Jupyter extension (and its related dependencies like the Python extension) multiple times.
-
Restarts: I have closed and reopened VS Code, and even restarted my computer.
-
New Environments: I've created fresh virtual environments (using
venv) and installedipykernelwithin them, but the issue persists no matter which interpreter I select. -
Different Files: This happens with any notebook file, even a brand new one with a single
print()statement.
I feel like I'm missing something obvious, but I can't figure out what
Hi everyone,
I am currently unable to connect to any Python kernel (and run Jupyter notebooks). However, I can still run Python commands (such as installing packages with pip) within a virtual environment.
My extensions on VSC also never load fully.
Please help.
I have tried to reinstall VSC, but I have had no success.
If Python extension is available, (if not install that extension) in VSCode, while the jupyter style file (cells beginning with # %%) is active:
- Press Ctrl+Shift+P
- Type: Export Current Python File as Jupyter Notebook
An easy way to fix this should be to save the file with an .ipynb ending, vs-code should then automatically start the notebook extension. You can also make sure that you activated a Python environment, then Python: Create New Blank Jupyter Notebook should appear.
An alternative I would recommend is editing notebooks following this guide in the vs-code documentation
It's not the Visual Studio Code update. I've been experimenting on a virtual machine, after my students started complaining this week that their Jupyter Notebooks stopped working...
I've tried downgrading Visual Studio Code, but that didn't solve the problem, so I started looking somewhere else.
As far as I know right now, the problem lies in the Jupyter-extension.
I have first disabled the Auto Update for the Jupyter-extension.
Next, I have downgraded the extension to version 2025.7.0, and it works again.
For good measure, I've then tried to update to version 2025.8.0: it also works.
But, when using version 2025.9.0: it breaks!
So what I would recommend:
In the Extensions-tab, disable Auto Update for the Jupyter extension.
Then use the Install Specific Version-menu to install version 2025.8.0.

After further testing:
The alternative is to Switch to Pre-Release Version, at least version 2025.10.2025101001. That also works.
UPDATE 2025-10-16:
Jupyter extension version 2025.9.1 has been released. This fixes the issue as well.
It seems to be an issue with the version 7.0.0 of the ipykernel python package. The jupyter notebook extension in vscode as well as the jupyter notebook in the browser get stuck in kernel connecting state when a cell is executed. On installing ipykernel==6.30.1, which is the version before 7.0.0, I don't face this issue in vscode or jupyter notebook in browser.
I have created an issue for the same: https://github.com/ipython/ipykernel/issues/1445
Hence I think we have to use ipykernel==6.30.1 until the issue is fixed. You can install it by running
pip install ipykernel==6.30.1
P.S.: ipykernel 7.0.1 has been released and it fixes this issue.