Repository navigation
"Debug Stopped" no matter "Start Debugging" or "Run Without Debugging" #826
Description
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.
Activity
NewUserHa commentedon Oct 10, 2025
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 commentedon Oct 10, 2025
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 commentedon Oct 10, 2025
python3.13 is affected too
martinowitsch commentedon Oct 10, 2025
Same issue after updating vscode
python 3.10
kcerniauskas3 commentedon Oct 10, 2025
I think it just co-coincided with VS Code update, as debugger extension got updated too.
martinowitsch commentedon Oct 10, 2025
True!
Setting Python Debugger extension to version 2025.10.0 resolved this issue for me
radu-ion commentedon Oct 10, 2025
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 commentedon Oct 10, 2025
This solution is an instant fix.
irenedecesare commentedon Oct 10, 2025
Man, you just saved me with this comment. You were more helpful than GPT. Thanks!
a-kachurin commentedon Oct 10, 2025
The same
drkpierson commentedon Oct 10, 2025
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 commentedon Oct 10, 2025
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 commentedon Oct 10, 2025
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)
2 remaining items
eleanorjboyd commentedon Oct 10, 2025
Hello! I have put out a release with the fix. It was release 5 minutes ago (so 11:39 PDT) and has the version
2025.15.2025101002but this specific version number may different across machine types. Please give this a try and let me know if it works. Thanks!blongbs commentedon Oct 10, 2025
Eleanor Boyd (@eleanorjboyd)
My path has spaces further up in the directory and I have had the problem.
blongbs commentedon Oct 10, 2025
Eleanor Boyd (@eleanorjboyd) installed the update from the prerelease. The change allowed my system to run the debug as the older version 2025.10.0
dmail00 commentedon Oct 11, 2025
Eleanor Boyd (@eleanorjboyd) This version broke my install, reporting "Debug Stopped", reverted to previous version.
radu-ion commentedon Oct 11, 2025
Yes, that fixes it for me. I've also updated the Python Environments extension, so everything Python is up to date on my machine, as is the VS Code. Thanks!
P.S. I have switched back the type from "python" to "debugpy" in launch.json, as it used to be.
P.P.S. My Python interpreter is in "Program Files", so yes, it has a space in it. I was suspecting that this could be the problem, so I will install it in a folder with no spaces from now on.
samdockrill commentedon Oct 11, 2025
Yep, my path had spaces and I had this issue too. Will try the update. Was very confusing considering I am still learning Python, glad it is a known and seemingly solved issue and not some mysterious misconfiguration on my end.
torolego commentedon Oct 12, 2025
well done Eleanor :) ! it's work also for me, thank you very much 💯
eleanorjboyd commentedon Oct 13, 2025
Glad it worked for everyone! I am putting out a new stable release with the fix (2025.14.1) right now that should be out soon. Thanks
minhbuibhm commentedon Nov 14, 2025
The new Debugger extension (version 2025.16), released yesterday, November 13th, has the same error "Debug Stopped". I've switched back to version 2025.15, and it's working fine now
ziadwagdy commentedon Nov 16, 2025
Encountering the same issue "Debug Stopped" after upgrading vscode to the latest version on macOS Silicon,
When having the following configuration to debug a python program:
it fails, but when attaching the debugger to a process it works fine.
eleanorjboyd commentedon Nov 18, 2025
may be related to #849. Can you try changing the setting
python.useEnvironmentsExtension: falseand let me know if that makes it work again?ziadwagdy commentedon Dec 1, 2025
It is set to false by default, yet it didn't make it work.
Having a default python environment set makes debugging works fine. with "request" : "launch", added.