Windows Terminal not running #2829

@jthvedt commented on GitHub (Jul 18, 2019):

Have you tried deleting or renaming your profiles.json file? I was having that same problem. The applications event log showed "Exception code: 0xc0000409" and referenced ucrtbase.dll. I may have had a corrupt settings file; after I deleted profiles.json, Windows Terminal would run. It recreated a new profiles.json file. Of course, I lost a few trivial settings I had changed. If you've made changes, you probably want to make a backup to use for reference.

@jthvedt commented on GitHub (Jul 18, 2019): Have you tried deleting or renaming your profiles.json file? I was having that same problem. The applications event log showed "Exception code: 0xc0000409" and referenced ucrtbase.dll. I may have had a corrupt settings file; after I deleted profiles.json, Windows Terminal would run. It recreated a new profiles.json file. Of course, I lost a few trivial settings I had changed. If you've made changes, you probably want to make a backup to use for reference.

claunia commented

@gwy15 commented on GitHub (Jul 18, 2019):

@jthvedt The thing is Windows Terminal haven't run even once on this PC so there's no profiles.json created. I used Everything to search for files named profiles.json or profile.json on this PC and none was found. So I guess it's not a corrupted config file.

BTW Can you tell me how do I access the application event log? Thanks a lot.

@gwy15 commented on GitHub (Jul 18, 2019): @jthvedt The thing is Windows Terminal haven't run even once on this PC so there's no `profiles.json` created. I used Everything to search for files named `profiles.json` or `profile.json` on this PC and none was found. So I guess it's not a corrupted config file. BTW Can you tell me how do I access the application event log? Thanks a lot.

claunia commented

@thegreatco commented on GitHub (Jul 18, 2019):

I'm having a similar issue albeit with a slightly different Windows version.

Edition: WIndows 10 Pro
Version: 1903
OS Build 18362.175

I've tried removing the application using Add/Remove Programs, it has never successfully run on this host.

From Application Event Log

Faulting application name: WindowsTerminal.exe, version: 1.0.1907.2001, time stamp: 0x5d1bd2d0
Faulting module name: ucrtbase.dll, version: 10.0.18362.1, time stamp: 0x5cbddb81
Exception code: 0xc0000409
Fault offset: 0x000000000006d3be
Faulting process id: 0x539c
Faulting application start time: 0x01d53d715cdee907
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: c16952b6-1fb4-4b4b-9511-e6332b0f86fe
Faulting package full name: Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

@thegreatco commented on GitHub (Jul 18, 2019): I'm having a similar issue albeit with a slightly different Windows version. Edition: WIndows 10 Pro Version: 1903 OS Build 18362.175 I've tried removing the application using Add/Remove Programs, it has never successfully run on this host. From Application Event Log ``` Faulting application name: WindowsTerminal.exe, version: 1.0.1907.2001, time stamp: 0x5d1bd2d0 Faulting module name: ucrtbase.dll, version: 10.0.18362.1, time stamp: 0x5cbddb81 Exception code: 0xc0000409 Fault offset: 0x000000000006d3be Faulting process id: 0x539c Faulting application start time: 0x01d53d715cdee907 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: c16952b6-1fb4-4b4b-9511-e6332b0f86fe Faulting package full name: Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ```

claunia commented

@jthvedt commented on GitHub (Jul 18, 2019):

BTW Can you tell me how do I access the application event log? Thanks a lot.

Easiest way is type Win-S and search for "Event Viewer". In the left panel, expand the "Windows Logs" section and choose "Application". It sorts by date, so it'll be easiest to find the error if you try to run Window Terminal immediately before you open the Event Viewer.

@jthvedt commented on GitHub (Jul 18, 2019): > BTW Can you tell me how do I access the application event log? Thanks a lot. Easiest way is type Win-S and search for "Event Viewer". In the left panel, expand the "Windows Logs" section and choose "Application". It sorts by date, so it'll be easiest to find the error if you try to run Window Terminal immediately before you open the Event Viewer.

claunia commented

@jthvedt commented on GitHub (Jul 18, 2019):

@thegreatco - That's exactly the error I was getting in my event log. Removing the app did not remove the profiles.json file for me; I had to delete that file manually.

@jthvedt commented on GitHub (Jul 18, 2019): @thegreatco - That's exactly the error I was getting in my event log. Removing the app did _not_ remove the profiles.json file for me; I had to delete that file manually.

