Run Python File via Git Bash suddently stopped working

[stephsi]

Type: Bug

Behaviour

When i click on the Run Python File button i get the following error message

C:\Users\username\repositories\project.venv\Scripts\python.exe c:/Users/username/repositories/project/test.py
bash: C:Usersusernamerepositoriesproject.venvScriptspython.exe: command not found

It seems that VSCode does not adjust the Path for the Git Bash.
Previously, it all worked perfectly, no issues whatsoever. I did not change anything.
It also does not matter if I use a virtual env or not.

Seems to be the identical problem as microsoft/vscode-python#25389
I also tried setting "python.useEnvironmentsExtension": false as suggested in the other bug ticket, but this did not fix the problem for me either.

As the other ticket was closed by the ticket creator, I opened a new one.
@anthonykim1, you mentioned here, that one should let you know if this happens again.

Thank you in advance

Steps to reproduce:

1. Select Git Bash terminal as default terminal
2. Make any python file, insides don't matter, cus it won't launch anyway
3. Get error because of backslashes

Extension version: 2025.12.0
VS Code version: Code 1.102.3 (488a1f239235055e34e673291fb8d8c810886f81, 2025-07-29T03:00:23.339Z)
OS version: Windows_NT x64 10.0.22631
Modes:

• Python version (& distribution if applicable, e.g. Anaconda): 3.12.10
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): System
• Value of the python.languageServer setting: Default

User Settings

languageServer: "Pylance"

terminal
• activateEnvironment: false

Installed Extensions

Extension Name	Extension Id	Version
copilot	Git	1.350.0
copilot-chat	Git	0.29.1
debugpy	ms-	2025.10.0
js-debug	ms-	1.102.0
js-debug-companion	ms-	1.1.3
jupyter	ms-	2025.7.0
jupyter-keymap	ms-	1.1.2
jupyter-renderers	ms-	1.3.0
python	ms-	2025.12.0
remote-containers	ms-	0.422.1
remote-explorer	ms-	0.5.0
remote-server	ms-	1.5.2
remote-ssh	ms-	0.120.0
remote-ssh-edit	ms-	0.87.0
remote-wsl	ms-	0.99.0
vscode-js-profile-table	ms-	1.0.10
vscode-jupyter-cell-tags	ms-	0.1.9
vscode-jupyter-slideshow	ms-	0.1.6
vscode-kubernetes-tools	ms-	1.3.25
vscode-pylance	ms-	2025.7.1
vscode-python-envs	ms-	1.2.0
vscode-remote-extensionpack	ms-	0.26.0
vscode-yaml	red	1.18.0

System Info

Item	Value
CPUs	Intel(R) Core(TM) Ultra 7 165H (22 x 3072)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	63.64GB (41.18GB free)
Process Argv	--crash-reporter-id afa123c2-11ba-4b1b-bd60-c10fe94c2ee5 --crash-reporter-id afa123c2-11ba-4b1b-bd60-c10fe94c2ee5
Screen Reader	no
VM	0%

A/B Experiments

vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythoneinst12:31285622
996jf627:31283433
pythonrdcb7:31342333
usemplatestapi:31297334
747dc170:31275177
aj953862:31281341
9d2cg352:31346308
convertlamdaf:31368658
usemarketplace:31343026
nesew2to5:31336538
agentclaude:31350858
replacestringexc:31350595
nes-set-on:31351930
6abeh943:31336334
envsactivate1:31353494
0927b901:31350571
f76d9909:31348711
45650338:31358607
0cj2b977:31352657
0574c672:31362109
controlchatstate:31363048
pylancealldocsf:31367565
retrydisabled:31368125

[stephsi]

Today, my company rolled out VSCode Version 1.103.1.

Together with "python.useEnvironmentsExtension": false, the path of the python executable is correctly parsed and the python file can be executed without any problem.

Setting "python.useEnvironmentsExtension": true still results in the incorrect parsing and the error message.
Is this the intended behaviour?
If so, the issue can be closed.

[anthonykim1]

@stephsi Thanks for filing the issue.
If it works with "python.useEnvironmentsExtension": false, but not with "python.useEnvironmentsExtension": true, it would be how we handle strings when executing via Run button from environment extension.

@eleanorjboyd I think we might be doing something different in env extension in terms of path when executing via 'run button'.

[Garyouki]

had the same issue, and can confirm that "python.useEnvironmentsExtension": false is able to fix the issue.

[eleanorjboyd]

Hi! Can someone confirm specifically what command they are seeing attempted in the gitbash that isn't working? I see Get error because of backslashes but is this in the file path or interpreter path?

Also is anyone seeing this on mac or linux? I see the first report was for windows

[stephsi]

Hello @eleanorjboyd!

I would say, only the interpreter path causes the problems.

When I click the Run Python File button, I receive the following error (as already posted at the beginning)

C:\Users\username\repositories\project.venv\Scripts\python.exe c:/Users/username/repositories/project/test.py
bash: C:Usersusernamerepositoriesproject.venvScriptspython.exe: command not found

If I manually copy the failed command, replace the \ with / in the interpreter path and then execute the command again, it works as expected.

[fiscalia8]

I am having the same issue. Git Bash terminal.

A git repo I've worked in for years suddenly will not execute .py files; I am getting the same type of results as user stephsi. (Only changes on the user side are moving off a branch to work in main and shifting from SSH to login and back.)

Have tried "python.useEnvironmentsExtension": , as both true and false, neither fixes it. It's not a PATH issue. Have uninstalled python extensions and reinstalled, no luck. disabled all other extensions just in case; again no luck.

can run the file if I type python test.py but not if I press the Play button or use keyboard shortcut to run code.
Extensions:

Extension | Author | Version
-- | -- | --
debugpy | ms- | 2025.14.1
python | ms- | 2025.16.0
vscode-pylance | ms- | 2025.9.1
vscode-python-envs | ms- | 1.10.0

Edition Windows 11 Home
Version 22H2
Installed on ‎11/‎17/‎2022
OS build 22621.1992

Edit to add: reverting to pre-release Version 1.11.13081015 fixed my issue. All python code runs properly again.