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

Aberta
#6,688 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
49/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
cpp
Domínio
backend, cli

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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)
Linguagem predominante
C++
Estrelas
26.6k
Forks
1.8k
Merge médio
3d 10h
PRs com merge (30d)
41

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/winget-cli

Todas as issues de microsoft/winget-cli

Issues semelhantes

Mais issues de C++

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.