If the Jupyter pre-release won’t install in Cursor on Windows 10 or Windows 11, first check whether Cursor offers the exact build. If it does, update Cursor, restart it when prompted, and retry once while noting the time so you can find the failure in the logs. If Cursor only offers a stable build, an update may fix a compatibility problem, but it won’t make a build available from a different extension catalog. These steps are the same on both Windows versions and apply to the local Cursor desktop editor.

A Cursor window shows a failed Jupyter extension install because Python isn’t found in PATH, alongside troubleshooting notes. Check whether Cursor offers the Jupyter pre-release​

  1. Record what’s installed before changing it. Open Help > About and note the Cursor version and the VSCode Version field if shown. Press Ctrl+Shift+X to open Extensions, search for Jupyter, and open the extension’s details. For the extension discussed here, look for the ID ms-toolsai.jupyter. Record the installed version, if any, so you know what to return to if the preview breaks notebook support.
  2. Check the install or version controls on that listing. If there’s an arrow next to Install, look for Install Pre-Release Version. If the extension is already installed, look for Switch to Pre-Release Version on its details page or in its management menu. If Install Another Version is offered, compare the versions it lists with the exact build you need. Don’t treat a long version number or a general Preview badge on a registry page as proof you’re getting that build.
  3. Distinguish an unavailable build from a failed install. As of November 21, 2026, Cursor documents that it uses Open VSX for third-party extensions and serves them through its own marketplace proxy. The Open VSX listing and Microsoft’s Visual Studio Marketplace listing can differ, even when they use the same extension ID. Check the publisher and version on the source you intend to use. If Cursor shows only stable versions but Microsoft’s listing shows a pre-release, that doesn’t establish that the pre-release is available in Cursor. If the exact build is listed on Open VSX but not offered in Cursor, report the discrepancy rather than assuming the package is broken.

Update Cursor and retry the install once​

  1. Save your work and run the editor update. Press Ctrl+Shift+P, run Cursor: Attempt Update, and restart Cursor when prompted. Open Help > About again and check the running version. Keep Cursor on its Stable update channel for this test. Cursor’s Early Access channel changes the editor itself; it is not the Jupyter extension’s pre-release channel.
  2. If the in-app update won’t run, use the official Windows installer. Cursor documents that the command won’t work if update.mode is set to none. On a work PC, ask IT whether the update setting is managed before changing it or running a different installer. On a PC you manage, get the current Windows installer from Cursor’s download page, matching the architecture and installation scope of your existing copy: x64 or ARM64, and User or System. Install it over the existing copy rather than uninstalling first. Cursor says an in-place update carries over settings and chat history. If a failed update has left Cursor unable to open, this is also the recovery path; don’t delete the Cursor data folder.
  3. Recheck the listing, then make one attempt. If the pre-release is now offered, select it, note the local time, and keep the exact wording of any notification. Follow any reload or restart prompt. If Cursor calls the build incompatible, compare the package’s documented engines.vscode requirement, if available, with the VSCode Version shown in Help > About. Don’t compare it with the Cursor product version or the version of a separate VS Code installation. A matching version range is a useful check, not a guarantee that the extension can activate in Cursor. If the current Cursor build still rejects the package, use a compatible version rather than editing the extension manifest.

Find the install error in Cursor’s logs​

  1. Open the logs for the session that failed. In Cursor, press Ctrl+Shift+P and run Developer: Open Logs Folder. If you already restarted, press Win+E and paste %APPDATA%\Cursor\logs into the File Explorer address bar. Open the timestamped session folder that covers the failed attempt, not necessarily the newest one.
  2. Start with the shared-process log for a failed download or install. Open sharedprocess.log if present and search for ms-toolsai.jupyter or the exact version you selected. Check the lines around the time you clicked Install. Keep the first relevant error and a few surrounding lines; the final “failed to install” message is often less useful than the error that preceded it. If a different extension ID is named in the error, record that too: the Jupyter package can bring in companion extensions.
  3. Use the extension-host and Jupyter logs for failures after install. If the build appears under installed extensions but fails when you open a notebook, open View > Output and select Extension Host from the channel list if available. Look for an activation error around the time you opened the notebook. If the notebook opens but the kernel won’t start, check the Jupyter output channel if present. A missing Jupyter channel isn’t evidence of a failed download; the extension may not have loaded far enough to create it.

Match the error to the next step​

  • Timeout, proxy, or certificate error: Open Cursor Settings > Network > Run Diagnostics. If the Marketplace check fails or other extension listings also fail to load, give the diagnostic result to IT or Cursor support. Leave certificate validation, the firewall, and endpoint protection in place.
  • Blocked by policy or signature verification: Ask IT to check the exact extension ID and version. Cursor documents enterprise allowlists, signature verification, and an install cooldown that can delay newly published builds. Don’t sideload the package to get around a block.
  • Only the pre-release fails: If the exact stable build installs from the same Cursor listing but the pre-release does not, keep the working build and report the preview-specific error. A successful stable install doesn’t prove the preview is compatible or that its companion packages are available.
  • Access denied or a file can’t be written: Record the path named in the log. On a managed PC, ask IT to check permissions or endpoint-security events for that path. Don’t change folder ownership or run the editor as administrator just to make an extension install.

Verify the build and test a notebook​

  1. Press Ctrl+Shift+X, search for @installed Jupyter, and reopen the matching extension. Verify the installed version against the exact pre-release you meant to test. A working notebook does not prove you installed the preview, and jupyter --version reports Python-side packages, not the Cursor extension version.
  2. Open a trusted local .ipynb file and choose Select Kernel if prompted. Pick a known-working Python environment and run a simple cell such as print("Jupyter OK") with Shift+Enter. If the version is correct but the cell won’t run, troubleshoot the selected kernel separately. For a local Python kernel, check for ipykernel in that environment, not in an unrelated Python installation.

Use a VSIX only if the exact build is authorized for Cursor​

A local .vsix is useful if a trusted publisher provides the exact Cursor-compatible build and your organization permits manual installation. It is not a fix for an incompatible or blocked package. Microsoft says its extensions acquired from the Visual Studio Marketplace are licensed for use within the Visual Studio family, not in Cursor. If the required Jupyter pre-release is only available there, use Microsoft’s Visual Studio Code to test it rather than downloading the Marketplace package into Cursor.

  1. Get the exact .vsix from the trusted distribution source. Check the version and, if the publisher supplies platform-specific files, choose the one that matches the Cursor build you’re running.
  2. In Cursor, press Ctrl+Shift+P, run Extensions: Install from VSIX, and select the file. If Cursor rejects it, capture the error rather than overriding it. Follow any reload prompt, then verify the installed version again. Don’t assume a manual install subscribes you to future pre-release updates.

Restore a working version or escalate​

  1. If the preview installed but caused a regression, stop any running notebook cells and save your work. Open the extension’s management menu and switch back to the release version if that option is available. If Install Another Version is available and lists your previous working build, select it. Otherwise, uninstall the preview and reinstall the stable build from the approved listing, if available. Follow any reload prompt and repeat the version check and notebook test.
  2. If no compatible build is offered or the same install error persists, send IT or Cursor support the Windows version, Cursor version, VSCode Version field if shown, extension ID, requested build, and the source where you found it. Include the time and time zone of the failed attempt, whether stable installs, and the relevant log excerpt. Before posting publicly, remove tokens, private server addresses, usernames, and sensitive file paths.