Debug Stopped, Unable to debug Python scripts

[amorenojr]

Not sure when it started but I am unable to debug Python scripts.

• Information

  • Python 3.13.8
  • Python Debugger 2025.14.0
  • VS Code
    • Version: 1.105.0 (system setup)
    • Commit: 03c265b1adee71ac88f833e065f7bb956b60550a
    • Date: 2025-10-08T14:09:35.891Z
    • Electron: 37.6.0
    • ElectronBuildId: 12502201
    • Chromium: 138.0.7204.251
    • Node.js: 22.19.0
    • V8: 13.8.258.32-electron.0
    • OS: Windows_NT x64 10.0.26100

• launch.json

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python Debugger: Current File",
            "type": "debugpy",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        }
    ]
}

Steps to reproduce

1. Open Python script
2. Press F5 (or play button to debug)
3. Select Python Debugger, current file
4. Observe

[CronusC]

Having the same issue in Cursor. Reversing back to 2025.10.0 solves the issue for me. It is the 2025.14.0 causing the issue.

[deniszitu]

Having the same issue in Cursor. Reversing back to 2025.10.0 solves the issue for me. It is the 2025.14.0 causing the issue.

I also reverted to version 2025.10.0 and it solved the issue with my vscode

[amorenojr]

I assume the dev team is aware?

[harpoonlobotomy]

Same issue here, started a few days ago. I switched to the prerelease version (2025.15.2025101002) and it fixed the issue; switching back to the Release Version (2025.14.0) immediately brings the error back.

[BuongiornoTexas]

Seems to be tied to the Python Environments release. #835?

[linghuye]

It wasted me two hour to fix the python environment, and in the end, I found out it was updated yesterday. Then reversing back to 2025.10.0 solves the issue.

[amorenojr]

I went to the pre-release version (2025.15.2025101002) as suggested by @harpoonlobotomy and no issues. I assume 2025.15.0 will have the fix.

[BoCoKeith]

Same for me on two different computers. Reverted to 2025.10,0 and it works fine.

[eleanorjboyd]

Yes the fix is out on the most recent pre-release of the extension and will be out on a point release of the extension within the hour (2025.14.1) thanks