Terminal: Windows Terminal 0.7 immediately crashes on startup

[johnc44]

Environment

Microsoft Windows [Version 10.0.18363.476]
Windows Terminal 0.7

Steps to reproduce

Start Windows Terminal.

Expected behavior

Was hoping the application would open..

Actual behavior

The terminal icon appears in the start bar, then a moment later it disappears. The application never starts.

I've been using Windows Terminal for the last few versions and it's been fine. I upgraded to 0.7 today and now it no longer opens. I tried uninstalling and reinstalling it. I also tried explicitly removing profile.json, because i had previously changed it.

I've also tried rebooting.

[zadjii-msft]

Thanks for the report! Would you mind filing a report with the feedback hub so we can get a stack trace and see what's going on?

/feedback

[msftbot[bot]]

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

[johnc44]

That was quick! I've submitted something through feedback hub now. I didn't realise it could be used for things like this.

[zadjii-msft]

@johnc44 Could you share the aka.ms link from the "Share my feedback" button here? I can't look it up without that unfortunately 🤣

[johnc44]

Oops, sorry - https://aka.ms/AA6ptgu

[Viruslav]

I have almost the same issue/crash - the window shows as a non-transparent single color rectangle and then disappears. I tried resetting and reinstalling but nothing helped. I tried on 2 very different devices and it was the same. I already submitted a feedback in the Feedback Hub but unfortunately I didn't include a stack trace.

[zhoupro]

Same problem

[Ma5ker]

Same problem,Microsoft Windows [Version 10.0.18363.476]

[johnc44]

Just noticed that I do get a single colour rectangle as per @Viruslav - I just didn't notice it yesterday.

[gregmuellegger]

Same problem here.

[a-was]

Same here. Updated today and app crashes after start. Only single grey color and then window immediately closed.
I updated through MS Store.

[owennewo]

[Update: Apologies - you've already tried deleting your profiles.json] - you can probably ignore this message, but you may want to check whether the file you deleted was similar to the path below

[Update2: Are you using a custom scaling for fonts? There appears to be some startup crashes caused by that https://github.com/microsoft/terminal/issues/3749

Something to try...
Delete your terminal settings file (make a backup first!).

My settings file is below but there is a hash in the directory name so yours will probably be different:
<User>\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\profiles.json
My guess is that will get you up on your feet and you could play around with introducing parts of the old file to see what is causing the crash.

[Viruslav]

I use custom scaling set at 160% on both PCs.

[owennewo]

It would be useful to know if original poster has custom scaling. If so this issue can be marked as duplicate of #3749. It's entirely possible there is more than one reason for startup crashes....

[elangelo]

I have the same
tried deleting the appdata folder and i have no custom scaling set.

[johnc44]

@owennewo Yes, I have custom scaling set to 135%, mirrored displays. (

I've already tried deleting profile.json which didn't help.

[marknelson]

this is my first install - i'm seeing the same symptoms. 175% scaling. Yeah, deleted profile, same thing.

[colcrunch]

I am having the same issue as this after an app update.

Feedback Hub link with Event Logs:
https://aka.ms/AA6q4df

[vuhg]

Hey guys, several usages are fine with normal 125% scale.
But the Terminal crash when i use custom scale 138%.

[zhoupro]

I disable advanced scale, Now It works fine.

[zhoupro]

Hey guys, several usages are fine with normal 125% scale.
But the Terminal crash when i use custom scale 138%.

Thanks for your tips.

[gregmuellegger]

Disabling custom scaling worked for me as well! Thanks so far.

[Viruslav]

I'm not gonna change my custom scale factor. I'd rather not use this terminal. I'm sorry but this is not a solution. Everything else works just fine.

[VictorNanka]

It’s working when I change the custom scale factor into default. Thanks a lot.

[DHowett-MSFT]

This looks like a /dupe of #3749. Thanks!

[msftbot[bot]]

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!