Skip to content

Normalize Windows drive letter when comparing cwd and userHome (fix #293049)#293065

Merged
anthonykim1 merged 1 commit intomicrosoft:mainfrom
gjsjohnmurray:fix-293049
Feb 5, 2026
Merged

Normalize Windows drive letter when comparing cwd and userHome (fix #293049)#293065
anthonykim1 merged 1 commit intomicrosoft:mainfrom
gjsjohnmurray:fix-293049

Conversation

@gjsjohnmurray
Copy link
Contributor

This PR fixes #293049.

Test by following the repro steps on the issue to confirm the fix.

Please consider taking this as a candidate for 1.109 recovery release.

Copilot AI review requested due to automatic review settings February 5, 2026 09:54
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a bug where terminal creation would incorrectly fail due to case-sensitive comparison of Windows drive letters. The issue occurred when attaching to a Docker container on Windows, where the cwd and userHome paths had different drive letter casing (e.g., "C:" vs "c:").

Changes:

  • Normalize drive letters before comparing cwd and userHome paths to handle case differences on Windows
  • Fix misleading error message to correctly state "empty workspace" instead of "untrusted workspace"

@anthonykim1 anthonykim1 added this to the February 2026 milestone Feb 5, 2026
@anthonykim1
Copy link
Contributor

Thank you! @gjsjohnmurray

@anthonykim1 anthonykim1 merged commit f47e17c into microsoft:main Feb 5, 2026
21 of 23 checks passed
@gjsjohnmurray gjsjohnmurray deleted the fix-293049 branch February 6, 2026 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The terminal process failed to launch because of Windows drive-letter case-difference

5 participants