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

Terminal in Microsoft store and WinGet has different identifiers #16154

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

Originally created by @LeftTwixWand on GitHub (Dec 16, 2021).

Windows Terminal version

1.11.3471.0

Windows build number

19044.1348

Other Software

No response

Steps to reproduce

Now the terminal can be installed twice, because the terminal in Microsoft Store and WinGet has different ID.

image

Expected Behavior

I've got confused, because I had installed two different terminals.
When I'm launching the terminal from the icon - MS Store terminal starts.
But when I'm launching it from the command line, with command wt - winget terminal starts.

I really want to see one single instance of the terminal.

Actual Behavior

And what's the problem - they have different settings.

image

Originally created by @LeftTwixWand on GitHub (Dec 16, 2021). ### Windows Terminal version 1.11.3471.0 ### Windows build number 19044.1348 ### Other Software _No response_ ### Steps to reproduce Now the terminal can be installed twice, because the terminal in Microsoft Store and WinGet has different ID. ![image](https://user-images.githubusercontent.com/50652041/146368758-c3158c82-0712-44fd-ac13-0c3a86247847.png) ### Expected Behavior I've got confused, because I had installed two different terminals. When I'm launching the terminal from the icon - MS Store terminal starts. But when I'm launching it from the command line, with command `wt` - winget terminal starts. I really want to see one single instance of the terminal. ### Actual Behavior And what's the problem - they have different settings. ![image](https://user-images.githubusercontent.com/50652041/146369253-3e4162a8-95a9-44a5-a3ab-ee70a28c1fb7.png)
claunia added the Resolution-Duplicate label 2026-01-31 04:59:08 +00:00
claunia commented 2026-01-31 04:59:09 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 16, 2021):

This is a WinGet issue -- it is not able to merge the two entries even though they do actually point to the same thing.

The Microsoft.WindowsTerminal moniker from the winget source installs the store package. The store ID 9N0... installs the same package.

This is not the source of your two different copies of Terminal...
are you using Scoop or some other third-party package manager?

If your "two" copies of Terminal both live under \Program Files\WindowsApps, you are probably seeing #9452.

@DHowett commented on GitHub (Dec 16, 2021): This is a WinGet issue -- it is not able to merge the two entries even though they do actually point to the same thing. The `Microsoft.WindowsTerminal` moniker from the `winget` source installs the store package. The store ID `9N0...` installs the same package. This is not the source of your two different copies of Terminal... are you using Scoop or some other third-party package manager? If your "two" copies of Terminal both live under `\Program Files\WindowsApps`, you are probably seeing #9452.
claunia commented 2026-01-31 04:59:09 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Dec 17, 2021):

@DHowett when using winget install --source=winget the package URL points to your GitHub releases:

Installer:
  Type: Msix
  Download Url: https://github.com/microsoft/terminal/releases/download/v1.11.3471.0/Microsoft.WindowsTerminal_1.11.3471.0_8wekyb3d8bbwe.msixbundle

When installing from the store is the URL the same as above? winget show 'Windows Terminal' --source=msstore won't reveal the download link. Thx!

@elsaco commented on GitHub (Dec 17, 2021): @DHowett when using `winget install --source=winget` the package URL points to your GitHub releases: ``` Installer: Type: Msix Download Url: https://github.com/microsoft/terminal/releases/download/v1.11.3471.0/Microsoft.WindowsTerminal_1.11.3471.0_8wekyb3d8bbwe.msixbundle ``` When installing from the store is the URL the same as above? `winget show 'Windows Terminal' --source=msstore` won't reveal the download link. Thx!
claunia commented 2026-01-31 04:59:10 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 17, 2021):

Effectively.

That msixbundle is the package we download from the store after uploading it for distribution!

When they're installed on the system, they are registered through the same mechanism. The system treats them identically.