claunia commented

@gwy15 commented on GitHub (Jul 19, 2019):

I had a look at the logs and I have the same report as @thegreatco .

@gwy15 commented on GitHub (Jul 19, 2019): I had a look at the logs and I have the same report as @thegreatco .

claunia commented

@thegreatco commented on GitHub (Jul 19, 2019):

I am now upgraded to OS Build 18362.10005 and it is still failing to start. This is a freshly installed copy after the update to 10005.

Faulting application name: WindowsTerminal.exe, version: 1.0.1907.2001, time stamp: 0x5d1bd2d0
Faulting module name: ucrtbase.dll, version: 10.0.18362.1, time stamp: 0x5cbddb81
Exception code: 0xc0000409
Fault offset: 0x000000000006d3be
Faulting process id: 0x28c
Faulting application start time: 0x01d53e5d96827e9b
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 65231be6-67f6-4d16-8a0a-705ff3795fd7
Faulting package full name: Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Fault bucket 1713649042173444167, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.0.1907.2001
P4: 5d1bd2d0
P5: ucrtbase.dll
P6: 10.0.18362.1
P7: 5cbddb81
P8: 000000000006d3be
P9: c0000409
P10: 0000000000000007

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58C4.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5971.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5992.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59A3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59D3.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_e2e3fa6c896198f1ea9ed1ce1e1cb6e78fc13_07ada22b_6c2d78f5-1793-49a2-ba93-def3371d502c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 65231be6-67f6-4d16-8a0a-705ff3795fd7
Report Status: 268435456
Hashed bucket: 0170e7cb87c40f84a7c81ab97c6fc047
Cab Guid: 0

I have a wer file if it would be helpful.

