same ![]()
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Right before pressing install update my interactive jupyter notebook (ctrl + shift + enter) worked fine. Now it’s throwing a:
/c:/Users/Lukas/AppData/Roaming/Cursor/User/globalStorage/ms-toolsai.jupyter/version-2025.2.0/jupyter/runtime contains invalid WIN32 path characters.
What I’ve tried
- Restarting Cursor
- Deleting venv and recreating
- Downgrading the jupyter extension to 2025.2.0
Steps to Reproduce
Download jupter extension from ms-toolsai. Activate interactive window in settings.
Open an interactive window
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.0.54
Windows
Does this stop you from using Cursor
No - Cursor works, but with this issue
I got the same issue and spent the whole day uninstall - reinstall again and again, it doesn’t work, I’m frustrating now. Maybe I’ll try downgrade it tmr
I’ve been forced to downgrade cursor by this too.
Same issue, so trying to bump the thread
Same issue, reinstalling to see if that works…
same
same. switching over to VSCode for now.
same
Same!!! I changed back to VStudio
Same issue, plz fix asap
So bad auto update, jupyter core not work, run by cell cannot be accessed now.
Same issue here … spend a lot of time trying to fix it as I thought it was something I had done, but should have looked here to find out immediately the later version of cursor seem to cause the issue.
Downgrading to the previous version fixed the issue …
same. but my current walkaround just install the previous version 1.7
all the extension are same as before and jupyter works fine
but my colleagues are not facing the same problems as us. that’s a bit strange
I have the same problem,too.
I have the same problem. I cannot select any of my Kernels.
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Sinde today’s update (Nov 4th, 2025) whenever I use Jupyter notebook, I cannot select any kernel: it lists available environments, just selecting them does nothing. tl;dr it worked 5 minutes before update. It still works on VS Code, so it seems to be Cursor-specific.
Steps to Reproduce
- Open a notebook
- Click “Select kernel”
- Click on any kernel
Expected Behavior
Kernel selected so that I can run the notebook.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.0.54 (system setup)
VSCode Version: 1.99.3
Commit: 7a31bffd467aa2d9adfda69076eb924e9062cb20
Date: 2025-11-03T22:40:44.657Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100
Does this stop you from using Cursor
No - Cursor works, but with this issue
version 2.0.60 still has this problem??? What have you updated?
It’s not working for me either.