@DHowett commented on GitHub (Dec 17, 2021): Effectively. That msixbundle is the package we *download* from the store after uploading it for distribution! When they're installed on the system, they are registered through the same mechanism. The system treats them identically.
claunia commented 2026-01-31 04:59:10 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 21, 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 (Dec 21, 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:59:10 +00:00
Author
Owner
Copy Link

@LeftTwixWand commented on GitHub (Dec 21, 2021):

This screenshot shows, that there are two absolutely different Terminals exist.
image

The first one stores its state in
AppData\Local\Microsoft
And another one - like all the other apps from Microsoft Store in the Packages folder.
AppData\Local\Packages

When I'm running the Terminal from the Start Menu - it runs the terminal from the Packages folder, like downloaded from the Microsoft Store:
image
image
And the setting file loaded from the Packages\LocalState folder.
image

But then I'm running the terminal through the command:
image
It opens absolutely other terminal with my custom configuration:
image
And the setting file had been read from the Local\Microsoft\Windows Terminal Folder
image

@LeftTwixWand commented on GitHub (Dec 21, 2021): This screenshot shows, that there are two absolutely different Terminals exist. ![image](https://user-images.githubusercontent.com/50652041/146369253-3e4162a8-95a9-44a5-a3ab-ee70a28c1fb7.png) The first one stores its state in `AppData\Local\Microsoft` And another one - like all the other apps from Microsoft Store in the Packages folder. `AppData\Local\Packages` When I'm running the Terminal from the Start Menu - it runs the terminal from the Packages folder, like downloaded from the Microsoft Store: ![image](https://user-images.githubusercontent.com/50652041/146896776-5c81c250-34fa-42f2-b51a-099b9cdc0bfb.png) ![image](https://user-images.githubusercontent.com/50652041/146896506-3ec3420d-abd3-4dfd-bb4b-ce46bdffa9f1.png) And the setting file loaded from the `Packages\LocalState` folder. ![image](https://user-images.githubusercontent.com/50652041/146897087-37185b4d-c4ff-4c8b-8d7d-51639488fa58.png) But then I'm running the terminal through the command: ![image](https://user-images.githubusercontent.com/50652041/146897209-ef311041-592e-411f-ae62-0174b70a6c5a.png) It opens absolutely other terminal with my custom configuration: ![image](https://user-images.githubusercontent.com/50652041/146897323-b33050f1-a6e1-4321-8ab3-9029d0788453.png) And the setting file had been read from the `Local\Microsoft\Windows Terminal` Folder ![image](https://user-images.githubusercontent.com/50652041/146897573-0192bfa1-0a5c-4fe9-a6cd-ae069fa9bc33.png)
claunia commented 2026-01-31 04:59:10 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 6, 2022):

Can you please report the actual path to WindowsTerminal.exe when you're in this state? You can get it by running, from PowerShell:

Get-Process WindowsTerminal | Select -Expand Path

As I mentioned in https://github.com/microsoft/terminal/issues/11960#issuecomment-996178368:

If your "two" copies of Terminal both live under \Program Files\WindowsApps, you are probably seeing #9452.

If you have two copies running, and you run that command, and they both point to the same EXE: go read #9452.

I promise you that WinGet and the Microsoft Store install identical bits on your computer. 😄

@DHowett commented on GitHub (Jan 6, 2022): Can you please report the _actual path to WindowsTerminal.exe_ when you're in this state? You can get it by running, from PowerShell: ```powershell Get-Process WindowsTerminal | Select -Expand Path ``` As I mentioned in https://github.com/microsoft/terminal/issues/11960#issuecomment-996178368: > If your "two" copies of Terminal both live under \Program Files\WindowsApps, you are probably seeing #9452. If you have two copies running, and you run that command, _and they both point to the same EXE_: go read #9452. I promise you that WinGet and the Microsoft Store install identical bits on your computer. :smile:
claunia commented 2026-01-31 04:59:10 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 11, 2022):

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 (Jan 11, 2022): 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:59:10 +00:00
Author
Owner
Copy Link

@LeftTwixWand commented on GitHub (Jan 11, 2022):

I've run the terminals from the Start menu and through the wt command.
The running processes are the same. But they have different styles....

image

@LeftTwixWand commented on GitHub (Jan 11, 2022): I've run the terminals from the Start menu and through the `wt` command. The running processes are the same. But they have different styles.... ![image](https://user-images.githubusercontent.com/50652041/148977350-06c9605b-ef16-43d6-978c-e49ef75879a6.png)
claunia commented 2026-01-31 04:59:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 11, 2022):

Presumably, that means they're running with different identities. I'd reckon that the one run via wt.exe is running packaged, and the Start Menu one is unpackaged. You should be able to confirm this by opening the About dialog.

@zadjii-msft commented on GitHub (Jan 11, 2022): Presumably, that means they're running with different identities. I'd reckon that the one run via `wt.exe` is running packaged, and the Start Menu one is unpackaged. You should be able to confirm this by opening the About dialog.
claunia commented 2026-01-31 04:59:11 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 11, 2022):

Thanks for the report! This is a clear case of /dup #9452, as mentioned before. Please follow the remediation steps in #9452. Again, that's #9452.

@DHowett commented on GitHub (Jan 11, 2022): Thanks for the report! This is a clear case of /dup #9452, as mentioned before. Please follow the remediation steps in #9452. Again, that's #9452.
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 Resolution-Duplicate
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#16154
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?