-
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
Terminal exited without user interaction #10277
Comments
The not-starting-part seems to be related to (using repair did not help me, still unable to launch): #10211 |
Can confirm the same, able to replicate it |
The same for me happened at both of my machines. Restart didn't helped |
Well the registry lookup sure is weird. Best way to get to the bottom of this is with a Feedback Hub trace: /feedback |
Created a crash report: https://aka.ms/AAcslt1 |
I created a report in the Hub, hopefully it has everything that could help: |
Thanks! This is /dup #10211 |
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 (or Windows build number)
WT 1.8.1444.0, Win 10 19042.985
Other Software
No response
Steps to reproduce
Terminal was left running a tool in Powershell. Returning to the computer showed Terminal closed. Trying to reopen it, the process exits after a few seconds without opening a window.
From around the time that Terminal exited, this is found in event log (unlocalized from German):
The access history in hive "\??\C:\Users\Username\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\Settings\settings.dat" was cleared updating 3 keys and creating 1 modified pages.
Expected Behavior
Terminal should not exit unless it is told to.
Actual Behavior
Terminal went bye-bye without telling anyone.
The text was updated successfully, but these errors were encountered: