starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows Terminal settings reset on reinstall #7966

New Issue
Closed
opened 2026-01-31 01:17:10 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 01:17:10 +00:00
Owner
Copy Link

Originally created by @dgellow on GitHub (May 6, 2020).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version (if applicable):

Version: 0.11.1251.0

Any other software?

-

Steps to reproduce

  1. Install Windows Terminal from Microsoft Store
  2. Modify Windows Terminal settings
  3. Uninstall Windows Terminal
  4. Reinstall Windows Terminal from Microsoft Store

At this point notice how you just lost your precious Windows Terminal settings and start crying.

Expected behavior

Windows Terminal settings are stored in the user data and should persist between reinstallation.

Actual behavior

Settings are reset each time the application is installed.

Originally created by @dgellow on GitHub (May 6, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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] Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): Version: 0.11.1251.0 Any other software? - ``` # Steps to reproduce 1. Install Windows Terminal from Microsoft Store 2. Modify Windows Terminal settings 3. Uninstall Windows Terminal 4. Reinstall Windows Terminal from Microsoft Store At this point notice how you just lost your precious Windows Terminal settings and start crying. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Windows Terminal settings are stored in the user data and should persist between reinstallation. # Actual behavior Settings are reset each time the application is installed.
claunia added the Resolution-By-DesignNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 01:17:10 +00:00
claunia commented 2026-01-31 01:17:11 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 7, 2020):

This is, unfortunately, how applications deployed through the store work. When you uninstall them, their settings are cleared.

@DHowett-MSFT commented on GitHub (May 7, 2020): This is, unfortunately, how applications deployed through the store work. When you uninstall them, their settings are cleared.
claunia commented 2026-01-31 01:17:11 +00:00
Author
Owner
Copy Link

@dgellow commented on GitHub (May 7, 2020):

Isn't the Roaming Folder exactly for that purpose? I.e: keep user data between an application installation.

@dgellow commented on GitHub (May 7, 2020): Isn't the [Roaming Folder](https://docs.microsoft.com/en-us/uwp/api/windows.storage.applicationdata.roamingfolder) exactly for that purpose? I.e: keep user data between an application installation.
claunia commented 2026-01-31 01:17:11 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 7, 2020):

We used to store settings in the roaming folder, but it turns out that people have different WSL distributions and powershell installations on different computers, and really do want different things on their other machines. We moved out of the roaming folder, and then found that it was resurrecting settings from very old versions of Terminal back into the roaming folder.

This is an area of active development, but "move settings back to the roaming folder" isn't going to be a viable solution. Sorry!

@DHowett-MSFT commented on GitHub (May 7, 2020): We used to store settings in the roaming folder, but it turns out that people have different WSL distributions and powershell installations on different computers, and really do want different things on their other machines. We moved _out_ of the roaming folder, and then found that it was resurrecting settings from _very old_ versions of Terminal back into the roaming folder. This is an area of active development, but "move settings back to the roaming folder" isn't going to be a viable solution. Sorry!
claunia commented 2026-01-31 01:17:12 +00:00
Author
Owner
Copy Link

@dgellow commented on GitHub (May 8, 2020):

Hey @DHowett-MSFT. Thanks for answering, I appreciate.

If it is an area of active development, is there an issue number I can subscribe to if I want to follow the discussion? If there isn't one yet, would it then make sense to reopen this issue? Or is the discussions and development happening outside of the GitHub repository?

I'm fine with the issue being closed, I just want to know where I can get update on that development, even just by intellectual curiosity.

@dgellow commented on GitHub (May 8, 2020): Hey @DHowett-MSFT. Thanks for answering, I appreciate. If it is an area of active development, is there an issue number I can subscribe to if I want to follow the discussion? If there isn't one yet, would it then make sense to reopen this issue? Or is the discussions and development happening outside of the GitHub repository? I'm fine with the issue being closed, I just want to know where I can get update on that development, even just by intellectual curiosity.
claunia commented 2026-01-31 01:17:12 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 9, 2020):

The best issue you can follow for this is gonna be #2933. Thanks!

@DHowett-MSFT commented on GitHub (May 9, 2020): The best issue you can follow for this is gonna be #2933. Thanks!
claunia commented 2026-01-31 01:17:12 +00:00
Author
Owner
Copy Link

@chylex commented on GitHub (Oct 23, 2022):

In case someone else finds this issue after it happened to them, if you have system backups (which you should), you can restore the settings by copy/pasting contents of this folder from the backup:

C:\Users\<USERNAME>\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe
@chylex commented on GitHub (Oct 23, 2022): In case someone else finds this issue after it happened to them, if you have system backups (which you should), you can restore the settings by copy/pasting contents of this folder from the backup: ``` C:\Users\<USERNAME>\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Needs-Triage Resolution-By-Design
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7966
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?