Windows Terminal 0.7 immediately crashes on startup #5253

Closed
opened 2026-01-31 00:08:43 +00:00 by claunia · 26 comments
Owner

Originally created by @johnc44 on GitHub (Nov 27, 2019).

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.

Originally created by @johnc44 on GitHub (Nov 27, 2019). # 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.
claunia added the Issue-BugResolution-DuplicateProduct-TerminalSeverity-Crash labels 2026-01-31 00:08:44 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Nov 27, 2019):

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

@zadjii-msft commented on GitHub (Nov 27, 2019): 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
Author
Owner

@ghost commented on GitHub (Nov 27, 2019):

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!

image image

@ghost commented on GitHub (Nov 27, 2019): Hi there!<br><br>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?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
Author
Owner

@johnc44 commented on GitHub (Nov 27, 2019):

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

@johnc44 commented on GitHub (Nov 27, 2019): That was quick! I've submitted something through feedback hub now. I didn't realise it could be used for things like this.
Author
Owner

@zadjii-msft commented on GitHub (Nov 27, 2019):

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

@zadjii-msft commented on GitHub (Nov 27, 2019): @johnc44 Could you share the `aka.ms` link from the "Share my feedback" button here? I can't look it up without that unfortunately 🤣
Author
Owner

@johnc44 commented on GitHub (Nov 27, 2019):

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

@johnc44 commented on GitHub (Nov 27, 2019): Oops, sorry - https://aka.ms/AA6ptgu
Author
Owner

@Viruslav commented on GitHub (Nov 27, 2019):

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.

@Viruslav commented on GitHub (Nov 27, 2019): 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.
Author
Owner

@zhoupro commented on GitHub (Nov 28, 2019):

Same problem

@zhoupro commented on GitHub (Nov 28, 2019): Same problem
Author
Owner

@Ma5ker commented on GitHub (Nov 28, 2019):

Same problem,Microsoft Windows [Version 10.0.18363.476]

@Ma5ker commented on GitHub (Nov 28, 2019): Same problem,Microsoft Windows [Version 10.0.18363.476]
Author
Owner

@johnc44 commented on GitHub (Nov 28, 2019):

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

@johnc44 commented on GitHub (Nov 28, 2019): Just noticed that I do get a single colour rectangle as per @Viruslav - I just didn't notice it yesterday.
Author
Owner

@gregmuellegger commented on GitHub (Nov 28, 2019):

Same problem here.

@gregmuellegger commented on GitHub (Nov 28, 2019): Same problem here.
Author
Owner

@a-was commented on GitHub (Nov 28, 2019):

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

@a-was commented on GitHub (Nov 28, 2019): Same here. Updated today and app crashes after start. Only single grey color and then window immediately closed. I updated through MS Store.
Author
Owner

@owennewo commented on GitHub (Nov 28, 2019):

[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.

@owennewo commented on GitHub (Nov 28, 2019): [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.
Author
Owner

@Viruslav commented on GitHub (Nov 28, 2019):

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

@Viruslav commented on GitHub (Nov 28, 2019): I use custom scaling set at 160% on both PCs.
Author
Owner

@owennewo commented on GitHub (Nov 28, 2019):

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....

@owennewo commented on GitHub (Nov 28, 2019): 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....
Author
Owner

@elangelo commented on GitHub (Nov 29, 2019):

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

@elangelo commented on GitHub (Nov 29, 2019): I have the same tried deleting the appdata folder and i have no custom scaling set.
Author
Owner

@johnc44 commented on GitHub (Nov 29, 2019):

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

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

@johnc44 commented on GitHub (Nov 29, 2019): @owennewo Yes, I have custom scaling set to 135%, mirrored displays. ( I've already tried deleting profile.json which didn't help.
Author
Owner

@marknelson commented on GitHub (Nov 29, 2019):

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

@marknelson commented on GitHub (Nov 29, 2019): this is my first install - i'm seeing the same symptoms. 175% scaling. Yeah, deleted profile, same thing.
Author
Owner

@colcrunch commented on GitHub (Dec 1, 2019):

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

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

@colcrunch commented on GitHub (Dec 1, 2019): I am having the same issue as this after an app update. Feedback Hub link with Event Logs: https://aka.ms/AA6q4df
Author
Owner

@ghost commented on GitHub (Dec 2, 2019):

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

@ghost commented on GitHub (Dec 2, 2019): Hey guys, several usages are fine with normal 125% scale. But the Terminal crash when i use **custom scale** 138%.
Author
Owner

@zhoupro commented on GitHub (Dec 2, 2019):

I disable advanced scale, Now It works fine.

@zhoupro commented on GitHub (Dec 2, 2019): I disable advanced scale, Now It works fine.
Author
Owner

@zhoupro commented on GitHub (Dec 2, 2019):

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

Thanks for your tips.

@zhoupro commented on GitHub (Dec 2, 2019): > Hey guys, several usages are fine with normal 125% scale. > But the Terminal crash when i use **custom scale** 138%. Thanks for your tips.
Author
Owner

@gregmuellegger commented on GitHub (Dec 2, 2019):

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

@gregmuellegger commented on GitHub (Dec 2, 2019): Disabling custom scaling worked for me as well! Thanks so far.
Author
Owner

@Viruslav commented on GitHub (Dec 2, 2019):

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.

@Viruslav commented on GitHub (Dec 2, 2019): 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.
Author
Owner

@VictorNanka commented on GitHub (Dec 2, 2019):

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

@VictorNanka commented on GitHub (Dec 2, 2019): It’s working when I change the custom scale factor into default. Thanks a lot.
Author
Owner

@DHowett-MSFT commented on GitHub (Dec 2, 2019):

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

@DHowett-MSFT commented on GitHub (Dec 2, 2019): This looks like a /dupe of #3749. Thanks!
Author
Owner

@ghost commented on GitHub (Dec 2, 2019):

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!

@ghost commented on GitHub (Dec 2, 2019): 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5253