Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[IMPROVEMENT] Do not show WinGet updates that WinGet itself cannot install (example: MSYS2)

Abierto
  • ¿Algo no está bien?
#5,597 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp
Área
desktop, devtools

Línea de trabajo

Start with the named entry points: NativeWinGetHelper.GetAvailableUpdates_UnSafe(), WinGetCliHelper.ParseAvailableUpdates(), and WinGetPkgOperationHelper; read related issue #882 and the Miniconda case in #2296. Check how WinGet distinguishes its normal upgrade table from the explicit-targeting table, then compare the two helper paths and the handling of error 0x8A150114. Done means explicit-targeting-only packages are not presented as installable normal updates, with the expected error explanation or ignore option handled consistently.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement winget
Please confirm these before moving forward.
  • I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
  • This improvement refers to an existing feature. If you want to suggest a new feature, please use this template.
  • This improvement is not a bug. If you want to report a bug, please use this template.
Describe the improvement
Summary

UniGetUI shows an update for MSYS2. The update always fails.
WinGet marks this package as "explicit upgrade only". UniGetUI does not use this mark.

What happens
  1. UniGetUI shows "MSYS2 Installer 20260611 -> 20260927" in Software Updates.
  2. I start the update. WinGet stops with this message:
    "The package cannot be upgraded using WinGet. Please use the method
    provided by the publisher for upgrading this package." (0x8A150114)
  3. I change the scope to "user" and set the install location. The update fails again.

MSYS2 updates itself with its own package manager (pacman).
WinGet cannot install this update. It does not matter which options I set.

What WinGet does

WinGet knows about this. The command winget upgrade does not show MSYS2
in the list of normal updates. WinGet shows MSYS2 in a separate list:
"The following packages have an upgrade available, but require explicit
targeting for upgrade."

What I expect

UniGetUI does the same as WinGet:

  • UniGetUI does not show these packages as normal updates.
  • Or: UniGetUI shows them with a clear note, for example
    "This package updates itself".
  • If WinGet returns 0x8A150114, UniGetUI tells the user why the update failed.
    UniGetUI then offers "Ignore updates for this package".
Workaround

I ignore updates for this package manually.

Where this happens in the code (current main)
  • NativeWinGetHelper.GetAvailableUpdates_UnSafe() adds each package that has
    IsUpdateAvailable = true. It does not check for "explicit upgrade only".
  • WinGetCliHelper.ParseAvailableUpdates() reads all tables from
    winget update. It also reads the "require explicit targeting" table
    as normal updates.
  • WinGetPkgOperationHelper handles the error code 0x8A150014.
    It does not handle 0x8A150114.

Related issues: #882 (explicit-targeting table), #2296 (same problem with Miniconda).

Environment
  • UniGetUI 2026.3.2
  • WinGet v1.29.380
  • Windows 11 Pro, build 26300
  • MSYS2 installed for the current user only
Describe how this improvement could help users

Users see an update that can never succeed. They try it, it fails, and they
do not know why. Then they try other options and it fails again.

With this improvement, UniGetUI shows only updates that WinGet can install.
For packages that update themselves (MSYS2, Miniconda, and others), users
get a clear note and know which tool to use. This saves time and avoids
confusing error messages.

Lenguaje dominante
C#
Estrellas
26.7k
Forks
955
Merge medio
16 h 22 min
PR fusionados (30 d)
97

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Devolutions/UniGetUI

Todos los issues de Devolutions/UniGetUI

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.