Windows terminal attempts to start but then crashes without showing main window. #11532

claunia commented

@DHowett commented on GitHub (Nov 22, 2020):

Thanks. Unfortunately, I can't get the dumps from secure@microsoft.com. Would you mind sharing the same content with me? My Microsoft e-mail address is on my profile.

Thank you. 😄

@DHowett commented on GitHub (Nov 22, 2020): Thanks. Unfortunately, I can't get the dumps from secure@microsoft.com. Would you mind sharing the same content with me? My Microsoft e-mail address is on my profile. Thank you. :smile:

claunia commented

@PreetSangha commented on GitHub (Nov 22, 2020):

Hi Dustin, I cannot get the dump. I can only get the report file. The dumps
just don't get created or get deleted. I'll send it to you any way.

Have just sent it to you.

@PreetSangha commented on GitHub (Nov 22, 2020): Hi Dustin, I cannot get the dump. I can only get the report file. The dumps just don't get created or get deleted. I'll send it to you any way. Have just sent it to you.

claunia commented

@DHowett commented on GitHub (Nov 22, 2020):

Thanks! Would you mind sharing your settings file? It's in %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json

It should be fine to paste in here or in a gist

I managed to get a dump from your crash report (thank you for leaving crash reporting enabled!) that implicated settings handling, but it's been stripped of all fun and useful information 😄

@DHowett commented on GitHub (Nov 22, 2020): Thanks! Would you mind sharing your settings file? It's in `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json` It should be fine to paste in here or in a [gist](https://gist.github.com) I managed to get a dump from your crash report (thank you for leaving crash reporting enabled!) that implicated settings handling, but it's been stripped of all fun and useful information :smile:

claunia commented

@PreetSangha commented on GitHub (Nov 22, 2020):

Here you do @DHowett

// This file was initially generated by Windows Terminal 1.4.3243.0
// It should still be usable in newer versions, but newer versions might have additional
// settings, help text, or changes that you will not see unless you clear this file
// and let us generate a new one for you.

// To view the default settings, hold "alt" while clicking on the "Settings" button.
// For documentation on these settings, see: https://aka.ms/terminal-documentation
{
    "$schema": "https://aka.ms/terminal-profiles-schema",

    "defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",

    // You can add more global application settings here.
    // To learn more about global settings, visit https://aka.ms/terminal-global-settings

    // If enabled, selections are automatically copied to your clipboard.
    "copyOnSelect": false,

    // If enabled, formatted data is also copied to your clipboard
    "copyFormatting": false,

    // A profile specifies a command to execute paired with information about how it should look and feel.
    // Each one of them will appear in the 'New Tab' dropdown,
    //   and can be invoked from the commandline with `wt.exe -p xxx`
    // To learn more about profiles, visit https://aka.ms/terminal-profile-settings
    "profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles.
        },
        "list":
        [
            {
                // Make changes here to the powershell.exe profile.
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name": "Windows PowerShell",
                "commandline": "powershell.exe",
                "hidden": false
            },
            {
                // Make changes here to the cmd.exe profile.
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "name": "Command Prompt",
                "commandline": "cmd.exe",
                "hidden": false
            },
            {
                "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
                "hidden": false,
                "name": "Ubuntu-20.04",
                "source": "Windows.Terminal.Wsl"
            },
            {
                "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
                "hidden": false,
                "name": "Azure Cloud Shell",
                "source": "Windows.Terminal.Azure"
            }
        ]
    },

    // Add custom color schemes to this array.
    // To learn more about color schemes, visit https://aka.ms/terminal-color-schemes
    "schemes": [],

    // Add custom actions and keybindings to this array.
    // To unbind a key combination from your defaults.json, set the command to "unbound".
    // To learn more about actions and keybindings, visit https://aka.ms/terminal-keybindings
    "actions":
    [
        // Copy and paste are bound to Ctrl+Shift+C and Ctrl+Shift+V in your defaults.json.
        // These two lines additionally bind them to Ctrl+C and Ctrl+V.
        // To learn more about selection, visit https://aka.ms/terminal-selection
        { "command": {"action": "copy", "singleLine": false }, "keys": "ctrl+c" },
        { "command": "paste", "keys": "ctrl+v" },

        // Press Ctrl+Shift+F to open the search box
        { "command": "find", "keys": "ctrl+shift+f" },

        // Press Alt+Shift+D to open a new pane.
        // - "split": "auto" makes this pane open in the direction that provides the most surface area.
        // - "splitMode": "duplicate" makes the new pane use the focused pane's profile.
        // To learn more about panes, visit https://aka.ms/terminal-panes
        { "command": { "action": "splitPane", "split": "auto", "splitMode": "duplicate" }, "keys": "alt+shift+d" }
    ]
}

