You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Settings : Source control Providers : Azure DevOps KO #2661
After investigating this, the bug seems to be that, at least on Windows, the az commands should be executed with shell: true.
The reason is that the command is actually a az.cmd file, and without the shell option, that command is not found.
Confirming what was noted here: same root cause — on Windows az is az.cmd, and the VCS process spawn can't resolve it without shell/PATHEXT handling. Consolidating into #2576.
Hey @juliusmarminge, I mentioned above that I'm seeing the same behavior on Arch Linux as well (all VCS provider toggles are unable to be enabled on v0.0.24).
The duplicate issue appears to be specifically about Windows failing to spawn az.cmd, which wouldn't apply on Arch. Is there evidence that this is the same root cause, or should the Linux case be tracked separately?
Activity
leddt commentedon May 26, 2026
After investigating this, the bug seems to be that, at least on Windows, the
azcommands should be executed withshell: true.The reason is that the command is actually a
az.cmdfile, and without the shell option, that command is not found.leddt commentedon May 27, 2026
Duplicate of #2576
DerekCorniello commentedon Jun 5, 2026
@leddt I am having the same issue with all VCS providers having the toggle unable to flip on Arch, v0.0.24.
juliusmarminge commentedon Jun 9, 2026
Duplicate of #2576
Confirming what was noted here: same root cause — on Windows
azisaz.cmd, and the VCS process spawn can't resolve it without shell/PATHEXT handling. Consolidating into #2576.az.cmd#2576DerekCorniello commentedon Jun 9, 2026
Hey @juliusmarminge, I mentioned above that I'm seeing the same behavior on Arch Linux as well (all VCS provider toggles are unable to be enabled on v0.0.24).
The duplicate issue appears to be specifically about Windows failing to spawn
az.cmd, which wouldn't apply on Arch. Is there evidence that this is the same root cause, or should the Linux case be tracked separately?