Terminal Preview: wt -v reports non-preview version #18312

Closed
opened 2026-01-31 06:10:06 +00:00 by claunia · 3 comments
Owner

Originally created by @tbakrf on GitHub (Aug 25, 2022).

Windows Terminal version

1.15.2283.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

[This may fall under documentation vs bug]

In your Issue: Bug report you say:
You can find the version in the about dialog, or by running wt -v at the commandline.

Running "wt -v" reports the Windows Terminal version, but not the Windows Terminal Preview version. Maybe in the form you can update the command for how to report the preview version or have a separate form for Preview?

Expected Behavior

report the correct version from within a PS window within Windows Terminal Preview or see updated helper text to clarify PS command for reporting Windows Terminal Preview

Actual Behavior

just seeing text to pull non-preview version

Originally created by @tbakrf on GitHub (Aug 25, 2022). ### Windows Terminal version 1.15.2283.0 ### Windows build number 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce [This may fall under documentation vs bug] In your Issue: Bug report you say: You can find the version in the about dialog, or by running wt -v at the commandline. Running "wt -v" reports the Windows Terminal version, but not the Windows Terminal Preview version. Maybe in the form you can update the command for how to report the preview version or have a separate form for Preview? ### Expected Behavior report the correct version from within a PS window within Windows Terminal Preview or see updated helper text to clarify PS command for reporting Windows Terminal Preview ### Actual Behavior just seeing text to pull non-preview version
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Attention labels 2026-01-31 06:10:06 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Aug 25, 2022):

Which version of the app do you have the wt app execution alias set to/? That might explain #13849, actually.
image
image

Terminal Stable and Terminal Preview both use the same alias, so you can only set one at a time.

@zadjii-msft commented on GitHub (Aug 25, 2022): Which version of the app do you have the `wt` app execution alias set to/? That might explain #13849, actually. ![image](https://user-images.githubusercontent.com/18356694/186685905-7dbe858e-a9a8-4c99-9c28-82ce118d6715.png) ![image](https://user-images.githubusercontent.com/18356694/186686058-8ed70b09-814a-473e-ae1d-e2fbbb6c5d52.png) Terminal Stable and Terminal Preview both use the same alias, so you can only set one at a time.
Author
Owner

@tbakrf commented on GitHub (Aug 25, 2022):

Well that's it then! :D

All I did was install the Windows Terminal Preview after hearing about the run as admin feature - I did not go under the hood to modify any alias.

I did set Windows Terminal Preview to be my default terminal application though.
Not sure if it would help or hurt, but perhaps if you choose the "Default terminal application" to be the preview, it could guide you to update the exe alias?

@tbakrf commented on GitHub (Aug 25, 2022): Well that's it then! :D All I did was install the Windows Terminal Preview after hearing about the run as admin feature - I did not go under the hood to modify any alias. I did set Windows Terminal Preview to be my default terminal application though. Not sure if it would help or hurt, but perhaps if you choose the "Default terminal application" to be the preview, it could guide you to update the exe alias?
Author
Owner

@DHowett commented on GitHub (Aug 25, 2022):

Thanks for confirming!

Not sure if it would help or hurt, but perhaps if you choose the "Default terminal application" to be the preview, it could guide you to update the exe alias?

This is a good idea. I wonder... I don't know if there's a way for us to detect this without relying on a private API. I do know that there's no way for us to deep-link into the "app execution aliases" page in Settings ☹️

@DHowett commented on GitHub (Aug 25, 2022): Thanks for confirming! > Not sure if it would help or hurt, but perhaps if you choose the "Default terminal application" to be the preview, it could guide you to update the exe alias? This is a good idea. I wonder... I don't know if there's a way for us to detect this without relying on a private API. I _do_ know that there's no way for us to deep-link into the "app execution aliases" page in Settings ☹️
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18312