Terminal in Microsoft store and WinGet has different identifiers

[LeftTwixWand]

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.

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.

[DHowett]

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.

[elsaco]

@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!

[DHowett]

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.

[ghost]

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.

[LeftTwixWand]

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

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:


And the setting file loaded from the Packages\LocalState folder.

But then I'm running the terminal through the command:

It opens absolutely other terminal with my custom configuration:

And the setting file had been read from the Local\Microsoft\Windows Terminal Folder

[DHowett]

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 #11960 (comment):

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. 😄

[ghost]

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.

[LeftTwixWand]

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....

[zadjii-msft]

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.

[DHowett]

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.