Settings.json is not re-generated *when deleted* on 1.6 preview #12298

Open
opened 2026-01-31 03:11:39 +00:00 by claunia · 0 comments
Owner

Originally created by @WSLUser on GitHub (Jan 29, 2021).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] 19041
Windows Terminal version (if applicable): 1.6 Preview

Any other software?

Steps to reproduce

  1. Have Windows Terminal open
  2. Delete the existing settings.json.
  3. Open a new instance of Windows Terminal.
  4. Open Settings from the drop-down. It will offer to create one but will be blanked out.

Expected behavior

I expect all the default settings to be regenerated.

Actual behavior

While 1.5 correctly regenerates the settings.json, 1.6 does not. Verified by @carlos-zamora that it occurs on 1.5 too

I suspect it has something to do with the way it's tied to the Settings UI.

Originally created by @WSLUser on GitHub (Jan 29, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] 19041 Windows Terminal version (if applicable): 1.6 Preview Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Have Windows Terminal open 2. Delete the existing settings.json. 3. Open a new instance of Windows Terminal. 4. Open Settings from the drop-down. It will offer to create one but will be blanked out. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> I expect all the default settings to be regenerated. # Actual behavior <!-- What's actually happening? --> ~While 1.5 correctly regenerates the settings.json, 1.6 does not.~ Verified by @carlos-zamora that it occurs on 1.5 too I suspect it has something to do with the way it's tied to the Settings UI.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12298