New tabs open as administrator without UAC prompt/consent #20444

Activity

1. James Epp (jamesaepp)

   added

   Issue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on Jul 18, 2026
2. James Epp (jamesaepp)

   added the

   Bug

   issue type on Jul 18, 2026
3. jamesaepp commented on Jul 18, 2026

   

   James Epp (jamesaepp)

   on Jul 18, 2026

   Last edited by jamesaepp

   Author

   More actions

   I'm not certain reproduce steps are accurate anymore.

   I created a fresh 25H2 Windows 11 VM and even after updating everything I can't reproduce the issue.

   It's possible some combination of software or configuration leads to my result, but my main system where I discovered this has lots of software.

   Listing what I'd consider the first suspects in order of recent to older updates/installations:

   • VSCode (1.129.1, updated yesterday)
   • Git for windows (2.55.0.3, updated yesterday)
   • Az CLI 2.88.0
   • PowerShell (7.6.3.0)
4. jamesaepp commented on Jul 18, 2026

   

   James Epp (jamesaepp)

   on Jul 18, 2026

   Last edited by jamesaepp

   Author

   More actions

   OK I think repro steps are instead this and this possibly points to the Terminal now possibly "sharing" a process or something inter-process?

   I didn't take proper snapshots during my VM testing so I can't easily revert back to the bundled terminal version 1.18.10301.0 to gauge if it's in there. Maybe this is expected behavior and I've just never encountered it before.

   Evolved repro steps:

   1. Close all Terminal windows
   2. Win+X , A to open terminal as admin, consent
   3. Win+X , I to open terminal without admin
   4. Open new tabs in terminal window from step # 3. Issue doesn't happen.
   5. Win+R , powershell to open powershell process without admin
   6. Open new tabs in window from step # 5. Issue happens, new tabs have admin
5. jamesaepp commented on Jul 18, 2026

   

   James Epp (jamesaepp)

   on Jul 18, 2026

   Last edited by jamesaepp

   Author

   More actions

   Whether or not this is working as designed was driving me a little nuts, but I found this which might help indicate that no, this is not intended:

   https://learn.microsoft.com/en-us/windows/terminal/faq#is-it-possible-to-mix-admin-and-non-admin-tabs-in-a-windows-terminal-window

   Is it possible to mix admin and non-admin tabs in a Windows Terminal window?

   No, mixing administrator-level permission tabbed shells with those that do not have elevated administrator permission is not supported due to security concerns.
6. jamesaepp commented on Jul 18, 2026

   

   James Epp (jamesaepp)

   on Jul 18, 2026

   Last edited by jamesaepp

   Author

   More actions

   Worked again to get a fresh VM going. I setup my newest test VM to have all updates installed EXCEPT Terminal. All other updates from below list were installed:

   • LCU (July 2026)
   • Microsoft Store (itself and apps, excluding Terminal which was manually paused once it showed up)
   • Windows Update in PC Settings (Defender intelligence, MRT, .NET 2026-07)
   • winget update (manually installed everything except Terminal)

   Issue does not occur in Terminal version 1.18.10301.0 (bundled with my 25H2 installer ISO). Issue occurs in Terminal version 1.24.11911.0.

   New repro steps below (and throughout this guide) assume the user has Administrative rights already.

   Issue does not occur with these steps:

   1. Close all terminal windows
   2. Update terminal to version 1.24.11911.0
   3. Win+X , I to open terminal as non-admin
   4. Win+X , A to open terminal as admin
   5. Win+R, powershell, to open powershell in new terminal window

   Result:

   • Terminal window launched in step 5 does NOT have admin abilities

   Issue does occur with these steps:

   1. Close all terminal windows
   2. Update terminal to version 1.24.11911.0
   3. Win+X , A to open terminal as admin
   4. Win+X , I to open terminal as non-admin
   5. Win+R, powershell, to open powershell in new terminal window

   Results:

   • Terminal window from step 4...
     • Doesn't have the Windows shield graphic indicating privileged shells cannot be created
     • Opening new shells within this terminal window do not open with Administrative rights
   • Terminal window from step 5...
     • Opens by default with a powershell shell without admin privileges
     • Has the Windows shield graphic indicating privileged shells can be created
       
     • New shells launched in this terminal have Administrative rights

   QED

   The order of how you launch your terminal windows with or without admin rights determines what behavior you end up with. Somehow the first Terminal window launched determines the behavior.

   Other thoughts

   This property appears transitive, even if the original window is closed. I haven't done extensive testing on that.
7. DHowett commented on Jul 29, 2026

   

   Dustin L. Howett (DHowett)

   on Jul 29, 2026

   Member

   More actions

   Thank you so much.

   👍React with 👍1Reacted by James Epp
8. Dustin L. Howett (DHowett)

   added

   Tracking-ExternalThis bug isn't resolved, but it's following an external workitem.This bug isn't resolved, but it's following an external workitem.

   and removed

   Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingIt's a new issue that the core contributor team needs to triage at the next triage meeting

   on Jul 29, 2026
9. jamesaepp commented on Oct 3, 2026

   

   James Epp (jamesaepp)

   on Oct 3, 2026

   Author

   More actions

   My installation has updated to version 1.25.2733.0. Appears issue is fixed but I haven't done or plan to test extensively.