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

Windows terminal doesn't start when using "Run as administrator" #23734

New Issue
Open
opened 2026-01-31 08:50:44 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:50:44 +00:00
Owner
Copy Link

Originally created by @sebandrei on GitHub (Oct 19, 2025).

Windows Terminal version

1.23.12811.0

Windows build number

10.0.26200.0

Other Software

Steps to reproduce

Launch Windows Terminal as administrator from the start menu using the context menu "Run as administrator" command. Or, from Windows Terminal, Ctrl+Click on new Powershell tab.

Expected Behavior

Terminal should open the elevated command prompt.

Actual Behavior

I see the rotating cricle next to the mouse arrow but Windows Terminal (with the elevated prompt) doesn't start. I get the UAC prompt. I click 'Yes'. And then nothing happens.

I'm running Windows Terminal on an admin account.

I've tried the following...

  1. Uninstall/Reinstall from MS Store
  2. Uninstall/Reinstall from GitHub packages

The interesting part is, after I uninstall/reinstall, the first time that I start Windows Terminal, I can run the elevated command prompts. But once I shut down the program and open it again, it doesn't work. (The behaviour then is as described in the first two paragraphs above.)

I've checked the CrashDumps folder in %localdata% but I don't see any Windows Terminal related dumps in there.

Originally created by @sebandrei on GitHub (Oct 19, 2025). ### Windows Terminal version 1.23.12811.0 ### Windows build number 10.0.26200.0 ### Other Software ### Steps to reproduce Launch Windows Terminal as administrator from the start menu using the context menu "Run as administrator" command. Or, from Windows Terminal, Ctrl+Click on new Powershell tab. ### Expected Behavior Terminal should open the elevated command prompt. ### Actual Behavior I see the rotating cricle next to the mouse arrow but Windows Terminal (with the elevated prompt) doesn't start. I get the UAC prompt. I click 'Yes'. And then nothing happens. I'm running Windows Terminal on an admin account. **I've tried the following...** 1. Uninstall/Reinstall from MS Store 2. Uninstall/Reinstall from GitHub packages The interesting part is, after I uninstall/reinstall, the first time that I start Windows Terminal, I can run the elevated command prompts. But once I shut down the program and open it again, it doesn't work. (The behaviour then is as described in the first two paragraphs above.) I've checked the CrashDumps folder in %localdata% but I don't see any Windows Terminal related dumps in there.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:50:44 +00:00
claunia commented 2026-01-31 08:50:45 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 22, 2025):

Hmm... have you actually enabled automatic dump collection? (https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically)

This seems very similar to #19482, but with slightly different repro steps.

If you have a debugger (like modern WinDbg) and the means to do so, you may be able to launch it as Admin and then launch "app package" "Microsoft.WindowsTerminal" from inside it and get some interesting results... 🤔

@DHowett commented on GitHub (Oct 22, 2025): Hmm... have you actually enabled automatic dump collection? (https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically) This seems very similar to #19482, but with slightly different repro steps. If you have a debugger (like [modern WinDbg](https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/)) and the means to do so, you may be able to launch _it_ as Admin and then launch "app package" "Microsoft.WindowsTerminal" from inside it and get some interesting results... 🤔
claunia commented 2026-01-31 08:50:45 +00:00
Author
Owner
Copy Link

@Tentacula commented on GitHub (Oct 26, 2025):

Here is what I have in my logs :

Nom de l’application défaillante WindowsTerminal.exe, version : 1.23.2510.8001, horodatage : 0x68e7198d
Nom du module défaillant : Windows.UI.Xaml.dll, version : 10.0.20348.587, horodatage : 0x29b1211a
Code d’exception : 0xc000027b
Décalage d’erreur : 0x0000000000814b18
ID du processus défaillant : 0x1580
Heure de début de l’application défaillante : 0x01dc4672744bbd24
Chemin d’accès de l’application défaillante : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.23.12811.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Chemin d’accès du module défaillant: C:\Windows\System32\Windows.UI.Xaml.dll
ID de rapport : 06cce0eb-8d71-45c5-98f6-1049dc132387
Nom complet du package défaillant : Microsoft.WindowsTerminal_1.23.12811.0_x64__8wekyb3d8bbwe
ID de l’application relative au package défaillant : App

I'm using Windows Server 2022, without PowerToys (as it seems to make UI.Xaml crash as I've seen on another post)
Here it seems that UI.Xaml is crashing when I run as administrator, otherwise it runs fine without elevated priviledges !

