Infobar for "make terminal the default" doesn't remember it was dismissed upon new OS flight #15822

Closed
opened 2026-01-31 04:49:24 +00:00 by claunia · 13 comments
Owner

Originally created by @asklar on GitHub (Nov 9, 2021).

Windows Terminal version (or Windows build number)

22496

Other Software

No response

Steps to reproduce

launch terminal, get the infobar about making Terminal de default console.
Close it, don't make it the default

get a new OS flight
launch terminal - same infobar shows up again

Expected Behavior

setting gets persisted

Actual Behavior

terminal insists

Originally created by @asklar on GitHub (Nov 9, 2021). ### Windows Terminal version (or Windows build number) 22496 ### Other Software _No response_ ### Steps to reproduce launch terminal, get the infobar about making Terminal de default console. Close it, don't make it the default get a new OS flight launch terminal - same infobar shows up again ### Expected Behavior setting gets persisted ### Actual Behavior terminal insists
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 04:49:24 +00:00
Author
Owner

@DHowett commented on GitHub (Nov 9, 2021):

@asklar can you share a copy of state.json from %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState?

Closing the infobar should make us record that it was dismissed. This is not tracked per OS version or stored anywhere that the OS would clear on upgrade.

@DHowett commented on GitHub (Nov 9, 2021): @asklar can you share a copy of `state.json` from `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState`? Closing the infobar should make us record that it was dismissed. This is not tracked per OS version or stored anywhere that the OS would clear on upgrade.
Author
Owner

@DHowett commented on GitHub (Nov 9, 2021):

(This assumes that you are using Terminal Stable and not switching back and forth between Stable and Preview, and that you are not using unpackaged terminal -- since you did not include a Terminal version, I must assume the formermost.)

@DHowett commented on GitHub (Nov 9, 2021): (This assumes that you are using Terminal Stable and not switching back and forth between Stable and Preview, and that you are not using unpackaged terminal -- since you did not include a Terminal version, I must assume the formermost.)
Author
Owner

@asklar commented on GitHub (Nov 9, 2021):

Using Preview, version 1.11.2921.0

{
	"dismissedMessages" : 
	[
		"setAsDefault"
	],
	"generatedProfiles" : 
	[
		"{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
		"{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
		"{574e775e-4f2a-5b96-ac1e-a2962a402336}",
		"{b453ae62-4e3d-5e58-b989-0a998ec441b8}"
	]
}

This is after dismissing the message. I guess I should check the content of this file after the next flight?
or maybe app updates/installs are clearing the localstate folder?

@asklar commented on GitHub (Nov 9, 2021): Using Preview, version 1.11.2921.0 ``` { "dismissedMessages" : [ "setAsDefault" ], "generatedProfiles" : [ "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "{b453ae62-4e3d-5e58-b989-0a998ec441b8}" ] } ``` This is after dismissing the message. I guess I should check the content of this file after the next flight? or maybe app updates/installs are clearing the localstate folder?
Author
Owner

@DHowett commented on GitHub (Nov 9, 2021):

or maybe app updates/installs are clearing the localstate folder?

That would definitely be worth checking! That's where we keep our settings, as well. Have you noticed Terminal deleting all your settings across OS upgrades? Would you mind capturing a snapshot of that directory next time you flight?

@DHowett commented on GitHub (Nov 9, 2021): > or maybe app updates/installs are clearing the localstate folder? That would definitely be worth checking! That's where we keep our settings, as well. Have you noticed Terminal deleting all your settings across OS upgrades? Would you mind capturing a snapshot of that directory next time you flight?
Author
Owner

@ghost commented on GitHub (Nov 13, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 13, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@DHowett commented on GitHub (Nov 16, 2021):

(I'll reopen this for another 7 days)

@DHowett commented on GitHub (Nov 16, 2021): (I'll reopen this for another 7 days)
Author
Owner

@ghost commented on GitHub (Nov 21, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 21, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@asklar commented on GitHub (Nov 21, 2021):

just hit this again, and this is the content now:

{
        "generatedProfiles" :
        [
                "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
                "{63e31163-583f-5850-9c1e-24e227dd2da9}",
                "{b453ae62-4e3d-5e58-b989-0a998ec441b8}"
        ]
}
@asklar commented on GitHub (Nov 21, 2021): just hit this again, and this is the content now: ```json { "generatedProfiles" : [ "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "{63e31163-583f-5850-9c1e-24e227dd2da9}", "{b453ae62-4e3d-5e58-b989-0a998ec441b8}" ] } ```
Author
Owner

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

It is deeply concerning that your state is getting destroyed but your settings are not... or.. are they? Do you tend to change settings.json at all?

@DHowett commented on GitHub (Nov 22, 2021): It is deeply concerning that your state is getting destroyed but your settings are not... or.. are they? Do you tend to change `settings.json` at all?
Author
Owner

@asklar commented on GitHub (Nov 22, 2021):

I haven't changed the state in a while... the only change I remember making in the last few months is adding -nologo to pwsh since I don't want to be reminded of the "build du jour" every time

@asklar commented on GitHub (Nov 22, 2021): I haven't changed the state in a while... the only change I remember making in the last few months is adding `-nologo` to pwsh since I don't want to be reminded of the "build du jour" every time
Author
Owner

@zadjii-msft commented on GitHub (Dec 2, 2021):

An OS update shouldn't be clearing out things from %LOCALAPPDATA%, right? Yea of course not, the settings file doesn't get deleted. There's also no code that's shipped yet for blowing away the elevated version of that file, so it's not like I'm accidentally doing that...

Maybe this is the thing where we can't find the settings file, or find that it's empty, and then re-create the state. Trick is, why do we think we can't find it? (and why isn't anyone else on the team seeing this?)

@zadjii-msft commented on GitHub (Dec 2, 2021): An OS update shouldn't be clearing out things from `%LOCALAPPDATA%`, right? Yea of course not, the settings file doesn't get deleted. There's also no code that's shipped yet for blowing away the elevated version of that file, so it's not like I'm accidentally doing that... Maybe this is the thing where we can't find the settings file, or find that it's empty, and then re-create the state. Trick is, why do we think we can't find it? (and why isn't anyone else on the team seeing this?)
Author
Owner

@zadjii-msft commented on GitHub (Jul 5, 2022):

You know, we've shipped this warning for a few months now and we've only ever gotten this one report of it. That's super weird. the rest of the code around this has stabilized for a few releases now - is this still happening/?

@zadjii-msft commented on GitHub (Jul 5, 2022): You know, we've shipped this warning for a few months now and we've only ever gotten this one report of it. That's super weird. the rest of the code around this has stabilized for a few releases now - is this still happening/?
Author
Owner

@asklar commented on GitHub (Jul 5, 2022):

haven't seen this recently

@asklar commented on GitHub (Jul 5, 2022): haven't seen this recently
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15822