Exiting Windows Terminal Triggers System Error #16312

Closed
opened 2026-01-31 05:03:43 +00:00 by claunia · 5 comments
Owner

Originally created by @JuliusDegesys on GitHub (Dec 29, 2021).

Relatively consistently (although not 100% of the time), exiting the windows terminal from WSL2 - Ubuntu 20.04 triggers the following popup:
Exception Processing Message - 0xc0000005 - Unexpected Parameters:
image

This happens when I type in exit or when I click on the top right X

I'm happy to help troubleshoot; however, I'm not really a power Windows user. Any guidance would be appreciated. Thanks!

I'm running Windows Terminal version 1.11.34710.0.

Windows specifications:
Edition: Windows 10 Pro
Version: 20H2
OS Build: 19042.1415
Experience: Windows Feature Experience Pack 120.2212.3920.0

Originally created by @JuliusDegesys on GitHub (Dec 29, 2021). Relatively consistently (although not 100% of the time), exiting the windows terminal from WSL2 - Ubuntu 20.04 triggers the following popup: Exception Processing Message - 0xc0000005 - Unexpected Parameters: ![image](https://user-images.githubusercontent.com/3232103/147705481-e38e923d-8a04-4e1a-9ba2-0804c80d0c32.png) This happens when I type in `exit` or when I click on the top right X I'm happy to help troubleshoot; however, I'm not really a power Windows user. Any guidance would be appreciated. Thanks! I'm running Windows Terminal version 1.11.34710.0. Windows specifications: Edition: Windows 10 Pro Version: 20H2 OS Build: 19042.1415 Experience: Windows Feature Experience Pack 120.2212.3920.0
Author
Owner

@zadjii-msft commented on GitHub (Jan 3, 2022):

That's... wild. Never seen a MessageBox that looks quite like that in my time. Maybe we'd be able to capture whatever's causing this with a Feedback Hub trace: /feedback

@zadjii-msft commented on GitHub (Jan 3, 2022): That's... wild. Never seen a MessageBox that looks quite like that in my time. Maybe we'd be able to capture whatever's causing this with a Feedback Hub trace: /feedback
Author
Owner

@ghost commented on GitHub (Jan 3, 2022):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@ghost commented on GitHub (Jan 3, 2022): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, 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/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
Author
Owner

@JuliusDegesys commented on GitHub (Jan 3, 2022):

https://aka.ms/AAfdpbh

@JuliusDegesys commented on GitHub (Jan 3, 2022): https://aka.ms/AAfdpbh
Author
Owner

@zadjii-msft commented on GitHub (Aug 15, 2022):

Hey there was a whole bunch of crash-on-exit fixes that we did in the last few months. Are you still seeing this on 1.15/? If so, an fresh Feedback hub dump might be needed (considering the volume of teardown code that changed)

@zadjii-msft commented on GitHub (Aug 15, 2022): Hey there was a whole bunch of crash-on-exit fixes that we did in the last few months. Are you still seeing this on 1.15/? If so, an fresh Feedback hub dump might be needed (considering the volume of teardown code that changed)
Author
Owner

@ghost commented on GitHub (Aug 19, 2022):

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 (Aug 19, 2022): 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#16312