starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal crashes on launch in Windows.UI.Xaml.dll #4726

New Issue
Closed
opened 2026-01-30 23:55:02 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 23:55:02 +00:00
Owner
Copy Link

Originally created by @jghal on GitHub (Oct 30, 2019).

Environment

OS:

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Terminal:

> get-appxpackage Microsoft.WindowsTerminal

Name              : Microsoft.WindowsTerminal
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X64
ResourceId        :
Version           : 0.6.2951.0
PackageFullName   : Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
InstallLocation   : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
IsFramework       : False
PackageFamilyName : Microsoft.WindowsTerminal_8wekyb3d8bbwe
PublisherId       : 8wekyb3d8bbwe
IsResourcePackage : False
IsBundle          : False
IsDevelopmentMode : False
NonRemovable      : False
Dependencies      : {Microsoft.VCLibs.140.00_14.0.27323.0_x64__8wekyb3d8bbwe,
                    Microsoft.VCLibs.140.00.UWPDesktop_14.0.27629.0_x64__8wekyb3d8bbwe}
IsPartiallyStaged : False
SignatureKind     : Store
Status            : Ok

I suspect I'm seeing the crash mentioned in PR #3027. While I can't recall the specific build number for Terminal that I first installed on this particular machine, it was one of the 0.5 releases. all versions I've tried from that first one to the version listed above by get-appxpackage have failed this same way (though I can't faithfully recall if it's been the same Event Viewer entry as reported below). I have used Feedback hub twice, I believe with different versions.

Steps to reproduce

Click Windows Terminal (Preview) in Start menu

Expected behavior

Application launches

Actual behavior

Empty Window frame is drawn, then closes. This is in Event Viewer under Windows Logs > Application

Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.356, time stamp: 0x0825b5b0
Exception code: 0xc000027b
Fault offset: 0x0000000000712cf0
Faulting process id: 0x2b68
Faulting application start time: 0x01d58f6c56566369
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 86621d0f-a0dd-4c17-9530-85a0b42ed873
Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Originally created by @jghal on GitHub (Oct 30, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment OS: ```none Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 ``` Terminal: ```none > get-appxpackage Microsoft.WindowsTerminal Name : Microsoft.WindowsTerminal Publisher : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US Architecture : X64 ResourceId : Version : 0.6.2951.0 PackageFullName : Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe InstallLocation : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe IsFramework : False PackageFamilyName : Microsoft.WindowsTerminal_8wekyb3d8bbwe PublisherId : 8wekyb3d8bbwe IsResourcePackage : False IsBundle : False IsDevelopmentMode : False NonRemovable : False Dependencies : {Microsoft.VCLibs.140.00_14.0.27323.0_x64__8wekyb3d8bbwe, Microsoft.VCLibs.140.00.UWPDesktop_14.0.27629.0_x64__8wekyb3d8bbwe} IsPartiallyStaged : False SignatureKind : Store Status : Ok ``` I suspect I'm seeing the crash mentioned in PR #3027. While I can't recall the specific build number for Terminal that I first installed on this particular machine, it was one of the 0.5 releases. all versions I've tried from that first one to the version listed above by `get-appxpackage` have failed this same way (though I can't faithfully recall if it's been the same Event Viewer entry as reported below). I have used Feedback hub twice, I believe with different versions. # Steps to reproduce Click `Windows Terminal (Preview)` in Start menu # Expected behavior Application launches # Actual behavior Empty Window frame is drawn, then closes. This is in _Event Viewer_ under _Windows Logs > Application_ ```none Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2 Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.356, time stamp: 0x0825b5b0 Exception code: 0xc000027b Fault offset: 0x0000000000712cf0 Faulting process id: 0x2b68 Faulting application start time: 0x01d58f6c56566369 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: 86621d0f-a0dd-4c17-9530-85a0b42ed873 Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ```
claunia added the Resolution-Duplicate label 2026-01-30 23:55:02 +00:00
claunia commented 2026-01-30 23:55:03 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 30, 2019):

Thanks for the report! The crash from #3027 was in TerminalControl.dll, not Windows.UI.Xaml.dll.

Would you mind sharing feedback, and your profiles.json (from %LOCALAPPDATA%\packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\profiles.json)?

/feedback

@DHowett-MSFT commented on GitHub (Oct 30, 2019): Thanks for the report! The crash from #3027 was in TerminalControl.dll, not Windows.UI.Xaml.dll. Would you mind sharing feedback, and your `profiles.json` (from `%LOCALAPPDATA%\packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\profiles.json`)? /feedback
claunia commented 2026-01-30 23:55:03 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 30, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Oct 30, 2019): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-30 23:55:04 +00:00
Author
Owner
Copy Link

@chayanbaner commented on GitHub (Oct 31, 2019):

I am facing the same issue....
please check https://aka.ms/AA6fsnn

@chayanbaner commented on GitHub (Oct 31, 2019): I am facing the same issue.... please check https://aka.ms/AA6fsnn
claunia commented 2026-01-30 23:55:04 +00:00
Author
Owner
Copy Link

@jghal commented on GitHub (Oct 31, 2019):

ere's the two I filed in Feedback Hub

https://aka.ms/AA6g4mf
https://aka.ms/AA6f8wz

GitHub won't let me attach a json file, so here it is zipped. It should be the default one.

profiles.zip

I've tried using the App Settings > Repair/Reset and also deleting the whole %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_* directory, with no effect.

@jghal commented on GitHub (Oct 31, 2019): ere's the two I filed in Feedback Hub https://aka.ms/AA6g4mf https://aka.ms/AA6f8wz GitHub won't let me attach a json file, so here it is zipped. It should be the default one. [profiles.zip](https://github.com/microsoft/terminal/files/3793787/profiles.zip) I've tried using the _App Settings > Repair/Reset_ and also deleting the whole `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_*` directory, with no effect.
claunia commented 2026-01-30 23:55:04 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 4, 2019):

This looks like a /dupe of #2277 (even though this doesn't involve resizing.)

@DHowett-MSFT commented on GitHub (Nov 4, 2019): This looks like a /dupe of #2277 (even though this doesn't involve resizing.)
claunia commented 2026-01-30 23:55:04 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 4, 2019):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 4, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Resolution-Duplicate
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#4726
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?