@PreetSangha commented on GitHub (Nov 22, 2020): Here you do @DHowett ``` // This file was initially generated by Windows Terminal 1.4.3243.0 // It should still be usable in newer versions, but newer versions might have additional // settings, help text, or changes that you will not see unless you clear this file // and let us generate a new one for you. // To view the default settings, hold "alt" while clicking on the "Settings" button. // For documentation on these settings, see: https://aka.ms/terminal-documentation { "$schema": "https://aka.ms/terminal-profiles-schema", "defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", // You can add more global application settings here. // To learn more about global settings, visit https://aka.ms/terminal-global-settings // If enabled, selections are automatically copied to your clipboard. "copyOnSelect": false, // If enabled, formatted data is also copied to your clipboard "copyFormatting": false, // A profile specifies a command to execute paired with information about how it should look and feel. // Each one of them will appear in the 'New Tab' dropdown, // and can be invoked from the commandline with `wt.exe -p xxx` // To learn more about profiles, visit https://aka.ms/terminal-profile-settings "profiles": { "defaults": { // Put settings here that you want to apply to all profiles. }, "list": [ { // Make changes here to the powershell.exe profile. "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "name": "Windows PowerShell", "commandline": "powershell.exe", "hidden": false }, { // Make changes here to the cmd.exe profile. "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "name": "Command Prompt", "commandline": "cmd.exe", "hidden": false }, { "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}", "hidden": false, "name": "Ubuntu-20.04", "source": "Windows.Terminal.Wsl" }, { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "hidden": false, "name": "Azure Cloud Shell", "source": "Windows.Terminal.Azure" } ] }, // Add custom color schemes to this array. // To learn more about color schemes, visit https://aka.ms/terminal-color-schemes "schemes": [], // Add custom actions and keybindings to this array. // To unbind a key combination from your defaults.json, set the command to "unbound". // To learn more about actions and keybindings, visit https://aka.ms/terminal-keybindings "actions": [ // Copy and paste are bound to Ctrl+Shift+C and Ctrl+Shift+V in your defaults.json. // These two lines additionally bind them to Ctrl+C and Ctrl+V. // To learn more about selection, visit https://aka.ms/terminal-selection { "command": {"action": "copy", "singleLine": false }, "keys": "ctrl+c" }, { "command": "paste", "keys": "ctrl+v" }, // Press Ctrl+Shift+F to open the search box { "command": "find", "keys": "ctrl+shift+f" }, // Press Alt+Shift+D to open a new pane. // - "split": "auto" makes this pane open in the direction that provides the most surface area. // - "splitMode": "duplicate" makes the new pane use the focused pane's profile. // To learn more about panes, visit https://aka.ms/terminal-panes { "command": { "action": "splitPane", "split": "auto", "splitMode": "duplicate" }, "keys": "alt+shift+d" } ] } ```

claunia commented

@DHowett commented on GitHub (Nov 22, 2020):

Huh, alright. I'll need a bit to think about this.

We added some new crash handlers in 1.4 that will make it easier to get information from these crashes, but I need some time to write up the instructions. We've never used them before! 😁

@DHowett commented on GitHub (Nov 22, 2020): Huh, alright. I'll need a bit to think about this. We added some new crash handlers in 1.4 that will make it easier to get information from these crashes, but I need some time to write up the instructions. We've never used them before! 😁

claunia commented

@PreetSangha commented on GitHub (Nov 22, 2020):

I don't know if it means anything but I'm using Oh My Posh and powershell is the the default shell I use.

@PreetSangha commented on GitHub (Nov 22, 2020): I don't know if it means anything but I'm using Oh My Posh and powershell is the the default shell I use.

claunia commented

@DHowett commented on GitHub (Nov 22, 2020):

