starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Crash on RDP connection #14222

New Issue
Closed
opened 2026-01-31 04:04:18 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 04:04:18 +00:00
Owner
Copy Link

Originally created by @shuffle2 on GitHub (Jun 13, 2021).

Windows Terminal version (or Windows build number)

1.8.1521.0

Other Software

Microsoft Windows [Version 10.0.19042.1055]

Steps to reproduce

Start Terminal (either from local session or RDP)
Connect a new RDP session
Observe Terminal (and any child processes) is no longer running.

Expected Behavior

Terminal continues running across RDP connects/disconnects.

Actual Behavior

I see the following crash logs in Event Viewer:

Faulting application name: WindowsTerminal.exe, version: 1.8.2106.1001, time stamp: 0x60b64ad3
Faulting module name: Microsoft.UI.Xaml.dll, version: 2.5.2012.2003, time stamp: 0x5fc87886
Exception code: 0xc0000005
Fault offset: 0x00000000000df4af
Faulting process id: 0x502c
Faulting application start time: 0x01d75fde99430238
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\Microsoft.UI.Xaml.dll
Report Id: 6cd58efd-60b4-47ca-a0fd-f325706fc589
Faulting package full name: Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Fault bucket 2238112546877327133, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.8.2106.1001
P4: 60b64ad3
P5: Microsoft.UI.Xaml.dll
P6: 2.5.2012.2003
P7: 5fc87886
P8: c0000005
P9: 00000000000df4af
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER904C.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9157.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9167.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9175.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9195.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_ea24f84bb2ad8ddcd6855a771669148aa5dbf98_60528276_beebf310-482c-4636-b3a3-9d972986f8ca

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6cd58efd-60b4-47ca-a0fd-f325706fc589
Report Status: 268435456
Hashed bucket: d56910dc0d52099aaf0f5f80dbf7c71d
Cab Guid: 0
Originally created by @shuffle2 on GitHub (Jun 13, 2021). ### Windows Terminal version (or Windows build number) 1.8.1521.0 ### Other Software Microsoft Windows [Version 10.0.19042.1055] ### Steps to reproduce Start Terminal (either from local session or RDP) Connect a new RDP session Observe Terminal (and any child processes) is no longer running. ### Expected Behavior Terminal continues running across RDP connects/disconnects. ### Actual Behavior I see the following crash logs in Event Viewer: ``` Faulting application name: WindowsTerminal.exe, version: 1.8.2106.1001, time stamp: 0x60b64ad3 Faulting module name: Microsoft.UI.Xaml.dll, version: 2.5.2012.2003, time stamp: 0x5fc87886 Exception code: 0xc0000005 Fault offset: 0x00000000000df4af Faulting process id: 0x502c Faulting application start time: 0x01d75fde99430238 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\Microsoft.UI.Xaml.dll Report Id: 6cd58efd-60b4-47ca-a0fd-f325706fc589 Faulting package full name: Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` ``` Fault bucket 2238112546877327133, type 5 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe P2: praid:App P3: 1.8.2106.1001 P4: 60b64ad3 P5: Microsoft.UI.Xaml.dll P6: 2.5.2012.2003 P7: 5fc87886 P8: c0000005 P9: 00000000000df4af P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER904C.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9157.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9167.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9175.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9195.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_ea24f84bb2ad8ddcd6855a771669148aa5dbf98_60528276_beebf310-482c-4636-b3a3-9d972986f8ca Analysis symbol: Rechecking for solution: 0 Report Id: 6cd58efd-60b4-47ca-a0fd-f325706fc589 Report Status: 268435456 Hashed bucket: d56910dc0d52099aaf0f5f80dbf7c71d Cab Guid: 0 ```
claunia added the Resolution-Duplicate label 2026-01-31 04:04:18 +00:00
claunia commented 2026-01-31 04:04:19 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 15, 2021):

Okay this might be insane, but could you repro this with the Feedback Hub? That'll get us a stack trace we can use to actually identify the root cause here.

/feedback

@zadjii-msft commented on GitHub (Jun 15, 2021): Okay this might be insane, but could you repro this with the Feedback Hub? That'll get us a stack trace we can use to actually identify the root cause here. /feedback
claunia commented 2026-01-31 04:04:20 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 15, 2021):

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 (Jun 15, 2021): 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-31 04:04:20 +00:00
Author
Owner
Copy Link

@shuffle2 commented on GitHub (Jun 16, 2021):

I don't have WER uploads enabled on that machine.
I tried to build a debug build of Terminal and reproduce, but now the issue doesn't even happen on the build from the Store, either 🤔
Oh well, can probably close this until it happens again.

@shuffle2 commented on GitHub (Jun 16, 2021): I don't have WER uploads enabled on that machine. I tried to build a debug build of Terminal and reproduce, but now the issue doesn't even happen on the build from the Store, either 🤔 Oh well, can probably close this until it happens again.
claunia commented 2026-01-31 04:04:20 +00:00
Author
Owner
Copy Link

@shuffle2 commented on GitHub (Jun 30, 2021):

My crash stack is the same as https://github.com/microsoft/terminal/issues/10520

@shuffle2 commented on GitHub (Jun 30, 2021): My crash stack is the same as https://github.com/microsoft/terminal/issues/10520
claunia commented 2026-01-31 04:04:20 +00:00
Author
Owner
Copy Link

@shuffle2 commented on GitHub (Jul 29, 2021):

Going to reopen as it still occurs (now on Version: 1.9.1942.0), and is very frustrating :/

@shuffle2 commented on GitHub (Jul 29, 2021): Going to reopen as it still occurs (now on Version: 1.9.1942.0), and is very frustrating :/
claunia commented 2026-01-31 04:04:20 +00:00
Author
Owner
Copy Link

@Dan-Albrecht commented on GitHub (Aug 17, 2021):

Hitting this as well. Can we use this issue to track pulling in the latest Microsoft.UI.Xaml.dll which should include https://github.com/microsoft/microsoft-ui-xaml/pull/5201 and allegedly fix this?

@Dan-Albrecht commented on GitHub (Aug 17, 2021): Hitting this as well. Can we use this issue to track pulling in the latest Microsoft.UI.Xaml.dll which should include https://github.com/microsoft/microsoft-ui-xaml/pull/5201 and allegedly fix this?
claunia commented 2026-01-31 04:04:20 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 17, 2021):

Since this is fixed in https://github.com/microsoft/microsoft-ui-xaml/pull/5201, which is in MUX 2.6.1, then I think we can just use the existing issue we have for "update to 2.6". Thanks all (sorry this dropped out of the triage queue)

/dup #10508

@zadjii-msft commented on GitHub (Aug 17, 2021): Since this is fixed in https://github.com/microsoft/microsoft-ui-xaml/pull/5201, which is in MUX 2.6.1, then I think we can just use the existing issue we have for "update to 2.6". Thanks all (sorry this dropped out of the triage queue) /dup #10508
claunia commented 2026-01-31 04:04:21 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 17, 2021):

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 (Aug 17, 2021): 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#14222
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?