Dump file :

wetransfer file : https://we.tl/t-XQMze24Zil

@Tentacula commented on GitHub (Oct 26, 2025): Here is what I have in my logs : Nom de l’application défaillante WindowsTerminal.exe, version : 1.23.2510.8001, horodatage : 0x68e7198d Nom du module défaillant : Windows.UI.Xaml.dll, version : 10.0.20348.587, horodatage : 0x29b1211a Code d’exception : 0xc000027b Décalage d’erreur : 0x0000000000814b18 ID du processus défaillant : 0x1580 Heure de début de l’application défaillante : 0x01dc4672744bbd24 Chemin d’accès de l’application défaillante : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.23.12811.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Chemin d’accès du module défaillant: C:\Windows\System32\Windows.UI.Xaml.dll ID de rapport : 06cce0eb-8d71-45c5-98f6-1049dc132387 Nom complet du package défaillant : Microsoft.WindowsTerminal_1.23.12811.0_x64__8wekyb3d8bbwe ID de l’application relative au package défaillant : App I'm using Windows Server 2022, without PowerToys (as it seems to make UI.Xaml crash as I've seen on another post) Here it seems that UI.Xaml is crashing when I run as administrator, otherwise it runs fine without elevated priviledges ! Dump file : <!-- Failed to upload "WindowsTerminal.exe.5096.zip" --> wetransfer file : https://we.tl/t-XQMze24Zil
claunia commented 2026-01-31 08:50:45 +00:00
Author
Owner
Copy Link

@sebandrei commented on GitHub (Oct 30, 2025):

Hmm... have you actually enabled automatic dump collection? (https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically)

This seems very similar to #19482, but with slightly different repro steps.

If you have a debugger (like modern WinDbg) and the means to do so, you may be able to launch it as Admin and then launch "app package" "Microsoft.WindowsTerminal" from inside it and get some interesting results... 🤔

Hi! Thank you for replying. In fact, I don't have automatic dump collection enabled. I'll enable it as suggested and try to recreate the issue. However, I won't have access to this machine for the next few weeks so it might take a while...

@sebandrei commented on GitHub (Oct 30, 2025): > Hmm... have you actually enabled automatic dump collection? (https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically) > > This seems very similar to [#19482](https://github.com/microsoft/terminal/issues/19482), but with slightly different repro steps. > > If you have a debugger (like [modern WinDbg](https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/)) and the means to do so, you may be able to launch _it_ as Admin and then launch "app package" "Microsoft.WindowsTerminal" from inside it and get some interesting results... 🤔 Hi! Thank you for replying. In fact, I don't have automatic dump collection enabled. I'll enable it as suggested and try to recreate the issue. However, I won't have access to this machine for the next few weeks so it might take a while...
claunia commented 2026-01-31 08:50:46 +00:00
Author
Owner
Copy Link

@sebandrei commented on GitHub (Dec 20, 2025):

A quick update on this issue:

I am not able to generate a dump file through task mamager because the option is greyed out.

However, I found a method to get Terminal running in admin mode after it refuses to start.

  1. After starting Windows Terminal in admin mode, end the application through the task mamager. (At this stage there will also be a Terminal system tray icon but it will be totally unresponsive.)

  2. Launch Terminal in admin mode. (It should open as expected.)

I'm currently using Version: 1.23.13503.0

I'm not sure if this helps to further diagnose the issue but I will now try other methods to get a dump file...

@sebandrei commented on GitHub (Dec 20, 2025): A quick update on this issue: I am not able to generate a dump file through task mamager because the option is greyed out. However, I found a method to get Terminal running in admin mode after it refuses to start. 1. After starting Windows Terminal in admin mode, end the application through the task mamager. (At this stage there will also be a Terminal system tray icon but it will be totally unresponsive.) 2. Launch Terminal in admin mode. (It should open as expected.) I'm currently using Version: 1.23.13503.0 I'm not sure if this helps to further diagnose the issue but I will now try other methods to get a dump file...
claunia commented 2026-01-31 08:50:46 +00:00
Author
Owner
Copy Link

@ANofsinger-Leer commented on GitHub (Jan 6, 2026):

I was able to get past this by updating Terminal from the MS Store. Now I'm on version 1.23.13503.0

@ANofsinger-Leer commented on GitHub (Jan 6, 2026): I was able to get past this by updating Terminal from the MS Store. Now I'm on version 1.23.13503.0
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-Attention 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#23734
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?