Terminal crashed on launch while accessing system through RDP #4239

Closed
opened 2026-01-30 23:41:47 +00:00 by claunia · 8 comments
Owner

Originally created by @asyncpoint on GitHub (Oct 3, 2019).

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.295]
Windows Terminal version (if applicable): Windows Terminal (Preview) Version: 0.5.2681.0

Steps to reproduce

  1. Install the latest (0.5.2681.0) windows terminal on windows 10 (1903), launch it and it works.
  2. RDP (using window RDP tool) your system from another windows computer
  3. Try to launch the windows terminal, it opens and crashed instantly

Expected behavior

Terminal should work while accessing it through RDP session

Actual behavior

Terminal crashed with below given windows event log entry:
Faulting application name: WindowsTerminal.exe, version: 1.0.1909.25001, time stamp: 0x5d8b1a61
Faulting module name: TerminalControl.dll, version: 1.0.1909.25001, time stamp: 0x5d8b194b
Exception code: 0xc0000409
Fault offset: 0x0000000000052691
Faulting process id: 0x1d3c
Faulting application start time: 0x01d579d25edff7c0
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.5.2681.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.5.2681.0_x64__8wekyb3d8bbwe\TerminalControl.dll
Report Id: 98b3041c-8f29-4d12-a639-8deebd0f828f
Faulting package full name: Microsoft.WindowsTerminal_0.5.2681.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Originally created by @asyncpoint on GitHub (Oct 3, 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 ```none Windows build number: Microsoft Windows [Version 10.0.18362.295] Windows Terminal version (if applicable): Windows Terminal (Preview) Version: 0.5.2681.0 ``` # Steps to reproduce 1. Install the latest (0.5.2681.0) windows terminal on windows 10 (1903), launch it and it works. 2. RDP (using window RDP tool) your system from another windows computer 3. Try to launch the windows terminal, it opens and crashed instantly # Expected behavior Terminal should work while accessing it through RDP session # Actual behavior Terminal crashed with below given windows event log entry: Faulting application name: WindowsTerminal.exe, version: 1.0.1909.25001, time stamp: 0x5d8b1a61 Faulting module name: TerminalControl.dll, version: 1.0.1909.25001, time stamp: 0x5d8b194b Exception code: 0xc0000409 Fault offset: 0x0000000000052691 Faulting process id: 0x1d3c Faulting application start time: 0x01d579d25edff7c0 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.5.2681.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.5.2681.0_x64__8wekyb3d8bbwe\TerminalControl.dll Report Id: 98b3041c-8f29-4d12-a639-8deebd0f828f Faulting package full name: Microsoft.WindowsTerminal_0.5.2681.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App
Author
Owner

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

/feedback

@DHowett-MSFT commented on GitHub (Oct 3, 2019): /feedback
Author
Owner

@ghost commented on GitHub (Oct 3, 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 3, 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)
Author
Owner

@oising commented on GitHub (Oct 3, 2019):

It's funny -- my terminal instance crashed while I was on lunch also. Seriously.

@oising commented on GitHub (Oct 3, 2019): It's funny -- my terminal instance crashed while I was on lunch also. Seriously.
Author
Owner

@MikeJerred commented on GitHub (Oct 6, 2019):

I also get a crash on startup. It was working fine a few days ago, but now it crashes every time I try to start it. Possibly caused by a recent update to Windows - I installed an update recently.

Currently OS build is: Windows 10 x64 version 1903, OS build: 18362.356

@MikeJerred commented on GitHub (Oct 6, 2019): I also get a crash on startup. It was working fine a few days ago, but now it crashes every time I try to start it. Possibly caused by a recent update to Windows - I installed an update recently. Currently OS build is: Windows 10 x64 version 1903, OS build: 18362.356
Author
Owner

@asyncpoint commented on GitHub (Oct 8, 2019):

It's funny -- my terminal instance crashed while I was on lunch also. Seriously.

When you are hungry and the lunchtime you can eat an 'a', but not anymore 😉

@asyncpoint commented on GitHub (Oct 8, 2019): > > > It's funny -- my terminal instance crashed while I was on lunch also. Seriously. When you are hungry and the lunchtime you can eat an 'a', but not anymore 😉
Author
Owner

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

/feedback

This still needs a feedback item, but the bot un-marked it as such. Sorry/thanks!

@DHowett-MSFT commented on GitHub (Oct 23, 2019): /feedback This still needs a feedback item, but the bot un-marked it as such. Sorry/thanks!
Author
Owner

@ghost commented on GitHub (Oct 23, 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 23, 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)
Author
Owner

@ghost commented on GitHub (Oct 27, 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 (Oct 27, 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**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4239