"Debug Stopped" no matter "Start Debugging" or "Run Without Debugging"

[NewUserHa]

version:
vscode: 1.104.3
python: 2025.16.0
python debugger: 2025.14.0
python environments: 1.8.0

after investigating, found output from python extension:

2025-10-10 11:55:58.227 [warning] Failed to check if .\"c:\Program Files\Python314\python.exe" is an executable [Error: ENOENT: no such file or directory, lstat 'C:\Users\User\AppData\Local\Programs\Microsoft VS Code\"c:\Program Files\Python314\python.exe"'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'lstat',
  path: 'C:\\Users\\User\\AppData\\Local\\Programs\\Microsoft VS Code\\"c:\\Program Files\\Python314\\python.exe"'
}
2025-10-10 11:55:58.229 [warning] Identifier for virt-virtualenv failed to identify .\"c:\Program Files\Python314\python.exe" [Error: ENOENT: no such file or directory, scandir 'C:\Users\User\AppData\Local\Programs\Microsoft VS Code\"c:\Program Files\Python314'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'scandir',
  path: 'C:\\Users\\User\\AppData\\Local\\Programs\\Microsoft VS Code\\"c:\\Program Files\\Python314'
}

the language server works normal, having no issue.
disabling python environments doesn't help.
sometimes it will prompt missing launch.json, but in previous version of python debugger, it can work without launch.json and should work without that, it's a feature.

[NewUserHa]

when setting "python.useEnvironmentsExtension": true, the error become:
the output of python extension stopped output that previous error, but no matter "Start Debugging" or "Run Without Debugging", it popup

[NewUserHa]

version 2025.6.0 version 2025.10.0 has no this issue, but to work on python3.14 needs debugpy>=v1.8.15, however, only version>=
2025.14.0 bundled debugpy>=v1.8.15.

so, python3.14 unable to use debug until this issue fixed.

info: https://www.github.com/microsoft/debugpy/issues/1893

[kcerniauskas3]

python3.13 is affected too

[martinowitsch]

Same issue after updating vscode

python 3.10

[kcerniauskas3]

I think it just co-coincided with VS Code update, as debugger extension got updated too.

[martinowitsch]

True!
Setting Python Debugger extension to version 2025.10.0 resolved this issue for me

[radu-ion]

Same here! The only thing that worked for me, with all latest versions of VS Code and all Python extensions, was to set the "type" from "debugpy" to "python" in the launch.json file.

[RamkiAllada]

Same here! The only thing that worked for me, with all latest versions of VS Code and all Python extensions, was to set the "type" from "debugpy" to "python" in the launch.json file.

This solution is an instant fix.

[irenedecesare]

Man, you just saved me with this comment. You were more helpful than GPT. Thanks!

Same here! The only thing that worked for me, with all latest versions of VS Code and all Python extensions, was to set the "type" from "debugpy" to "python" in the launch.json file.

[a-kachurin]

The same

[drkpierson]

Same here! The only thing that worked for me, with all latest versions of VS Code and all Python extensions, was to set the "type" from "debugpy" to "python" in the launch.json file.

Any ideas how to do something similar for jupyter notebooks? When I run my notebook it hangs with "Connecting to kernel: Python 3.13.7..."

[eleanorjboyd]

Hi everyone- so sorry for this issue arising and thank you for all the details on what is happening. It seems like downgrading to 2025.10.0 or switching the "type" are fixes people are seeing. Are others also seeing an error message along the lines of "Failed to check if ."c:\Program Files\Python314\python.exe" is an executable"? Investigating the issue now- thanks

[eleanorjboyd]

My best guess for the regression is this PR: 408601a#diff-393c6b35367e2a8adc44dc3c3a41fc893d752e37dae2d0f6ed5bbe29da485648. Curious what people's interpreter paths are which are failing (ie do they have spaces in them)