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

Profiles completely reset #14289

New Issue
Closed
opened 2026-01-31 04:06:19 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 04:06:19 +00:00
Owner
Copy Link

Originally created by @tracker1 on GitHub (Jun 21, 2021).

Windows Terminal version (or Windows build number)

1.8.1521.0

Other Software

  • Terminal 1.8.1521.0
  • Windows 10.0.19043.0
  • WSL2
  • Ubuntu LTS
  • Docker Desktop (WSL2)

Steps to reproduce

  • Set "Ubuntu" to a startup directory under \wsl$... (Ubuntu user's home directory) - save
  • Set "Ubuntu" as Default profile - save
  • Reboot

Expected Behavior

I would expect that my profile settings should remain intact until whatever process is checking for subsystems available to terminal to complete. I would expect that my starting directory for my WSL2 Ubuntu profile to not get reset.

Actual Behavior

About 1 in 5 reboots, I see a "There was a problem with your settings..." or some such result. The list of Profiles is reset, the default is now Powershell, and all the customizations are gone. There's no WSL profiles for several; minutes, only Powershell and CMD. Several minutes later "Ubuntu" shows up again, but customizations also gone, namely the starting directory, and it's no longer my default profile.

I've had similar issues on my personal desktop. It's very annoying to say the least since 90% of my desktop time is in development, under the WSL environment.

NOTE: I also created a custom profile for WSL, not just the detected one, and that disappears as well.

Originally created by @tracker1 on GitHub (Jun 21, 2021). ### Windows Terminal version (or Windows build number) 1.8.1521.0 ### Other Software - Terminal 1.8.1521.0 - Windows 10.0.19043.0 - WSL2 - Ubuntu LTS - Docker Desktop (WSL2) ### Steps to reproduce - Set "Ubuntu" to a startup directory under \\wsl$\... (Ubuntu user's home directory) - save - Set "Ubuntu" as Default profile - save - Reboot ### Expected Behavior I would expect that my profile settings should remain intact until whatever process is checking for subsystems available to terminal to complete. I would expect that my starting directory for my WSL2 Ubuntu profile to not get reset. ### Actual Behavior About 1 in 5 reboots, I see a "There was a problem with your settings..." or some such result. The list of Profiles is reset, the default is now Powershell, and all the customizations are gone. There's no WSL profiles for several; minutes, only Powershell and CMD. Several minutes later "Ubuntu" shows up again, but customizations also gone, namely the starting directory, and it's no longer my default profile. I've had similar issues on my personal desktop. It's very annoying to say the least since 90% of my desktop time is in development, under the WSL environment. NOTE: I also created a custom profile for WSL, not just the detected one, and that disappears as well.
claunia commented 2026-01-31 04:06:21 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 29, 2021):

Does your error look like this by any chance? https://github.com/microsoft/terminal/issues/6160

@lhecker commented on GitHub (Jun 29, 2021): Does your error look like this by any chance? https://github.com/microsoft/terminal/issues/6160
claunia commented 2026-01-31 04:06:21 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 11, 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 (Jul 11, 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**.
claunia commented 2026-01-31 04:06:21 +00:00
Author
Owner
Copy Link

@tracker1 commented on GitHub (Sep 16, 2021):

@lhecker yes, it does, thank you... With so many issues, it's hard to find if something is a dupe via GH search...

@tracker1 commented on GitHub (Sep 16, 2021): @lhecker yes, it does, thank you... With so many issues, it's hard to find if something is a dupe via GH search...
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 Area-Settings Issue-Bug Needs-Attention Needs-Triage Product-Terminal
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#14289
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?