@thegreatco commented on GitHub (Jul 19, 2019): I am now upgraded to OS Build 18362.10005 and it is still failing to start. This is a freshly installed copy after the update to 10005. ``` Faulting application name: WindowsTerminal.exe, version: 1.0.1907.2001, time stamp: 0x5d1bd2d0 Faulting module name: ucrtbase.dll, version: 10.0.18362.1, time stamp: 0x5cbddb81 Exception code: 0xc0000409 Fault offset: 0x000000000006d3be Faulting process id: 0x28c Faulting application start time: 0x01d53e5d96827e9b Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: 65231be6-67f6-4d16-8a0a-705ff3795fd7 Faulting package full name: Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` ``` Fault bucket 1713649042173444167, type 5 Event Name: MoBEX Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe P2: praid:App P3: 1.0.1907.2001 P4: 5d1bd2d0 P5: ucrtbase.dll P6: 10.0.18362.1 P7: 5cbddb81 P8: 000000000006d3be P9: c0000409 P10: 0000000000000007 Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58C4.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5971.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5992.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59A3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59D3.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_e2e3fa6c896198f1ea9ed1ce1e1cb6e78fc13_07ada22b_6c2d78f5-1793-49a2-ba93-def3371d502c Analysis symbol: Rechecking for solution: 0 Report Id: 65231be6-67f6-4d16-8a0a-705ff3795fd7 Report Status: 268435456 Hashed bucket: 0170e7cb87c40f84a7c81ab97c6fc047 Cab Guid: 0 ```` I have a `wer` file if it would be helpful.

claunia commented

@DHowett-MSFT commented on GitHub (Jul 20, 2019):

This seems similar to #1364. @thegreatco, is there a chance your "default profile" points to something that doesn't exist on this computer?

@DHowett-MSFT commented on GitHub (Jul 20, 2019): This seems similar to #1364. @thegreatco, is there a chance your "default profile" points to something that doesn't exist on this computer?

claunia commented

@gwy15 commented on GitHub (Jul 20, 2019):

So it turns out Windows automatically syncs the profiles.json between different computers under your MS account. And it seems that if the synced profiles.json includes something that is not suitable for the host, e.g., a font not installed, the Windows Terminal crashes without giving any warnings or logs.

For my case, I manually entered the directory
%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState and deleted the synced profiles.json from my laptop, which does exist but for some reason was not found in everything. The file included a font not installed on the crashing host. Then I re-ran the Windows Terminal and a default profiles.json was generated with which Windows Teminal worked fine.

@gwy15 commented on GitHub (Jul 20, 2019): So it turns out Windows automatically syncs the `profiles.json` between different computers under your MS account. And it seems that if the synced `profiles.json` includes something that is not suitable for the host, e.g., a font not installed, the Windows Terminal crashes without giving any warnings or logs. For my case, I manually entered the directory `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState` and deleted the synced `profiles.json` from my laptop, which does exist but for some reason was not found in everything. The file included a font not installed on the crashing host. Then I re-ran the Windows Terminal and a default profiles.json was generated with which Windows Teminal worked fine.

claunia commented

@fedelaport commented on GitHub (Jul 21, 2019):

I have two laptops. Installing from Windows Store works nice on the first laptop. Then, installing on the second laptop syncs the profiles.json. The file points to things that I don't have on the second laptop. WT crashes.

Update: A missing font (Ubuntu Mono) was the issue.

@fedelaport commented on GitHub (Jul 21, 2019): I have two laptops. Installing from Windows Store works nice on the first laptop. Then, installing on the second laptop syncs the `profiles.json`. The file points to things that I don't have on the second laptop. WT crashes. **Update:** A missing font (Ubuntu Mono) was the issue.

claunia commented

@erkattak commented on GitHub (Jul 22, 2019):

I have two machines as well. On one machine, I have Ubuntu. The other has Ubuntu-18.04. If I use WSL as the default profile, it will only run on one machine because:

"commandline": "wsl.exe -d Ubuntu-18.04",

is not the same as

"commandline": "wsl.exe -d Ubuntu",

@erkattak commented on GitHub (Jul 22, 2019): I have two machines as well. On one machine, I have Ubuntu. The other has Ubuntu-18.04. If I use WSL as the default profile, it will only run on one machine because: ``` "commandline": "wsl.exe -d Ubuntu-18.04", ``` is not the same as ``` "commandline": "wsl.exe -d Ubuntu", ```

claunia commented

@thegreatco commented on GitHub (Jul 24, 2019):

I was missing a font. I deleted the profile.json, and it started up just fine. Then i slowly merged the old and new profile.json until something broke. Installed the font, problem solved.

@thegreatco commented on GitHub (Jul 24, 2019): I was missing a font. I deleted the `profile.json`, and it started up just fine. Then i slowly merged the old and new `profile.json` until something broke. Installed the font, problem solved.

claunia commented

@TheAndyMac commented on GitHub (Aug 6, 2019):

Thank you! This fixed my install as well... had the same problem for weeks and only just found this solution - I had assumed that an Uninstall/Reinstall and/or a Reset of the app through the Windows App Settings would sort it out - maybe one easy fix to cope with profile "corruptions" would be to make sure the Windows App Settings "Reset" feature deletes the profile file?

@TheAndyMac commented on GitHub (Aug 6, 2019): Thank you! This fixed my install as well... had the same problem for weeks and only just found this solution - I had assumed that an Uninstall/Reinstall and/or a Reset of the app through the Windows App Settings would sort it out - maybe one easy fix to cope with profile "corruptions" would be to make sure the Windows App Settings "Reset" feature deletes the profile file?

claunia commented

@gwy15 commented on GitHub (Aug 10, 2019):

For WT 0.3.2171.0, it seems that for a profiles.json with invalid font Windows Terminal will now fallback to a default font (seems like consolas to me) instead of crashing. For now I don't see any necessary to keep this issue open and I'm closing it.

But still, no warnings are raised to remind users to fix their profiles.json.

@gwy15 commented on GitHub (Aug 10, 2019): For WT 0.3.2171.0, it seems that for a `profiles.json` with invalid font Windows Terminal will now fallback to a default font (seems like consolas to me) instead of crashing. For now I don't see any necessary to keep this issue open and I'm closing it. But still, no warnings are raised to remind users to fix their `profiles.json`.

claunia commented

@EricBuist commented on GitHub (May 27, 2021):

Hi,
Is there a way to prevent synching this profile.json, which looks to me like the worst idea ever. The file depends on what is installed on the host computer so it should not be synched, or things in there that don't work on the host computer should trigger warnings at worst, not crash the terminal without any form of clue. I cannot spend my time deleting that file (and finding it) and then trying to figure out again the tweaks I did in there to have a block cursor, disable the annoying beep, add a tab pointing at my SSH server, etc. It was working yesterday and all of a sudden, I cannot start the Windows Terminal. That problem WILL occur again, again and again, if I just recreate that profile.json file. Having to remove profile.json (and search for it, it is really non-obvious to find), is not a fix.

@EricBuist commented on GitHub (May 27, 2021): Hi, Is there a way to prevent synching this profile.json, which looks to me like the worst idea ever. The file depends on what is installed on the host computer so it should not be synched, or things in there that don't work on the host computer should trigger warnings at worst, not crash the terminal without any form of clue. I cannot spend my time deleting that file (and finding it) and then trying to figure out again the tweaks I did in there to have a block cursor, disable the annoying beep, add a tab pointing at my SSH server, etc. It was working yesterday and all of a sudden, I cannot start the Windows Terminal. That problem WILL occur again, again and again, if I just recreate that profile.json file. Having to remove profile.json (and search for it, it is really non-obvious to find), is not a fix.

claunia commented

@zadjii-msft commented on GitHub (May 27, 2021):

@EricBuist We stopped syncing profiles.json like, nearly two years ago. We also don't migrate settings from the old roamed location to settings.json anymore.

If you're experiencing a new crash on launch, then it's probably some totally new scenario. Could you follow up in a new thread, so we can track your issue specifically? Thanks!

@zadjii-msft commented on GitHub (May 27, 2021): @EricBuist We stopped syncing `profiles.json` like, [nearly two years ago](https://github.com/microsoft/terminal/pull/2298). We also [don't migrate settings from the old roamed location](https://github.com/microsoft/terminal/pull/5199) to `settings.json` anymore. If you're experiencing a new crash on launch, then it's probably some totally new scenario. Could you follow up in a new thread, so we can track your issue specifically? Thanks!

claunia commented

@gemini88mill commented on GitHub (May 28, 2021):

Hey All ran into the exact same issue and realized that I didn't even have a profiles.json. I ended up going into "Add or Remove Programs" and repairing Windows Terminal, fixed the problem for me.

@gemini88mill commented on GitHub (May 28, 2021): Hey All ran into the exact same issue and realized that I didn't even have a profiles.json. I ended up going into "Add or Remove Programs" and repairing Windows Terminal, fixed the problem for me.

claunia commented

@alibenmessaoud commented on GitHub (May 29, 2021):

I am experiencing the same issue and WT stills always crashing even after restart, reinstall, and a new Windows update.

@alibenmessaoud commented on GitHub (May 29, 2021): I am experiencing the same issue and WT stills always crashing even after restart, reinstall, and a new Windows update.

claunia commented

@etalian commented on GitHub (May 29, 2021):

Same here, fixed by "repairing". Even though this is the top search result now, I believe we are actually seeing #10211.

@etalian commented on GitHub (May 29, 2021): Same here, fixed by "repairing". Even though this is the top search result now, I believe we are actually seeing #10211.

claunia commented

@DLX23 commented on GitHub (May 30, 2021):

Now, same Problem here. "Repairing" and "reset" dont help.

Name der fehlerhaften Anwendung: WindowsTerminal.exe, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2e94 Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.19041.789, Zeitstempel: 0x2bd748bf Ausnahmecode: 0xc0000409 Fehleroffset: 0x000000000007286e ID des fehlerhaften Prozesses: 0x9858 Startzeit der fehlerhaften Anwendung: 0x01d7552ffe6e2922 Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\ucrtbase.dll Berichtskennung: c1016986-f7c6-4cde-8f0d-669bdea6c357 Vollständiger Name des fehlerhaften Pakets: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Complete uninstall and reinstall helped

@DLX23 commented on GitHub (May 30, 2021): Now, same Problem here. "Repairing" and "reset" dont help. `Name der fehlerhaften Anwendung: WindowsTerminal.exe, Version: 1.8.2105.24004, Zeitstempel: 0x60ac2e94 Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.19041.789, Zeitstempel: 0x2bd748bf Ausnahmecode: 0xc0000409 Fehleroffset: 0x000000000007286e ID des fehlerhaften Prozesses: 0x9858 Startzeit der fehlerhaften Anwendung: 0x01d7552ffe6e2922 Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\ucrtbase.dll Berichtskennung: c1016986-f7c6-4cde-8f0d-669bdea6c357 Vollständiger Name des fehlerhaften Pakets: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App` Complete uninstall and reinstall helped

claunia commented

@annahri commented on GitHub (May 31, 2021):

Fixed this by repairing it via Add or remove programs.

@annahri commented on GitHub (May 31, 2021): Fixed this by repairing it via Add or remove programs.

claunia commented