microsoft / microsoft/winget-cli

Strange behavior -update

Open
#5,641 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-External Command-Upgrade Issue-Bug
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Server 2022 Standard v.10.0.20348 N/A Build 20348
winget run from WinTerminal.

I try update WinTerminal:
winget update --id microsoft.windowsterminal
Found Windows Terminal [Microsoft.WindowsTerminal] Version 1.22.12111.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
This package requires the following dependencies:

  • Packages
    Microsoft.UI.Xaml.2.8 [>= 8.2306.22001.0]
    Successfully verified installer hash
    Starting package install...
    ████████████████████████████▌ 95%
    Successfully installed. Restart the application to complete the upgrade.

I restart Terminal, check version - old version.
I try found other way how restart Terminal (w/o restart Windows). Not found.

Finaly, i try update Terminal again:
winget update --id microsoft.windowsterminal
Found Windows Terminal [Microsoft.WindowsTerminal] Version 1.22.12111.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
This package requires the following dependencies:

  • Packages
    Microsoft.UI.Xaml.2.8 [>= 8.2306.22001.0]
    Successfully verified installer hash
    Starting package install...
    ██████████████████████████████ 100%
    Successfully installed

I restart Terminal, check version - NEW version.

Hmm. For success update i must use update twice?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported sequence with winget update --id microsoft.windowsterminal, restarting Windows Terminal between attempts, and compare the displayed version after each run. Trace the update and application-restart handling from the winget CLI entry point; done means a single update completes and the new Terminal version is reported after restarting the application.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.