1.28.0 unable to open terminal

[unional]

• VSCode Version: 1.28.0
• OS Version: Windows 10

Steps to Reproduce:

1. Install 1.28.0 in user mode
2. Open and launch terminal

Does this issue occur when all extensions are disabled?: Yes

It errors with:

The terminal process command 'C:\Program Files\Git\bin\bash.exe' failed to launch (exit code: 2)

The same goes for cmd.exe (the default).

By the way, in Windows, when I try to upgrade from background it fails with

There ARE other instances of VSCode running by other users. But no instance is running for the current user. That's probably a separate bug.

[unional]

For the upgrade issue, it is mentioned and tracked in #60375

[Tyriar]

Does this path exist C:\Program Files\Git\bin\bash.exe? exit code 2 means the path doesn't exist. For cmd.exe what path are you using to test this? Are you on a corporate locked down machine?

[unional]

Yes it exists. When downgrade back to 1.27.2, it works fine.
the same problem when I switch back to cmd.exe it's the basic command prompt.
The paths are correct and it is not in a locked down machine.

[unional]

This issue still exists in 1.28.2

[unional]

If I install it twice (before opening it), then it works. Seems like there is some corruption during upgrade.

[Tyriar]

Ok, let me know if you see it again. Closing for now.

[vscodebot]

We closed this issue because we are unable to reproduce the problem with the steps you describe. Chances are we've already fixed your problem in a recent version of VS Code. If not, please ask us to reopen the issue and provide us with more detail. Our issue reporting guidelines might help you with that.

Happy Coding!

[unional]

The corruption is due to #60375, so will see what happen after that is fixed.

[unional]

Said too soon. After I close VSCode and reopen it, the issue still exists. So it is not related to upgrade.

Please reopen.

[unional]

This is related to Workspace.

I have an additional setting in the workspace file:

{
  "settings": {
    "terminal.integrate.cwd": "..."
   }
}

That path is valid when the active project is "project-a" (I have "project-a" and "project-b" in the workspace) but not "project-b".

When the "project-b" is active (i.e. the currently active file is in "project-b"), the said path is invalid and causing the terminal fails to open (code 2).

[unional]

Since this is not officially supported, we can keep this issue closed.

Reference:
#42661
#42165