Latest store update 1.8.1521.0 caused problems with the installed preview Terminal #14159

Closed
opened 2026-01-31 04:02:29 +00:00 by claunia · 3 comments
Owner

Originally created by @kapsiR on GitHub (Jun 8, 2021).

Windows Terminal version (or Windows build number)

10.0.19042.0, 1.8.1521.0

Other Software

Windows Terminal Preview

Steps to reproduce

Yesterday I got a new Windows Terminal update via the store:
grafik

My wt.exe suddenly pointed to the installed preview version of Windows Terminal instead my default stable one:
I'm using the following shortcut: %LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe

Expected Behavior

When starting wt.exe, the stable Windows Terminal should launch

Actual Behavior

When starting wt.exe, the preview version of the Windows Terminal comes up
Thanks to the different icons I saw it, that the wrong version comes up.

I uninstalled Windows Terminal Preview and installed it again - the problem was gone.

Originally created by @kapsiR on GitHub (Jun 8, 2021). ### Windows Terminal version (or Windows build number) 10.0.19042.0, 1.8.1521.0 ### Other Software Windows Terminal Preview ### Steps to reproduce Yesterday I got a new Windows Terminal update via the store: ![grafik](https://user-images.githubusercontent.com/7165033/121134774-14ef1700-c834-11eb-8f6d-536b0005e995.png) My `wt.exe` suddenly pointed to the installed preview version of Windows Terminal instead my default stable one: I'm using the following shortcut: `%LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe` ### Expected Behavior When starting `wt.exe`, the stable Windows Terminal should launch ### Actual Behavior When starting `wt.exe`, the preview version of the Windows Terminal comes up Thanks to the different icons I saw it, that the wrong version comes up. I uninstalled Windows Terminal Preview and installed it again - the problem was gone.
claunia added the Resolution-Duplicate label 2026-01-31 04:02:29 +00:00
Author
Owner

@DHowett commented on GitHub (Jun 8, 2021):

This seems to be another symptom of /dup #10243. Sorry about that.

@DHowett commented on GitHub (Jun 8, 2021): This seems to be another symptom of /dup #10243. Sorry about that.
Author
Owner

@ghost commented on GitHub (Jun 8, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 8, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Author
Owner

@kapsiR commented on GitHub (Jun 8, 2021):

This seems to be another symptom of /dup #10243. Sorry about that.

Thanks for the duplicate hint.
I think it would be good to pin this information somewhere? It seems there are multiple duplicates already?

@kapsiR commented on GitHub (Jun 8, 2021): > This seems to be another symptom of /dup #10243. Sorry about that. Thanks for the duplicate hint. I think it would be good to pin this information somewhere? It seems there are multiple duplicates already?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14159