Administrator Protection: machine-scope installs are not matched across the user and the elevated account

Aperta
#6,688 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
49/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp
Ambito
backend, cli

Direzione di ricerca

Start by tracing how winget list and winget upgrade match installed packages to catalog entries across the normal and elevated account profiles; the issue names no source files or tests. Compare the matching behavior for machine-wide installers with the unaffected portable package. Done means machine-wide packages are matched consistently from both accounts and can be upgraded from either.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Command-List Command-Upgrade Issue-Bug Needs-Triage
Relevant area(s)

WinGet CLI

Relevant command(s)

winget list, winget upgrade

Brief description of your issue

With Administrator Protection on, an elevated winget runs as the separate account ADMIN_, with its own profile and so its own tracking catalog. A machine-wide package installed from one account is matched to its winget package only in that account. The other account lists it as an unmatched ARP entry, and its winget upgrade never offers the update. My scheduled upgrade runs elevated, so Ruby 3.4 stayed on an old version for weeks.

Steps to reproduce
  1. Turn on Administrator Protection (TypeOfAdminApprovalMode = 2).
  2. Install a machine-wide package from a normal terminal, for example winget install --id RubyInstallerTeam.Ruby.3.4 (the installer elevates itself).
  3. Run winget list in a normal terminal and in an elevated terminal, and compare.
  4. When a newer version is published, run winget upgrade in both.
Expected behavior

A machine-wide package is matched the same way from both accounts, so either one can upgrade it.

Actual behavior

Normal terminal:

Ruby 3.4                                  RubyInstallerTeam.Ruby.3.4        3.4.12-1-arm    winget
Windows Software Development Kit - ...    Microsoft.WindowsSDK.10.0.26100   > 10.0.26100.7705 winget

Elevated terminal:

Ruby 3.4                                  ARP\Machine\X86\RubyInstaller-3.4-aarch64-mingw-ucrt_is1  3.4.12-1-arm
Windows Software Development Kit - ...    ARP\Machine\X86\{45e335f3-c807-43b8-9ed1-43666cfcf939}    10.1.26100.9457

Before I updated it by hand, the normal winget upgrade listed Ruby 3.4.11-1 -> 3.4.12-1, while the elevated one reported "No installed package found" for it. A portable package is not affected: zoxide installed from the elevated account showed up as winget-matched in the normal account too.

Environment
Windows Package Manager v1.29.380
Windows: Windows.Desktop v10.0.26300.9974
System Architecture: Arm64
Package: Microsoft.DesktopAppInstaller v1.29.380.0
Administrator Protection: on (TypeOfAdminApprovalMode = 2)
Lingua principale
C++
Stelle
26.6k
Fork
1.8k
Merge medio
3g 10h
PR unite (30g)
41

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/winget-cli

Tutte le issue di microsoft/winget-cli

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.