vscode-jupyter: Failed to start the Kernel due to corrupted/partial installation of the extension

Hello everyone,

I have been founding some issues in running a jupyter notebook code in vscode, since I downloaded the last vscode version.

• I have installed python 3.9.7
• pip install jupyter
• pip install ipykernel
• I have the jupyter extension in visual studio.

Is there anyone can help me? Thank you so much.

Environment data

• VS Code version: May 2022 (version 1.68)
• Jupyter Extension version: v2022.5.1001601848
• Windows 10
• Python 3.9.7
• Jupyter server running: Local

Behaviour

I run “import numpy as np” and this generates an error message: Failed to start the Kernel. Failed to start the Kernel ‘base (Python 3.9.7 64-bit)’. View Jupyter log for further details. Cannot read properties of undefined (reading ‘makeSettings’)

Click on “log”:

Visual Studio Code (1.68.1, undefined, desktop) Jupyter Extension Version: 2022.5.1001601848. Python Extension Version: 2022.8.0. Workspace folder c:\Users\Elisa\Desktop\nn_loaddata info 18:6:51.878: ZMQ install verified. User belongs to experiment group ‘jupyterTestcf’ User belongs to experiment group ‘jupyterEnhancedDataViewer’ info 18:6:52.659: LSP Notebooks experiment is disabled – not in treatment group info 18:6:54.50: Starting Jupyter Session id = 'startUsingPythonInterpreter:. … FutureWarning: Supporting extra quotes around strings is deprecated in traitlets 5.0. You can use ‘hmac-sha256’ instead of ‘“hmac-sha256”’ if you require traitlets >=5. warn( … FutureWarning: Supporting extra quotes around Bytes is deprecated in traitlets 5.0. Use ‘49125cc5-3a6e-46af-a935-1adfb98431bd’ instead of ‘b"49125cc5-3a6e-46af-a935-1adfb98431bd"’. warn( … error 18:7:9.636: Failed to connect raw kernel session: TypeError: Cannot read properties of undefined (reading ‘makeSettings’) warn 18:7:9.643: Error occurred while trying to start the kernel, options.disableUI=true [r [Error]: … info 18:7:9.711: Kernel Output: NOTE: When using the ipython kernel entry point, Ctrl-C will not work.

To exit, you will have to explicitly quit this process, by either sending “quit” from a client, or using Ctrl-\ in UNIX-like environments.