-
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 will not open #17255
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Closed similar issues:
|
If you send a feedback via the Feedback Hub, can you please share a link here?
It's definitely not my right to meddle, but if you're afraid of losing that data (= can't restore it some other way), and don't have a backup of that data right now, it's already as critical as it gets. As you're probably aware, even when your PC is completely switched off, any file on your SSD/HDD may randomly corrupt itself, even if the likelihood is small. The likelihood gets way larger if it's switched on. Please consider making backups of data you cannot restore some other way soon. |
Feedback Hub with recording && CrashDump files shared: https://aka.ms/AAqd98q Self-hosted .dmp files from I can back up my data, it's just time consuming. It's also annoying to have to reinstall Windows over this issue, I just hoped that there would be an easier manual solution. Even if not all that easy... I will start backing up my data, I suppose. Please keep me posted on your findings and suggestions! Thanks for the reply, and let me know if you need anything else. |
Regarding your system, I have bad news. All of your dumps show:
(That's probably
Regarding However, this is only a guess. It's possible that the application is crashing for you and others for a different reason. It's difficult to say what it could be, especially since the Feedback Hub item doesn't seem to be processed yet. If you want to investigate this yourself, you can install WinDbg from the app store (https://www.microsoft.com/store/productId/9PGJGD53TN86), click "Launch app package" and launch Windows Terminal Preview. You won't have source code access inside WinDbg unfortunately, but you at least get the stack traces of anything that's happening. |
@lhecker I appreciate your experienced insight and willingness to go out of your way to help. Well explained, and suggested. I will continue to dig a bit and see what I find.. I suppose a back up + refresh / restore point is in order, ultimately. I honestly might just try win11. If they're throwing different errors based on version, I'll try other versions also. And not sure what I'd be looking at with stack traces, but I'll do some googling and also let you know what transpires, if anything else. No way to simply try and replace that ucrtbase.dll, eh? I don't want to download one randomly online for security reasons.. and from what I see I can't find Microsoft offering one. Please don't close the issue yet, if you don't mind. I hope this reference helps your dev team and also anyone in the future. Thanks again! |
Just to be clear, I'm not 100% sure if the warning is correct. It's just not something I usually see in my own Windows 10 dumps. I can give you my Edit: Oh, I almost forgot to mention: Before you replace it, could you check if their checksums match? If you don't know how, launch PowerShell and run: Get-FileHash SHA1 <path> If they don't match, could you upload your version as a .zip here? We'd be interested to see what the differences are. (You should also keep a copy yourself of course, just to be sure.)
For what it's worth, I'm not 100% sure it's because of just your system. We do have an overall increase in |
@lhecker Hey, Sorry it's been over a week. I've been meaning to reply, finally got some time to sit down and analyze some things. The SHA-1 of the .dll file you provided
However, I am failing to see how this is relevant - or where the .dmp files got that .dll path & file, unless it creates a new version of the .dll in that path upon hitting the error or upon running WinDbg. I believe that is the case, because that .dll shows a file creation date of May 15, 2024 which is when I ran the WinDbg again. Point being, it does not match the SHA-1 checksum on the .dll in the notes on the error in the Event Viewer logs wherein it shows
Again, as per relevance, I'm going through these other details in this response because After reading your last response, on May 15th I took it upon myself to install and evaluate multiple different versions of WindowsTerminal.. from 1.21 back to about 1.15-ish. I think I skipped 1.16, maybe 1.17... Same issue - runs first time when launched from install - or from Windows Store if the version matches to one on there - otherwise crashes when trying to open from file, taskbar search, or "run" (WindowsKey+R). I also downloaded WinDbg as you suggested, and also ran it on all the .dmp files that I sent you from the previous session. STRANGELY -- I am not getting the same
CrashDumps_from_May13-2024.zip -- All crash dumps from May 13th for Windows Terminal versions 1.19 & 1.21 WinDbg_log_WindowsTerminal_dmp_files_from_May13-2024.txt -- WinDbg logs from the May 13th .dmp files I ran. (I only did the recent most 5 .dmp files, figuring they'd all be similar.). May 15th 2024 retry of different versions:v1.19.11213:
v1.20.11271:
v1.21.11271:
v1.18.10301:
v1.15.2524:
^^ ALL CrashDumps_from_May15-2024.zip - All .dmp files from May 15th, 2024 WinDbg_log_WindowsTerminal_dmp_files_from_May15-2024.txt - WinDbg logs for .dmp files from May 15th, 2024 May 22nd, 2024 - retry of v1.19 from MS Store:v1.19.11213:
^^ CrashDump_from_May22-2024.zip - .dmp file from May 22nd, 2024 WinDbg_log_WindowsTerminal_dmp_files_from_May22-2024.txt - WinDbg log file for the .dmp from May 22nd, 2024 Okay, so as you can see -- I am getting completely different FAILURE_ID_HASH values on different dates, for different versions (save for the one WinUI/XML error which is an outlier) -- but they all have the same ERROR_CODE. As I alluded to earlier in the post, I am a cybersecurity hobbyist. I have to wonder if I have a poisoned DLL file in ucrtbase.dll, especially after seeing that error message I ran Norton on both ucrtbase.dll files that I gave you the SHA-1 checksums for, no red flags. However, I know that does not mean anything. Perhaps it's severe speculation, but I have to wonder, because it is very possible. Even though, I do not even play with malware on purpose, or at all - for that matter. I do CTF events, etc, and some minor research on web apps and systems. Nothing ever outside of a virtual machine. Anyway, tell me what you think. If nothing else, then I am going to backup my data this weekend and do the windows refresh. I actually just built a brand new PC with Win 11 Pro so in the end, this won't matter much for me. Regardless, I would still like to get to the bottom of it, even if it only helps you guys out in any form. Here is the ucrtbase.dll from Here is the ucrtbase.dll from The WinDbg logs state Thanks again, let me know if you need anything else. PS: Perhaps you'll also find some different, helpful info in the stack trace / STACK_TEXT of some of these. |
Worth noting that I found yesterday.. searching and opening "CMD" "PowerShell" or "WSL" in Windows search/start button opens the respective tool right in Windows terminal v1.19 without an issue. Whereas trying to open "wt" or "wt.exe" - whether from search, run, or the direct file in its folder - causes this issue described in this thread. Very strange. I don't know if there is more information I can offer you that would help you understand more of what is occurring here, but if there is then please let me know. I did some searching around, and installed Process Explorer from SysInternals. Just starting to dig around now, not sure what I'm looking for but it shows ucrtbase.dll & Microsoft.UI.Xaml.dll running just fine in the above-mentioned instances. I don't want to give you guys more issues to worry about than you need, if this whole task seems null to you then that's fine. I would genuinely like to think that it's worth solving a potential issue that many others may encounter. If you think it's just a one-off occurrence due to my PC or Windows having an error, I can live with backing up data/reinstalling Windows. As mentioned, I built a new PC last week so that would be the route I end up going anyway. Just wanted to share that new piece of info at the top. Let me know if I can get you anything else. Thanks again! |
Hello, I came across this case and I would like to add my observations about this problem just to help you guys understand more deeply what could be the cause of this issue (at the risk of repeating already known information). We have several clients who are experiencing the same issue : when trying to launch an application through Windows Terminal from our application, it crashes and only informs us about the fact that the process has been terminated. What we know
Here are the arguments passed to the ProcessStartInfo C# object : Thanks in advance ! |
Hey there, Came back this morning to make the dump file and found out it is working now... Still with the QA team trying to reproduce the issue. EDITOne of our QA team member was still able to reproduce the issue (OS BUILD = 22621.3593, Windows Terminal Version = 1.20.11381.0). Weirdly I still am not able to remake the crash happen... Here is the crash report file from last week : Here is also the process dump file from this QA Team member : |
Okay well, that dump was a RemoteDesktopManger dump, so that wasn't helpful, but maybe the
weird. |
bucket |
which is also bucket |
All, hope you had a nice weekend. I see some activity recently on this so I wanted to say if you need anything from my environment please feel free to ask, I'll give you anything you require just tell me what to do. I doubt you need my interference but I wanted to say that ^^ and: The same issue persists, except now it's no longer win terminal 1.19.x from Microsoft Store installed, it is v1.20.11381.0. I think back when this started, 1.19.x was in the store, and I tried 1.21.x preview from the store, and then 1.15 - 1.21.x from Github Releases. So now it is in fact 1.20.11381.0. Same issue persists, installed from MS Store, cannot open with "wt" in taskbar search, can not open by going into the dir and double clicking wt.exe. It only opens form the store "Open" (button shows after it's installed, of course) and I found that after the 1.20.x install it windows terminal opens by default if i just run "cmd" or "wsl" etc, with the respective terminal requested. |
Update: we have identified the issue on our side as being an exception thrown during JSON parsing of the settings. With WT 1.18, our generated state.json contained "dismissedMessages" : [ "deprecated" ], a setting which is only handled by WT 1.20+. Upgrading to WT 1.20 fixes it for us, but anything that looks like this crash for others is likely caused by a similar JSON parsing exception being thrown. Here's what the call stack looks like for us: I don't know if there's a better way to handle cases where the JSON parsing throws an exception, other than crashing silently. |
@awakecoding are you part of the Microsoft team? I'm on version 1.20.11381.0 which is the newest in the Microsoft Store and the issue persists for me. I also tried the beta of 1.21.xxxx at the very beginning of when this started and same thing. If there is any other info / data / files / screenshots I can provide to shed some light if it's a result of my environment, please direct me at what's needed and I'll gladly provide it. |
Edit: Ah right, I forgot that nowadays we don't update the OS version number anymore. -.- |
@lhecker these are the two updates available. It appears the optional quality update offers a more current OS build? or at least that's what the Microsoft link says. This link says something about OS build 19045.4717 so I assume this update upgrades the OS build when installed? If that's the case, then I have Interesting fact that the And 2) I went through this in the start of this thread, there are numerous ucrtbase.dll files in my system - not one. It's in the subdirectory for whichever program utilizes it. So, it would seem when one of those programs are installed, it copies or creates a ucrtbase.dll which is a version relevant to the OS build at the time of installation? Because the ucrtbase.dll in Windows Terminal subdir is a different file hash than others found in the system, thus should be different versions. I will try to actually delete the existing ucrtbase.dll, install the newer outstanding Cumulative Update so it's there to hopefully propagate the newer ucrtbase.dll when I then install the newer Windows Terminal after. In theory, that should upgrade the ucrtbase.dll. This very well may be the root of the whole issue, so let's see. Thanks. Furthermore are you part of the Microsoft Terminal Dev Team? It didn't appear so, and I haven't responded sooner because I don't want to flood this chain with a bunch of irrelevant info. But I am wondering when they are going to respond / ask me for more info or data, or what further findings or suggestions they've developed? 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441) OPTIONAL: |
Windows Terminal version
1.19.11213.0 & 1.21.1272.0
Windows build number
Win10 22H2 build 19045.4355
Other Software
N/A
Steps to reproduce
Windows Terminal will not open now, as of a couple weeks ago.
It will not run by opening wt.exe, or WIndowsTerminal.exe. Regularly, or as administrator. In it's default folder, or by typing wt.exe in "run:"
I've tried rebooting, I've ensured the system is fully updated, I've tried Settings>Apps>Windows Terminal>Advanced Options> Terminate/Repair/Reset.
It started with v 1.19.11213.0 which I've had installed from Windows Store for a while now. It was working fine up until a couple weeks ago. I don't know what's changed other than maybe a system update? I've also tried uninstalling it then reinstalling it - same issue. Then, I uninstalled it and installed v 1.21.1272.0 - same exact issue. It runs at first launch after install, then won't open after.
It will only open from Windows Store > Windows Terminal > "Open" -- but without any of my settings.
I've looked online (and yes, I've looked in Github Open & Closed issues) and I've tried just about everything except the generic MS Agent response to:
I am not going to reinstall windows and have to backup 1tb of data or risk it being lost over this.
There needs to be a different way?
I'm at the point of deleting anything "WindowsTerminal" in Windows Registry but I have not done so unless you tell me to, or another option.
Edit:
Per the github-actions bot, before posting this I also did find #14133 which refers to #14104 - which recommends to simply install "Windows Media Feature Pack" -- however, that is for Windows N versions. So I did not do it.
They also reference #14110 & #14124 - which appears to be a different error, but it did prompt me to look at Event Viewer:
Regular opening attempt of wt.exe as non-administrator:
Attempt at opening wt.exe with "Run ad Administrator:
Appears to be a different faulting DLL than those issues referenced.
Per the feedback in all of those issues - I will also send feedback via the Feedback Hub, however I really would appreciate some insight or a fix here asap because Windows Terminal is meta, and I need to use it!!!
Thanks!
Expected Behavior
The program to run regularly.
Actual Behavior
The program will not open other than via Windows Store > Open, with stock settings.
The text was updated successfully, but these errors were encountered: