microsoft / microsoft/terminal
Found multiple profiles with the same GUID in your settings file
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
### Windows Terminal version (or Windows build number)
Windows Terminal Version: 1.11.2921.0
### Other Software
PowerShell (multiple versions)
### Steps to reproduce
I have multiple versions of PowerShell installed because I need to support all versions. I do not have WSL installed.
1. I deleted all of my PowerShell profiles and uninstalled PowerShell. My setttings.json file only contained CMD and Windows PowerShell 5.1. In that state, I did not get the error
2. I installed PowerShell 7.2 via the MSI package and installed PS 7.0.8 and 7.1.5 from zip files.
3. Launched Windows Terminal. It added profiles 7.1.5 and 7.0.8. It made 7.1.5 the default profile. It didn't add 7.2, which should have been the default. It is the version that is actually registered on the system (via MSI install). In this state, the error occurs.
I have edited the json file to ensure there are not duplicates. See my settings file attached to this issue
[LocalSettings-State.zip](https://github.com/microsoft/terminal/files/7530091/LocalSettings-State.zip)
.
### Expected Behavior
_No response_
### Actual Behavior

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the attached LocalSettings-State.zip and the settings.json state described in the reproduction steps, then reproduce the profile detection with PowerShell 7.2, 7.1.5, and 7.0.8 installed. Done means Windows Terminal no longer reports duplicate GUIDs and selects the registered PowerShell 7.2 profile correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100