Workspace trust doesn't work in VS Code 1.106.0

[JVApen]

Does this issue occur when all extensions are disabled?: N/A

• VS Code Version: 1.106.0
• OS Version: Local: Windows_NT x64 10.26100

Steps to Reproduce:

1. Use VS Code on Windows to remotely connect to a Linux device.
2. On the device, have following tasks in the workspace:

      {
         "label": "Initialize launch.json",
         "type": "shell",
         "windows": {
            "command": "if (! (Test-Path \\\".vscode/launch.json\\\" -PathType Leaf)) { Copy-Item \\\".vscode/launch.json.windows\\\" -Destination \\\".vscode/launch.json\\\" }",
         },
         "linux": {
            "command": "if [ ! -f .vscode/launch.json ]; then cp .vscode/launch.json.linux .vscode/launch.json; fi",
         },
         "group": "none",
         "presentation": {
            "reveal": "never",
            "revealProblems": "onProblem",
            "close": true,
            "panel": "dedicated"
         },
         "runOptions": {
            "runOn": "folderOpen"
         },
         "problemMatcher": []
      },

3. Open the workspace
4. Notice the task keeps hanging, following notifications appears;

The terminal process failed to launch: Cannot launch a terminal process in an untrusted workspace with cwd \workspaces and userHome \home\coder.

5. Note that the path separators are using \ instead of /

Enabling trace logging gives the following in terminal:

2025-11-17 11:01:17.549 [trace] [91b0b07] terminalMultiLineLinkDetector#detect text [" *  Executing task: if [ ! -f .vscode/launch.json ]; then cp .vscode/launch.json.linux .vscode/launch.json; fi "]
2025-11-17 11:01:17.550 [trace] [91b0b07] terminalLocalLinkDetector#detect text [" *  Executing task: if [ ! -f .vscode/launch.json ]; then cp .vscode/launch.json.linux .vscode/launch.json; fi "]
2025-11-17 11:01:17.551 [trace] [91b0b07] terminalLocalLinkDetector#detect parsedLinks [[{"path":{"index":30,"text":".vscode/launch.json"}},{"path":{"index":61,"text":".vscode/launch.json.linux"}},{"path":{"index":87,"text":".vscode/launch.json"}}]]
2025-11-17 11:01:17.551 [trace] [91b0b07] terminalLinkHelpers#updateLinkWithRelativeCwd cwd ["\\workspaces"]
2025-11-17 11:01:17.552 [trace] [91b0b07] terminalLocalLinkDetector#detect linkCandidates [["/WINDOWS/system32/\\workspaces/.vscode/launch.json"]]
2025-11-17 11:01:17.553 [trace] [91b0b07] terminalUriLinkDetector#detect computedLinks [[]]
2025-11-17 11:01:17.609 [trace] [91b0b07] terminalLinkHelpers#updateLinkWithRelativeCwd cwd ["\\workspaces"]
2025-11-17 11:01:17.610 [trace] [91b0b07] terminalLocalLinkDetector#detect linkCandidates [["/WINDOWS/system32/\\workspaces/.vscode/launch.json.linux"]]
2025-11-17 11:01:17.668 [trace] [91b0b07] terminalLinkHelpers#updateLinkWithRelativeCwd cwd ["\\workspaces"]
2025-11-17 11:01:17.669 [trace] [91b0b07] terminalLocalLinkDetector#detect linkCandidates [["/WINDOWS/system32/\\workspaces/.vscode/launch.json"]]

[JVApen]

Found a workaround: Add following to the task:

         "options": {
            "cwd": ""
         },

[mnemotic]

Same issue when using WSL2.

[cuttingd]

Just updated to 1.106.0 this morning and am now seeing the same issue on VSCode installed on Windows attempting to launch a process on a remote linux server.

[cuttingd]

Found a workaround: Add following to the task:

         "options": {
            "cwd": ""
         },

This worked for me as well.

[AshokSasi]

Is this added to the launch.json file?

[JVApen]

No, it's added to every task in tasks.json

[AshokSasi]

No, it's added to every task in tasks.json

Thanks, you're a lifesaver

[DasRedy]

Got the same issue with 1.106.1. Sadly the fix from JVAPen didn´t work for me

[anthonykim1]

Thanks for the issue. Did same thing happen on 1.105?

[JVApen]

We did not have the issue on 105, it started when 106 was installed. (I pressed the update button, so am very sure the update is the problem)

[anthonykim1]

I think this might be a dup of #275011