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

Drag & Drop Folder to Elevated Terminal Not Working #22397

New Issue
Closed
opened 2026-01-31 08:12:00 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:12:00 +00:00
Owner
Copy Link

Originally created by @arpan3t on GitHub (Oct 14, 2024).

Windows Terminal version

1.20.11781.0

Windows build number

10.0.19045

Other Software

No response

Steps to reproduce

  1. Open Windows Terminal as administrator.
  2. Open File Explorer (explorer.exe) to a directory that contains a subdirectory.
  3. Drag subdirectory from File Explorer to elevated Windows Terminal new tab icon.

Expected Behavior

New tab using default profile should open with the working directory of the subdirectory that was dragged over, as detailed here.

Actual Behavior

🚫Windows Unavailable mouse pointer icon is displayed, and dropping the folder does nothing.

Tried launching explorer.exe from the same elevated Windows Terminal but get the same results. Looks like the drag & drop feature only works for non-elevated Windows Terminal processes, which does work in the same environment btw. Not sure if this is intentional to prevent some sort of privilege escalation scenario or something, but it's not a deal imo. Just saw the feature in the documentation, but I doubt I'd use it regularly. Maybe just add a note to the documentation that it only works in non-elevated Windows Terminals.

Originally created by @arpan3t on GitHub (Oct 14, 2024). ### Windows Terminal version 1.20.11781.0 ### Windows build number 10.0.19045 ### Other Software _No response_ ### Steps to reproduce 1. Open Windows Terminal as administrator. 2. Open File Explorer (explorer.exe) to a directory that contains a subdirectory. 3. Drag subdirectory from File Explorer to elevated Windows Terminal new tab icon. ### Expected Behavior New tab using default profile should open with the working directory of the subdirectory that was dragged over, as detailed [here](https://learn.microsoft.com/en-us/windows/terminal/tips-and-tricks#drag-and-drop-filefolder-to-open). ### Actual Behavior 🚫Windows Unavailable mouse pointer icon is displayed, and dropping the folder does nothing. Tried launching explorer.exe from the same elevated Windows Terminal but get the same results. Looks like the drag & drop feature only works for non-elevated Windows Terminal processes, which does work in the same environment btw. Not sure if this is intentional to prevent some sort of privilege escalation scenario or something, but it's not a deal imo. Just saw the feature in the documentation, but I doubt I'd use it regularly. Maybe just add a note to the documentation that it only works in non-elevated Windows Terminals.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:12:00 +00:00
claunia commented 2026-01-31 08:12:01 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 14, 2024):

Not sure if this is intentional to prevent some sort of privilege escalation scenario or something

This is a Windows platform restriction that is also present in the original console host. The clipboard is the only "approved" way to get content from a medium-integrity process to a high-integrity one on the same Window Station.

We'll add a documentation note! Sorry!

@DHowett commented on GitHub (Oct 14, 2024): > Not sure if this is intentional to prevent some sort of privilege escalation scenario or something This is a Windows platform restriction that is also present in the original console host. The clipboard is the only "approved" way to get content from a medium-integrity process to a high-integrity one on the same Window Station. We'll add a documentation note! Sorry!
claunia commented 2026-01-31 08:12:02 +00:00
Author
Owner
Copy Link

@c834606877 commented on GitHub (Oct 21, 2024):

So many users raise issue here, it indicates that this Drag&Drop feature is necessary for daily usage.
So, Please make it as a optional feature for those users want use it at take self own risk way!
Do NOT break the user's usage habits. even you have strong security reason, you can take a msgbox as warning.

@c834606877 commented on GitHub (Oct 21, 2024): So many users raise issue here, it indicates that this Drag&Drop feature is necessary for daily usage. So, Please make it as a optional feature for those users want use it at take self own risk way! Do NOT break the user's usage habits. even you have strong security reason, you can take a msgbox as warning.
claunia commented 2026-01-31 08:12:02 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 21, 2024):

There can't possibly be "user's habits" yet, since what you're asking for has never worked on any Windows version before. But we'll definitely take it into consideration for future versions.

@lhecker commented on GitHub (Oct 21, 2024): There can't possibly be "user's habits" yet, since what you're asking for has never worked on any Windows version before. But we'll definitely take it into consideration for future versions.
claunia commented 2026-01-31 08:12:02 +00:00
Author
Owner
Copy Link

@Quaraxkad commented on GitHub (Dec 28, 2024):

This is a Windows platform restriction that is also present in the original console host. The clipboard is the only "approved" way to get content from a medium-integrity process to a high-integrity one on the same Window Station.

Are you sure that's right? For me, drag+drop of a file or folder does work in normal conhost window but NOT Terminal. Since switching to Terminal as my default i have not been able to drag+drop files or folders to "paste" their paths. I used this extensively in conhost. I searched and see a lot of posts about similar issues but they're almost all unclear if they're talking about the same feature I am.

@Quaraxkad commented on GitHub (Dec 28, 2024): > This is a Windows platform restriction that is also present in the original console host. The clipboard is the only "approved" way to get content from a medium-integrity process to a high-integrity one on the same Window Station. Are you sure that's right? For me, drag+drop of a file or folder does work in normal conhost window but NOT Terminal. Since switching to Terminal as my default i have not been able to drag+drop files or folders to "paste" their paths. I used this *extensively* in conhost. I searched and see a lot of posts about similar issues but they're almost all unclear if they're talking about the same feature I am.
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 Issue-Bug Needs-Triage
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#22397
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?