-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Terminal crashing when invoking a Console request from .NET #16204
Comments
Alas, that Report Id didn't show up on the backend. We might need a Feedback Hub dump or a post-mortem dump to definitively ID this. Can you try following these steps to get us a dump/? I'm guessing this is MSFT:44310564 which is #16199, but we don't really have a repro for that, just crash dumps. |
I've sent an email with the crash dump per the instructions. Far as reproduction unfortunately where EcoServer crashes vs when Windows Terminal crashes are not related so trying to pinpoint it is rather difficult. Only known constant is it doesn't fail in the same spot every time and running as Administrator seems to sometimes help. |
Yep this is definitely /dup #16199. Thanks! |
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! |
Windows Terminal version
1.18.2310.9002
Windows build number
10.0.22621.0
Other Software
Eco (EcoServer.exe)
Steps to reproduce
Run the application without Administrator privileges.
Expected Behavior
It launches as expected.
Actual Behavior
Windows Terminal crashes resulting in a closed pipe error within .NET
This also seems to happen with the legacy applications such as cmd.exe. The issue is not consistent. However, once it starts it does not go away. We have had a few users report uninstalling Windows update KB5030649 resolves their issues.
Attempting to investigate inside the Event Viewer turns up this error
The text was updated successfully, but these errors were encountered: