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

Crash on launch / creating new tab when using RDP #3723

New Issue
Closed
opened 2026-01-30 23:28:27 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 23:28:27 +00:00
Owner
Copy Link

Originally created by @mttradebyte on GitHub (Sep 3, 2019).

Originally assigned to: @cinnamon-msft on GitHub.

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.295]
Windows Terminal version (if applicable): 0.4.2382.0_x64

Any other software? 
- Remote Desktop
- Not sure if relevant, but Ubuntu WSL is the default profile

Steps to reproduce

  1. Use RDP to access your device
  2. Either start the terminal fresh, or close a tab, or try to open a new tab.

Expected behavior

Terminal should open / tab should open / close.

Actual behavior

The terminal will not start when using RDP to connect to my laptop. It brings up the outline, then crashes (eventvwr log below). It will also crash if I try to close a tab or open a tab. General use, like switching tabs or generally interacting with the window (resizing, maximising, etc.) works fine. This is reproducible 100% of the time. It never fails to open when I'm physically on the device, but it is intermittent if I can then switch to RDP and continue to use it. Potentially related to #2183?

EDIT: I've done some more fiddling and by going into the graphics settings and by forcing the app to use the "Power Saving" (onboard) GPU, it launches and works via RDP as intended.

Faulting application name: WindowsTerminal.exe, version: 1.0.1908.26002, time stamp: 0x5d641823
Faulting module name: ucrtbase.dll, version: 10.0.18362.267, time stamp: 0x080a13f7
Exception code: 0xc0000409
Fault offset: 0x000000000006d33e
Faulting process ID: 0x54d4
Faulting application start time: 0x01d562452690fb35
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 7edb0c83-abc5-43dc-b02f-f1bb04084933
Faulting package full name: Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Originally created by @mttradebyte on GitHub (Sep 3, 2019). Originally assigned to: @cinnamon-msft on GitHub. # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18362.295] Windows Terminal version (if applicable): 0.4.2382.0_x64 Any other software? - Remote Desktop - Not sure if relevant, but Ubuntu WSL is the default profile ``` # Steps to reproduce 1. Use RDP to access your device 2. Either start the terminal fresh, or close a tab, or try to open a new tab. # Expected behavior Terminal should open / tab should open / close. # Actual behavior The terminal will not start when using RDP to connect to my laptop. It brings up the outline, then crashes (eventvwr log below). It will also crash if I try to close a tab or open a tab. General use, like switching tabs or generally interacting with the window (resizing, maximising, etc.) works fine. This is reproducible 100% of the time. It never fails to open when I'm physically on the device, but it is intermittent if I can then switch to RDP and continue to use it. Potentially related to #2183? EDIT: I've done some more fiddling and by going into the graphics settings and by forcing the app to use the "Power Saving" (onboard) GPU, it launches and works via RDP as intended. Faulting application name: WindowsTerminal.exe, version: 1.0.1908.26002, time stamp: 0x5d641823 Faulting module name: ucrtbase.dll, version: 10.0.18362.267, time stamp: 0x080a13f7 Exception code: 0xc0000409 Fault offset: 0x000000000006d33e Faulting process ID: 0x54d4 Faulting application start time: 0x01d562452690fb35 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report ID: 7edb0c83-abc5-43dc-b02f-f1bb04084933 Faulting package full name: Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App
claunia commented 2026-01-30 23:28:29 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 4, 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 (Sep 4, 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:28:30 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 8, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Sep 8, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-30 23:28:30 +00:00
Author
Owner
Copy Link

@mttradebyte commented on GitHub (Sep 9, 2019):

Feedback Hub link here: https://aka.ms/AA6017r

@mttradebyte commented on GitHub (Sep 9, 2019): Feedback Hub link here: https://aka.ms/AA6017r
claunia commented 2026-01-30 23:28:31 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 28, 2020):

I think we might have fixed this in one of our recent crash purges. Would you mind seeing if this still repros? We were never able to hit it ourselves. Thanks!

@DHowett-MSFT commented on GitHub (Feb 28, 2020): I think we might have fixed this in one of our recent crash purges. Would you mind seeing if this still repros? We were never able to hit it ourselves. Thanks!
claunia commented 2026-01-30 23:28:31 +00:00
Author
Owner
Copy Link

@mttradebyte commented on GitHub (Jun 22, 2020):

Sorry for the delay in responding, completely forgot about this and the use case wasn't as prevalent anymore. I can verify that it is indeed resolved. Thanks for your efforts.

@mttradebyte commented on GitHub (Jun 22, 2020): Sorry for the delay in responding, completely forgot about this and the use case wasn't as prevalent anymore. I can verify that it is indeed resolved. Thanks for your efforts.
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 Area-Quality Issue-Bug Needs-Attention Needs-Tag-Fix Priority-1 Product-Terminal Resolution-No-Repro Severity-Crash
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#3723
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?