VS Code on Windows 11 pops the 'Debugger Stopped" message when debugging Python 3.11.

Cary Hutchinson 20 Reputation points
2025-10-10T19:40:56.8666667+00:00

When trying to debug python code in VS Code using a virtual environment, the "Debugger Stopped" message pops up. When I check the launch.json file, it looks ok. There is a debugpy in the type: parameter When I change that to python, the problem goes away. I looked at some troubleshooting tips that recommend installing debugpy in the venv. That does not fix the error. Is this a bug? It happens every time I create a virtual environment. I have to switch the type to "Python". There is a statement that this is depreciated. Is there a work-around?

"type": "python"
{
    
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python Debugger: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "python":"${workspaceFolder}/venv/Scripts/python.exe"
        }
    ]
}
"type": "python"
Developer technologies | Visual Studio | Debugging
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Crespo Santiago, Alvaro 0 Reputation points
    2025-10-13T09:16:20.9133333+00:00

    The only workaround I have found so far is to downgrade all the python extensions in VSCode to the previous versions before this newest update. Namely, I am using Python extension v2025.14.0, Python Debugger extension v2025.10.0 and Python Environments extension v1.8.0.

    Using those versions the debugging works as before, with the same configurations.

    I guess we'll have to wait until the bug gets fixed before updating the extensions again.

    0 comments No comments

  2. Surya Amrutha Vaishnavi Lanka (INFOSYS LIMITED) 885 Reputation points Microsoft External Staff
    2025-10-14T12:26:27.49+00:00

    It sounds like you're running into an issue with the debugger in VS Code when using Python 3.11 in a virtual environment.

    1.You mentioned that changing the type to "python" resolves the issue. This suggests that the current setup with "debugpy" may not be functioning as expected. It could be a compatibility issue with your version of Python or the extension itself.

    2.Although you've already installed debugpy in your virtual environment and it didn't solve the problem, it's essential to ensure that it's the latest version. You can update it using:

    pip install --upgrade debugpy

    3.Make sure your launch.json file is correctly set up. You've shared a snippet that looks mostly fine, but ensure that it is correctly formatted and follows any updates to the VS Code configuration standards.

    0 comments No comments

  3. Surya Amrutha Vaishnavi Lanka (INFOSYS LIMITED) 885 Reputation points Microsoft External Staff
    2025-10-20T12:04:53.8266667+00:00

    Hope you're doing well! Please let us know if the issue persists or resolved. If the answer is helpful, please click "Accept Answer" and kindly approve it. If we didn't get any response from your side. we will proceed to close the thread by 23rd october.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.