skip to Main Content

After updating VSCode, I have been unable to run Jupyter notebooks anymore. I am using VSCode on a MacBook Pro Max M1 and am encountering the following error:

Failed to start the Kernel. 
Jupyter server crashed. Unable to connect. 
Error code from Jupyter: 1
usage: jupyter.py [-h] [--version] [--config-dir] [--data-dir] [--runtime-dir]
                  [--paths] [--json] [--debug]
                  [subcommand]

Jupyter: Interactive Computing

positional arguments:
  subcommand     the subcommand to launch

options:
  -h, --help     show this help message and exit
  --version      show the versions of core jupyter packages and exit
  --config-dir   show Jupyter config dir
  --data-dir     show Jupyter data dir
  --runtime-dir  show Jupyter runtime dir
  --paths        show all Jupyter paths. Add --json for machine-readable
                 format.
  --json         output paths as machine-readable json
  --debug        output debug information about paths

Available subcommands: kernel kernelspec migrate run troubleshoot

Jupyter command jupyter-notebook not found. 
View Jupyter log for further details.

Unfortunately, none of the steps I tried have worked.

I am using January 2023 (version 1.75) release and extesion versions are as follows:

  • Python v2023.2.0
  • Jupyter v2023.1.2010391206

Has anyone else faced this issue? I would greatly appreciate any suggestions or solutions.

Thank you!

I have tried a number of steps to resolve the issue, including:

  1. Making sure that jupyter-notebook is running in the terminal
  2. Installing Jupyter in new conda and Python virtual environments
  3. Removing VSCode and its related directories completely and downloading it again
  4. Trying the "Switch to Pre-Release Version" for both Jupyter and Python extensions in VSCode
  5. Tried updating jupyter and notebook liberaries
  6. Tried running VSCode with code --no-sandbox

2

Answers


  1. 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).

    Login or Signup to reply.
  2. solved downgrading to previous version (November 2022) then updating to latest version again. Running same Python and Jupyter version. Good luck

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search