terminal: An unexpected profile appearing in dropdown called "Default"

Environment

Windows build number: Windows 10.0.21292.0
Windows Terminal version (if applicable):1.6.10412.0

Steps to reproduce

When I tried to change the default profile, a new cmd.exe admin profile called “Default” emerged -> Screenshot 2021-02-27 201944

Expected behavior

Expected that it would change the default profile from powershell to fedora(installed using rootfs)

Actual behavior

Another new profile emerged called “Default” which I didn’t made!

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 1
  • Comments: 18 (7 by maintainers)

Most upvoted comments

Nope. We’ll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button? image That way you’ll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️

All of a sudden I got this same issue. What i had done recently -

  1. I had installed wsl and ubuntu image.
  2. I opened terminal settings and tried to set the starting directory for wsl. For some reason, it kept on resetting to the default starting directory and would not let me change it.
  3. After some time, I had no more use of wsl, so i uninstalled it. (This step might not be required, i have “alwaysShowTabs” set to false and i only use the default powershell profile, so i only noticed this issue now when i needed a different profile)

Then, i found that Terminal now showed a default profile. When i opened settings.json, i found a stray profile (note that this profile was in addition to the wsl profile) -

{
	"startingDirectory": "<dir i was trying to set for wsl>"
}

Without a “name” property, the name defaulted to Default.

It looks like some bug with the code that reads/writes from the SUI to the json file. For some reason, instead of updating a profile, it is creating a new profile with the only property that the user was trying to modify. It might also be related to some wsl handling.

What can be the possible reason for this behavior to happen? Can you please tell?

If we knew, we’d tell you! That’s what we’ve got to investigate here.

Could you share the contents of your settings.json file?

Reopening and moving to v1.9

SUI = the Settings UI

@carlos-zamora, you’ve been working on the SUI mostly, wanna take a first stab at investigating this?


Any update on this yet??

@Krrishdhaneja FYI we generally don’t check our work emails on the weekend, and largely only work M-F, 9-5. We appreciate you patience ☺️