Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Terminal Canary 1.23.3181.0 does not update #18204

Closed
vbrozik opened this issue Nov 15, 2024 · 3 comments
Closed

Windows Terminal Canary 1.23.3181.0 does not update #18204

vbrozik opened this issue Nov 15, 2024 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@vbrozik
Copy link

vbrozik commented Nov 15, 2024

Windows Terminal version

1.23.3181.0

Windows build number

10.0.22631.4317

Other Software

N/A

Steps to reproduce

In Windows Terminal Canary 1.23.3181.0 open the About pop-up. The pop-up will show that an update is available:
Image

Close the terminal and restart it.

Expected Behavior

The new running instance should be updated.

Note that it is user-unfriendly that the Terminal does not show any information about when the update will be installed and when it is ongoing.

Actual Behavior

There is still the same version, again showing "An update is available."

I tried waiting between the individual steps (to allow the terminal to update) but the result is always the same.

The older Canary versions updated fine. I think that in some cases I had to wait between the steps but because of the lacking UI feedback I have no idea when should I wait and for how long.

@vbrozik vbrozik added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 15, 2024
@vbrozik
Copy link
Author

vbrozik commented Nov 15, 2024

Later I noticed that I accidentally opened the "Quake" terminal which was in the background all the time. So after I closed all Windows Terminal windows there still was an instance running. After exiting the Quake terminal the update finished successfully.

IMHO this illustrates the weaknesses of the current UI for updates. For the beginning it would be helpful to add a button with meaning: "close all instances allowing the update to install".

@carlos-zamora
Copy link
Member

Thanks for filing! We're going to mark this as a /dup of #15132

Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants