starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

"Open in Windows Terminal" doesn't work on renamed drive letter #13464

New Issue
Closed
opened 2026-01-31 03:43:25 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 03:43:25 +00:00
Owner
Copy Link

Originally created by @prabhumns on GitHub (Apr 15, 2021).

Windows Terminal version (or Windows build number)

1.8.1032.0

Other Software

Create and format hard disk partitions

Steps to reproduce

Change the drive letter to any one of the attached drives and check the context menu

Expected Behavior

The 'Open Windows Terminal Here' option should exist even after a drive letter has been changed.

Actual Behavior

I have recently re-installed windows insider version and it came with windows terminal (non preview) already installed in it. I can see 'Open Windows Terminal here' option in the context menu of folders (even in background). Then I installed windows terminal preview in my system, then the context menu option is opening the terminal preview version instead of non preview version. After a couple of days I re assigned drive letter for non windows drives, from then I cant see 'open windows terminal here' option in the context menu (even in the shift + right click context menu).

Originally created by @prabhumns on GitHub (Apr 15, 2021). ### Windows Terminal version (or Windows build number) 1.8.1032.0 ### Other Software Create and format hard disk partitions ### Steps to reproduce Change the drive letter to any one of the attached drives and check the context menu ### Expected Behavior The 'Open Windows Terminal Here' option should exist even after a drive letter has been changed. ### Actual Behavior I have recently re-installed windows insider version and it came with windows terminal (non preview) already installed in it. I can see 'Open Windows Terminal here' option in the context menu of folders (even in background). Then I installed windows terminal preview in my system, then the context menu option is opening the terminal preview version instead of non preview version. After a couple of days I re assigned drive letter for non windows drives, from then I cant see 'open windows terminal here' option in the context menu (even in the shift + right click context menu).
claunia commented 2026-01-31 03:43:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 15, 2021):

After a couple of days I re assigned drive letter for non windows drives, from then I cant see 'open windows terminal here' option in the context menu (even in the shift + right click context menu).

Hmm. Lemme reach out to my file explorer contact, see if he has ever heard of anything like this.

By any chance, have you restarted your PC since updating the drive letter? explorer.exe is notoriously finicky about caching the context menu entries. Maybe it's possible it's just a bad cache...

@zadjii-msft commented on GitHub (Apr 15, 2021): > After a couple of days I re assigned drive letter for non windows drives, from then I cant see 'open windows terminal here' option in the context menu (even in the shift + right click context menu). Hmm. Lemme reach out to my file explorer contact, see if he has ever heard of anything like this. By any chance, have you restarted your PC since updating the drive letter? `explorer.exe` is notoriously finicky about caching the context menu entries. Maybe it's possible it's just a bad cache...
claunia commented 2026-01-31 03:43:28 +00:00
Author
Owner
Copy Link

@prabhumns commented on GitHub (Apr 15, 2021):

I restarted multiple times since then

@prabhumns commented on GitHub (Apr 15, 2021): I restarted multiple times since then
claunia commented 2026-01-31 03:43:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 16, 2021):

Okay, I've filed a bug internally. This is now MSFT:32535359

@zadjii-msft commented on GitHub (Apr 16, 2021): Okay, I've filed a bug internally. This is now MSFT:32535359
claunia commented 2026-01-31 03:43:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 11, 2022):

Huh. This came back to us internally 😕

Sorry it's been a LONG time OP. What OS version are you on/? There's been a pile of bugs with context menus on drive letters that I think were all sorted out in the Windows 11 timeframe...

@zadjii-msft commented on GitHub (Aug 11, 2022): Huh. This came back to us internally 😕 Sorry it's been a LONG time OP. What OS version are you on/? There's been a pile of bugs with context menus on drive letters that I think were all sorted out in the Windows 11 timeframe...
claunia commented 2026-01-31 03:43:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 11, 2022):

After a couple of days I re assigned drive letter for non windows drives, from then I cant see 'open windows terminal here' option in the context menu (even in the shift + right click context menu

Wait, you mean for some file like f:\foo\bar, where f:\ is some drive that used to be d:\, that doesn't work anymore?

#6654 suggests that Terminal still won't ever work on any drive directly in explorer, but it should work for any subdirectory in a drive...

@zadjii-msft commented on GitHub (Aug 11, 2022): > After a couple of days I re assigned drive letter for non windows drives, from then I cant see 'open windows terminal here' option in the context menu (even in the shift + right click context menu Wait, you mean for some file like `f:\foo\bar`, where `f:\` is some drive that used to be `d:\`, that doesn't work anymore? #6654 suggests that Terminal still won't ever work on any _drive_ directly in explorer, but it should work for any subdirectory in a drive...
claunia commented 2026-01-31 03:43:29 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 15, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 15, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-ShellExtension Issue-Bug Needs-Author-Feedback No-Recent-Activity Product-Terminal Tracking-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13464
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?