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

WindowsTerminal could not launch under certain installation method with PowerToys 0.95.0 is installed #23745

New Issue
Open
opened 2026-01-31 08:51:18 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:51:18 +00:00
Owner
Copy Link

Originally created by @KateWang-js on GitHub (Oct 23, 2025).

Windows Terminal version

1.23.12811.0

Windows build number

10.0.22631

Other Software

PowerToys 0.95.0

Steps to reproduce

(We used our own Nuget package to install Windows Terminal, but nothing too special other than we put the WindowsTerminal.exe and all the other files in C:\Program Files\WindowsTerminal )
WT always working fine unless we updated PowerToys to 0.95.0 from 0.94.2. Since PowerToys 0.95.0, WT failed to launch with below error (Application event log with error 1000):
Faulting application name: WindowsTerminal.exe, version: 1.23.2510.8001, time stamp: 0x68e7198d
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.5983, time stamp: 0xe081eb6a
Exception code: 0xc000027b
Fault offset: 0x0000000000875470
Faulting process id: 0x0x6460
Faulting application start time: 0x0x1DC43DC358EF426
Faulting application path: C:\Program Files\WindowsTerminal\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: e91910e1-59bc-40bc-9502-1742d6828da9
Faulting package full name:
Faulting package-relative application ID:_

We captured process monitor trace while PowerToys 0.95.0 is installed. Found it failed because WT loaded C:\Program Files\PowerToys\Microsoft.UI.Xaml.Controls.dll, which caused C:\Windows\System32\Windows.UI.Xaml.dll crash. (Added process monitor trace)
In our system environmental path ($env:path), we found "C:\Program Files\PowerToys".

Image

We captured process monitor trace while PowerToys 0.94.2 is installed. Found it also tried to load Microsoft.UI.Xaml.xx but nothing was found from the other Apps' folder , so finally WT loaded C:\Program Files\WindowsTerminal\Microsoft.UI.Xaml.dll and it does not crash. (Added process monitor trace)
In our system environmental path ($env:path), we do not find "C:\Program Files\PowerToys".

Image

Expected Behavior

Windows Terminal launch successfully.

Actual Behavior

WIndowsTerminal.exe failed to launch with below error (Application event log with error 1000):
Faulting application name: WindowsTerminal.exe, version: 1.23.2510.8001, time stamp: 0x68e7198d
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.5983, time stamp: 0xe081eb6a
Exception code: 0xc000027b
Fault offset: 0x0000000000875470
Faulting process id: 0x0x6460
Faulting application start time: 0x0x1DC43DC358EF426
Faulting application path: C:\Program Files\WindowsTerminal\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: e91910e1-59bc-40bc-9502-1742d6828da9
Faulting package full name:
Faulting package-relative application ID:_

Originally created by @KateWang-js on GitHub (Oct 23, 2025). ### Windows Terminal version 1.23.12811.0 ### Windows build number 10.0.22631 ### Other Software PowerToys 0.95.0 ### Steps to reproduce (We used our own Nuget package to install Windows Terminal, but nothing too special other than we put the WindowsTerminal.exe and all the other files in C:\Program Files\WindowsTerminal ) WT always working fine unless we updated PowerToys to 0.95.0 from 0.94.2. Since PowerToys 0.95.0, WT failed to launch with below error (Application event log with error 1000): _Faulting application name: WindowsTerminal.exe, version: 1.23.2510.8001, time stamp: 0x68e7198d Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.5983, time stamp: 0xe081eb6a Exception code: 0xc000027b Fault offset: 0x0000000000875470 Faulting process id: 0x0x6460 Faulting application start time: 0x0x1DC43DC358EF426 Faulting application path: C:\Program Files\WindowsTerminal\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: e91910e1-59bc-40bc-9502-1742d6828da9 Faulting package full name: Faulting package-relative application ID:__ We captured process monitor trace while PowerToys 0.95.0 is installed. Found it failed because WT loaded _C:\Program Files\PowerToys\Microsoft.UI.Xaml.Controls.dll_, which caused _C:\Windows\System32\Windows.UI.Xaml.dll_ crash. (Added process monitor trace) In our system environmental path ($env:path), we found "C:\Program Files\PowerToys". <img width="3594" height="1881" alt="Image" src="https://github.com/user-attachments/assets/f7b9875d-5e7f-4fba-84a7-cb1fad5b5176" /> We captured process monitor trace while PowerToys 0.94.2 is installed. Found it also tried to load Microsoft.UI.Xaml.xx but nothing was found from the other Apps' folder , so finally WT loaded C:\Program Files\WindowsTerminal\Microsoft.UI.Xaml.dll and it does not crash. (Added process monitor trace) In our system environmental path ($env:path), we do not find "C:\Program Files\PowerToys". <img width="2617" height="688" alt="Image" src="https://github.com/user-attachments/assets/28dfcffc-6c20-4268-b456-05f422b59715" /> ### Expected Behavior Windows Terminal launch successfully. ### Actual Behavior WIndowsTerminal.exe failed to launch with below error (Application event log with error 1000): _Faulting application name: WindowsTerminal.exe, version: 1.23.2510.8001, time stamp: 0x68e7198d Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.5983, time stamp: 0xe081eb6a Exception code: 0xc000027b Fault offset: 0x0000000000875470 Faulting process id: 0x0x6460 Faulting application start time: 0x0x1DC43DC358EF426 Faulting application path: C:\Program Files\WindowsTerminal\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: e91910e1-59bc-40bc-9502-1742d6828da9 Faulting package full name: Faulting package-relative application ID:__
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:51:18 +00:00
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#23745
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?