Alright, this is a long shot.

Can you download this file (15fd93e628/Terminal.wprp), raw, and save it as Terminal.wprp?
As an administrator, run wpr -start C:\Path\To\Terminal.wprp!Terminal (the !Terminal part is important)
Launch terminal and crash it.
As an administrator, run wpr -stop C:\Users\MyUserName\Desktop\terminal.etl
E-mail me a copy of terminal.etl

It should only contain information generated by Terminal, so it's fairly minimal. 😄

@DHowett commented on GitHub (Nov 22, 2020): Alright, this is a long shot. 1. Can you download this file (https://gist.githubusercontent.com/DHowett/2636e8bf86a837ffa16293acf803bb52/raw/15fd93e628e620578a7595408c88c8bce2fda4a6/Terminal.wprp), raw, and save it as `Terminal.wprp`? 2. **As an administrator**, run `wpr -start C:\Path\To\Terminal.wprp!Terminal` (the `!Terminal` part is important) 3. Launch terminal and crash it. 3. **As an administrator**, run `wpr -stop C:\Users\MyUserName\Desktop\terminal.etl` 3. E-mail me a copy of `terminal.etl` It should only contain information generated by Terminal, so it's fairly minimal. :smile:

claunia commented

@DHowett commented on GitHub (Nov 22, 2020):

I apologize -- I just updated Terminal.wprp for something I forgot.

@DHowett commented on GitHub (Nov 22, 2020): I apologize -- I just updated Terminal.wprp for something I forgot.

claunia commented

@DHowett commented on GitHub (Nov 22, 2020):

Alright, so this is a really strange crash. Can you add "fontFace": "Consolas" to the Windows PowerShell profile in your settings? I've never seen this before, but the text renderer is failing to find a font (our default font, Cascadia Mono, which comes with the application(!)) and actually failing because of it. That's totally new.

@DHowett commented on GitHub (Nov 22, 2020): Alright, so this is a really strange crash. Can you add `"fontFace": "Consolas"` to the Windows PowerShell profile in your settings? I've never seen this before, but the text renderer is failing to find a font (our default font, Cascadia Mono, which comes with the application(!)) and _actually failing because of it_. That's totally new.

claunia commented

@DHowett commented on GitHub (Nov 22, 2020):

Error info:

{2291683331; ; 0; TerminalApp.dll; 1;
winrt::hresult_error: A font file could not be opened because the
file, directory, network location, drive, or other storage location
does not exist or is unavailable.; 39812; ; 0; ; ; 0; ; }

@DHowett commented on GitHub (Nov 22, 2020): Error info: ``` {2291683331; ; 0; TerminalApp.dll; 1; winrt::hresult_error: A font file could not be opened because the file, directory, network location, drive, or other storage location does not exist or is unavailable.; 39812; ; 0; ; ; 0; ; } ```

claunia commented

@PreetSangha commented on GitHub (Nov 22, 2020):

That worked. Thank you do much for you efforts and so quickly.

So where would the font be :-D

@PreetSangha commented on GitHub (Nov 22, 2020): That worked. Thank you do much for you efforts and so quickly. So where would the font be :-D

claunia commented

@PreetSangha commented on GitHub (Nov 22, 2020):

Ok I reinstalled the fonts. But it still doesn't work if I remove the "fontFace": "Consolas" from the profile.

@PreetSangha commented on GitHub (Nov 22, 2020): Ok I reinstalled the fonts. But it still doesn't work if I remove the `"fontFace": "Consolas"` from the profile.

claunia commented

@KalleOlaviNiemitalo commented on GitHub (Nov 22, 2020):

The Untrusted Font Blocking policy setting comes to mind, but Windows Terminal appears to use DirectWrite rather than GDI, so I'm not sure the setting matters at all.

@KalleOlaviNiemitalo commented on GitHub (Nov 22, 2020): The [Untrusted Font Blocking](<https://docs.microsoft.com/windows/security/threat-protection/block-untrusted-fonts-in-enterprise> "Block untrusted fonts in an enterprise (Windows 10) - Windows security | Microsoft Docs") policy setting comes to mind, but Windows Terminal appears to use DirectWrite rather than GDI, so I'm not sure the setting matters at all.

claunia commented

@DHowett commented on GitHub (Nov 23, 2020):

Quick question -- can you run sc.exe query FontCache?

@KalleOlaviNiemitalo Good thinking! I gave blocking a shot but was unable to repro this, unfortunately. You're right that it doesn't seem to apply here 😄

@DHowett commented on GitHub (Nov 23, 2020): Quick question -- can you run `sc.exe query FontCache`? @KalleOlaviNiemitalo Good thinking! I gave blocking a shot but was unable to repro this, unfortunately. You're right that it doesn't seem to apply here :smile:

claunia commented

@DHowett commented on GitHub (Nov 23, 2020):

Since we've isolated the issue to being DirectWrite-related (that error code is in the DWrite error namespace 😄), if you're feeling up to it I would love to get a DirectWrite ETL from you during the crash!

this file -> DirectWrite.wprp
wpr -start DirectWrite.wprp
crash Terminal!
wpr -stop dwrite.etl
mail up a copy of dwrite.etl 😁

If I can't figure this one out, I'll forward it straight on to my friends over in DWrite.

@DHowett commented on GitHub (Nov 23, 2020): Since we've isolated the issue to being DirectWrite-related (that error code is in the DWrite error namespace :smile:), if you're feeling up to it I would _love_ to get a DirectWrite ETL from you during the crash! 1. [this file](https://gist.github.com/DHowett/2636e8bf86a837ffa16293acf803bb52/raw/15fd93e628e620578a7595408c88c8bce2fda4a6/DirectWrite.wprp) -> `DirectWrite.wprp` 2. `wpr -start DirectWrite.wprp` 3. crash Terminal! 4. `wpr -stop dwrite.etl` 5. mail up a copy of dwrite.etl :grin: If I can't figure this one out, I'll forward it straight on to my friends over in DWrite.

claunia commented

@PreetSangha commented on GitHub (Nov 24, 2020):

Ok step 1:

@PreetSangha commented on GitHub (Nov 24, 2020): Ok step 1: ![image](https://user-images.githubusercontent.com/15098094/100048824-aee40900-2e7a-11eb-8b49-f19b76d052b3.png)

claunia commented

@PreetSangha commented on GitHub (Nov 24, 2020):

Step 2: I commented ou tthe default font face of consolas

However Terminal no longer crashes.

If we can work what I need to do to get it that state again (:-D) I'm happy to create etl for you.

@PreetSangha commented on GitHub (Nov 24, 2020): Step 2: I commented ou tthe default font face of consolas ![image](https://user-images.githubusercontent.com/15098094/100048840-bd322500-2e7a-11eb-85fc-a506c2998c89.png) **However Terminal no longer crashes.** If we can work what I need to do to get it that state again (:-D) I'm happy to create etl for you.

claunia commented

@greg-hammond commented on GitHub (Dec 12, 2020):

I have the same problem, and does not appear to be related to fontFace setting as described above.
Version: 1.4.3243.0
Description: Open wt => it opens, seemingly normally, then the window just vaporizes anywhere from 2-10 seconds later (without doing any typing or mouse clicks inside the window)
I changed settings to use cmd as the default window.
I've never seen this before today, and use wt most days.
Windows 10 2004 19041.685

attempted resolution steps:

tried "repair", no luck
tried "reset", no luck
after the reset, went into settings.json and added "fontFace": "Consolas" under the "defaults", no luck.

I am going to send you an etl file using your instructions above.

TIA for your help!

Update 6/27/21: 6 months later. still crashing, still not resolved. maybe different causes/mechanisms, but i'm not spending any more time triaging this stuff. it's a terminal program. #uninstall #cmd-works-for-me #bash-works-for-me.

@greg-hammond commented on GitHub (Dec 12, 2020): I have the same problem, and does not appear to be related to fontFace setting as described above. Version: 1.4.3243.0 Description: Open wt => it opens, seemingly normally, then the window just vaporizes anywhere from 2-10 seconds later (without doing any typing or mouse clicks inside the window) I changed settings to use cmd as the default window. I've never seen this before today, and use wt most days. Windows 10 2004 19041.685 attempted resolution steps: - tried "repair", no luck - tried "reset", no luck - after the reset, went into settings.json and added "fontFace": "Consolas" under the "defaults", no luck. I am going to send you an etl file using your instructions above. TIA for your help! Update 6/27/21: 6 months later. still crashing, still not resolved. maybe different causes/mechanisms, but i'm not spending any more time triaging this stuff. it's a terminal program. #uninstall #cmd-works-for-me #bash-works-for-me.

claunia commented

@watfordsuzy commented on GitHub (May 26, 2021):

@DHowett I'm receiving the same crash as @PreetSangha. Adding the fontFace to every terminal I use fixed it for me.

Of note:

Terminal was active on Monday (2021-05-24), and I used it all day
I was out-of-office yesterday (2021-05-25)
I came back in today (2021-05-26) to find Terminal is no longer open (no crash event in Event Viewer on the 24th or 25th)
Attempts to relaunch it failed with the crash in ucrtbase

For posterity:

Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x43fc
Faulting application start time: 0x01d7524345d1c165
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: b3ff4c65-b83c-416e-b836-059fad70f14c
Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I've emailed you the WER package.

@watfordsuzy commented on GitHub (May 26, 2021): @DHowett I'm receiving the same crash as @PreetSangha. Adding the fontFace to every terminal I use fixed it for me. Of note: - Terminal was active on Monday (2021-05-24), and I used it all day - I was out-of-office yesterday (2021-05-25) - I came back in today (2021-05-26) to find Terminal is no longer open (no crash event in Event Viewer on the 24th or 25th) - Attempts to relaunch it failed with the crash in `ucrtbase` For posterity: ``` Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process id: 0x43fc Faulting application start time: 0x01d7524345d1c165 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: b3ff4c65-b83c-416e-b836-059fad70f14c Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` I've emailed you the WER package.

claunia commented

@DHowett commented on GitHub (May 26, 2021):

Thanks for this -- that is a really useful data point.

@DHowett commented on GitHub (May 26, 2021): Thanks for this -- that is a really useful data point.

claunia commented

@SpitFire-666 commented on GitHub (May 27, 2021):

Same here. Worked yesterday, rebooted computer, now WT won't launch.

Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process ID: 0x2858
Faulting application start time: 0x01d75284d2841d36
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 738df3c9-37ab-4ad0-b704-666f6e33a2c1
Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I tried adding the fontface lines to the profiles in the .json, but no luck:

@SpitFire-666 commented on GitHub (May 27, 2021): Same here. Worked yesterday, rebooted computer, now WT won't launch. ``` Faulting application name: WindowsTerminal.exe, version: 1.8.2105.24004, time stamp: 0x60ac2e94 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process ID: 0x2858 Faulting application start time: 0x01d75284d2841d36 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report ID: 738df3c9-37ab-4ad0-b704-666f6e33a2c1 Faulting package full name: Microsoft.WindowsTerminal_1.8.1444.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` I tried adding the fontface lines to the profiles in the .json, but no luck: ![image](https://user-images.githubusercontent.com/38451588/119743596-9312fb80-becd-11eb-93bf-e2fb12d5ac7c.png)

claunia commented

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

If you're impacted by this after the 1.8 update, can you go into Settings > Applications > All Applications, choose Windows Terminal and then Repair? We've heard that this helps.

@DHowett commented on GitHub (May 27, 2021): If you're impacted by this after the 1.8 update, can you go into Settings > Applications > All Applications, choose Windows Terminal and then **Repair**? We've heard that this helps.

claunia commented

@SpitFire-666 commented on GitHub (May 27, 2021):

@DHowett yep that worked! Thanks.

@SpitFire-666 commented on GitHub (May 27, 2021): @DHowett yep that worked! Thanks.

claunia commented

@Simran-B commented on GitHub (May 27, 2021):

Just ran into the same issue. Terminal was working fine yesterday, today it wouldn't launch. If I add "fontFace": "Consolas" in settings.json under profiles.defaults then it starts just fine. However, resetting the app also worked for me. I will send the diagnostic files just in case.

@Simran-B commented on GitHub (May 27, 2021): Just ran into the same issue. Terminal was working fine yesterday, today it wouldn't launch. If I add `"fontFace": "Consolas"` in `settings.json` under `profiles.defaults` then it starts just fine. However, resetting the app also worked for me. I will send the diagnostic files just in case.

claunia commented

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

@campbellkerr as a quick note your JSON was missing commas after the source property and before the fontFace property, which would have been an impact.

@watfordsuzy commented on GitHub (May 27, 2021): @campbellkerr as a quick note your JSON was missing commas after the source property and before the fontFace property, which would have been an impact.

claunia commented

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

I started experiencing this, but only on one profile on my machine. It still works perfectly on the other. I've tried the reset, repair, restoring the .backup profile, and even adding the default font consolas setting. Nothing works for me, it opens and crashes with the same MobEx error. It stopped working a few days ago, FWIW. It had worked perfectly fine up until then.

@x86txt commented on GitHub (May 30, 2021): I started experiencing this, but only on one profile on my machine. It still works perfectly on the other. I've tried the reset, repair, restoring the .backup profile, and even adding the default font consolas setting. Nothing works for me, it opens and crashes with the same MobEx error. It stopped working a few days ago, FWIW. It had worked perfectly fine up until then.

claunia commented

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

Same here, working on Friday, not working on Monday, with similar event viewer details:

Faulting application name: WindowsTerminal.exe, version: 1.9.2105.24005, time stamp: 0x60ac3929
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x4f24
Faulting application start time: 0x01d755b84ae7db8d
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.9.1445.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\windows\System32\ucrtbase.dll
Report Id: 8673480e-1061-4c66-a519-e437e727e907
Faulting package full name: Microsoft.WindowsTerminalPreview_1.9.1445.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Repairing did help.

@riprwwa commented on GitHub (May 31, 2021): Same here, working on Friday, not working on Monday, with similar event viewer details: ``` Faulting application name: WindowsTerminal.exe, version: 1.9.2105.24005, time stamp: 0x60ac3929 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process id: 0x4f24 Faulting application start time: 0x01d755b84ae7db8d Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.9.1445.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\windows\System32\ucrtbase.dll Report Id: 8673480e-1061-4c66-a519-e437e727e907 Faulting package full name: Microsoft.WindowsTerminalPreview_1.9.1445.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` Repairing did help.

claunia commented

@NeKJ commented on GitHub (Jun 1, 2021):

Alright, so this is a really strange crash. Can you add "fontFace": "Consolas" to the Windows PowerShell profile in your settings? I've never seen this before, but the text renderer is failing to find a font (our default font, Cascadia Mono, which comes with the application(!)) and actually failing because of it. That's totally new.

This worked for me too. I added the "fontFace": "Consolas", on all my profiles (profiles.list array) and voila it worked. Now I need to find out how to restore my settings after numerous uninstallers/repairs and resets...

@NeKJ commented on GitHub (Jun 1, 2021): > > > Alright, so this is a really strange crash. Can you add `"fontFace": "Consolas"` to the Windows PowerShell profile in your settings? I've never seen this before, but the text renderer is failing to find a font (our default font, Cascadia Mono, which comes with the application(!)) and _actually failing because of it_. That's totally new. This worked for me too. I added the `"fontFace": "Consolas",` on all my profiles (profiles.list array) and voila it worked. Now I need to find out how to restore my settings after numerous uninstallers/repairs and resets...

claunia commented

@zadjii-msft commented on GitHub (Jun 1, 2021):

If folks are coming to this thread after the update to 1.8.1444 or 1.9.1445 - the original issue in this thread probably isn't the root cause you're actually hitting right now. That's more likely #10211.

That being said, they're both caused by the same thing - failing to open the font as we're creating the window, and then us throwing an exception instead of logging the error and letting font fallback do it's thing.

@DHowett We never did get a solid repro on OP's issue, but I'm guessing that #10260 will fix this as well. Sanity check that?

@zadjii-msft commented on GitHub (Jun 1, 2021): If folks are coming to this thread after the update to 1.8.1444 or 1.9.1445 - the original issue in this thread _probably_ isn't the root cause you're actually hitting right now. That's more likely #10211. That being said, they're both caused by the same thing - failing to open the font as we're creating the window, and then us throwing an exception instead of logging the error and letting font fallback do it's thing. @DHowett We never did get a solid repro on OP's issue, but I'm guessing that #10260 will fix this as well. Sanity check that?

claunia commented

@DHowett commented on GitHub (Jun 1, 2021):

It should at least help. Failing to open the font because the app platform messed up our package is likely the “canary in the coal mine,” but we may be able to hobble along until the update is finished.

@DHowett commented on GitHub (Jun 1, 2021): It should at least help. Failing to open the font because the app platform messed up our package is likely the “canary in the coal mine,” but we may be able to hobble along until the update is finished.

claunia commented

@Rafagd commented on GitHub (Jun 1, 2021):

Just ran into the same issue. Terminal was working fine yesterday, today it wouldn't launch. If I add "fontFace": "Consolas" in settings.json under profiles.defaults then it starts just fine. However, resetting the app also worked for me. I will send the diagnostic files just in case.

Restart, Reset, Repair and Uninstall/Reinstall did not work for me. But this instantly solved the problem.

@Rafagd commented on GitHub (Jun 1, 2021): > > > Just ran into the same issue. Terminal was working fine yesterday, today it wouldn't launch. If I add `"fontFace": "Consolas"` in `settings.json` under `profiles.defaults` then it starts just fine. However, resetting the app also worked for me. I will send the diagnostic files just in case. Restart, Reset, Repair and Uninstall/Reinstall did not work for me. But this instantly solved the problem.

claunia commented

@x86txt commented on GitHub (Jun 1, 2021):

If folks are coming to this thread after the update to 1.8.1444 or 1.9.1445 - the original issue in this thread probably isn't the root cause you're actually hitting right now. That's more likely #10211.

That being said, they're both caused by the same thing - failing to open the font as we're creating the window, and then us throwing an exception instead of logging the error and letting font fallback do it's thing.

@DHowett We never did get a solid repro on OP's issue, but I'm guessing that #10260 will fix this as well. Sanity check that?

I randomly tried again today and it's working. I'm on version 1.8.1444.0. As per a comment in https://github.com/microsoft/terminal/issues/10211 - I too did reboot my machine in between, so perhaps that is what it needed for the font to be recognized?

Either way, it's sooo nice to have it back. I forgot how much of a PITA cmd.exe was compared to it. Nice job, folks.

@x86txt commented on GitHub (Jun 1, 2021): > If folks are coming to this thread after the update to 1.8.1444 or 1.9.1445 - the original issue in this thread _probably_ isn't the root cause you're actually hitting right now. That's more likely #10211. > > That being said, they're both caused by the same thing - failing to open the font as we're creating the window, and then us throwing an exception instead of logging the error and letting font fallback do it's thing. > > @DHowett We never did get a solid repro on OP's issue, but I'm guessing that #10260 will fix this as well. Sanity check that? I randomly tried again today and it's working. I'm on version 1.8.1444.0. As per a comment in https://github.com/microsoft/terminal/issues/10211 - I too did reboot my machine in between, so perhaps that is what it needed for the font to be recognized? Either way, it's sooo nice to have it back. I forgot how much of a PITA cmd.exe was compared to it. Nice job, folks.

claunia commented

@Talmanes commented on GitHub (Jun 2, 2021):

Same problem fixed by adding the fontFace. Realized not all Cascadia Code fonts were imported, just the most basic one from Terminal install. Installed all from https://github.com/microsoft/cascadia-code/releases/tag/v2105.24, specifically the OTF files. Can now remove fontFace and it loads normally.

@Talmanes commented on GitHub (Jun 2, 2021): Same problem fixed by adding the `fontFace`. Realized not all **Cascadia Code** fonts were imported, just the most basic one from Terminal install. Installed all from https://github.com/microsoft/cascadia-code/releases/tag/v2105.24, specifically the OTF files. Can now remove `fontFace` and it loads normally.

claunia commented

@x86txt commented on GitHub (Jun 4, 2021):

Problem came back after I adjusted the font settings for cmd and WSL. Attached is the settings.json that are broken.

Renaming it to .old, logging out, and then back in fixes it.
settings.json.old.zip

@x86txt commented on GitHub (Jun 4, 2021): Problem came back after I adjusted the font settings for cmd and WSL. Attached is the settings.json that are broken. Renaming it to .old, logging out, and then back in fixes it. [settings.json.old.zip](https://github.com/microsoft/terminal/files/6598189/settings.json.old.zip)

claunia commented