[PR #14946] Clearly differentiate running elevated vs. drag/drop breaking #30324

Open
opened 2026-01-31 09:40:07 +00:00 by claunia · 0 comments
Owner

Original Pull Request: https://github.com/microsoft/terminal/pull/14946

State: closed
Merged: Yes


Credit where credit is due - @jboelter did literally all the hard work.

I just separated this out to two elements:

  • Are we running elevated?
  • Can we drag drop?

As we learned in #7754, the builtin administrator can drag drop. But critically, they are also running as admin! The way we had this logic before, we're treat them as unelevated, because we had been overloading the meaning here.

This splits these into two separate functions. Comes with the added benefit of re-adding the elevation shield to the Terminal window for users with UAC disabled (which was missing before) (and can still be disabled).

Closes #13928

Tested on a Win10 VM with EnableLua=0

**Original Pull Request:** https://github.com/microsoft/terminal/pull/14946 **State:** closed **Merged:** Yes --- Credit where credit is due - @jboelter did literally all the hard work. I just separated this out to two elements: * Are we running elevated? * Can we drag drop? As we learned in #7754, the builtin administrator _can_ drag drop. But critically, they are also running as admin! The way we had this logic before, we're treat them as unelevated, because we had been overloading the meaning here. This splits these into two separate functions. Comes with the added benefit of re-adding the elevation shield to the Terminal window for users with UAC disabled (which was missing before) (and can _still_ be disabled). Closes #13928 Tested on a Win10 VM with `EnableLua=0`
claunia added the pull-request label 2026-01-31 09:40:07 +00:00
Sign in to join this conversation.
No Label pull-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#30324