[Package Issue]: EpicGames.EpicGamesLauncher 1.3.210.0 is offered as an upgrade for Preview 0.111.0

Aperta
  • Qualcosa non va?
#470,786 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
devtools

Direzione di ricerca

Start with the EpicGames.EpicGamesLauncher 1.3.210.0 installer manifest linked in the issue and compare its UpgradeCode with the Preview uninstall registry key and per-user install location reported here. Reproduce with the listed winget upgrade --all steps; done when WinGet no longer offers the legacy version as an upgrade for the Preview installation while still detecting the legacy installation correctly.

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

Descrizione

Issue-Bug Needs-Triage
Please confirm these before moving forward
  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue

Side-By-Side installation.

Brief description of your issue

The new standalone Epic Games Launcher Preview (version 0.111.0) is incorrectly detected by WinGet as the legacy EpicGames.EpicGamesLauncher package.

My Preview installation is per-user and located at:

%LOCALAPPDATA%\Epic Games\Launcher

The legacy machine-wide installation directory does not exist:

%ProgramFiles(x86)%\Epic Games\Launcher

However, WinGet reports version 1.3.210.0 as an available upgrade for the installed Preview version 0.111.0.

A related issue (#365053) concerns the Microsoft Store version. This report concerns the standalone Preview installation.

I believe this may be an incorrect package detection or upgrade matching issue. Additional technical evidence:

The Preview installation has this uninstall registry subkey:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{D0769F44-D459-450F-B084-CAE38062C75B}

The WinGet 1.3.210.0 installer manifest contains the same GUID as its UpgradeCode.

Manifest:
https://github.com/microsoft/winget-pkgs/blob/master/manifests/e/EpicGames/EpicGamesLauncher/1.3.210.0/EpicGames.EpicGamesLauncher.installer.yaml

This may explain why WinGet incorrectly matches the Preview installation with the legacy package.

Steps to reproduce
  1. Install the new Epic Games Launcher Preview.
  2. Confirm that the installed version is 0.111.0.
  3. Confirm that the installation location is %LOCALAPPDATA%\Epic Games\Launcher.
  4. Confirm that the legacy machine-wide installation directory does not exist.
  5. Run winget upgrade --all.
  6. Observe that WinGet offers version 1.3.210.0 as an upgrade.

The upgrade was not executed because a blocking pin was applied to prevent a potentially incompatible installation.

Actual behavior

WinGet incorrectly offers the legacy Epic Games Launcher version 1.3.210.0 as an upgrade for the new Preview installation version 0.111.0.

Expected behavior

WinGet should correctly distinguish the new Epic Games Launcher Preview from the legacy MSI/WiX installation.

The legacy version 1.3.210.0 should not be offered as an upgrade for the Preview installation.

Environment
Windows: 10.0.26300.9818
WinGet: 1.29.380
PowerShell: 5.1
Architecture: x64

Epic Games Launcher:
Installed Version: 0.111.0
Publisher: Epic Games, Inc.
Install Location:
C:\Users\KAĞAN\AppData\Local\Epic Games\Launcher

Legacy installation directory:
C:\Program Files (x86)\Epic Games\Launcher
Not present.  Windows PowerShell 5.1
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> winget --info
Windows Package Manager v1.29.380
© 2026 Microsoft. All rights reserved.

Windows: Windows.Desktop v10.0.26300.9818
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.29.380.0

WinGet Directories
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads
Configuration Modules              %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
ConfigurationProcessorPath                Disabled
DefaultProxy                              Disabled
PS C:\WINDOWS\system32>
Screenshots and Logs

No response

Lingua principale
Nessun dato sulla lingua
Stelle
11.3k
Fork
12.2k
Merge medio
2h 16m
PR unite (30g)
566

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-pkgs

Tutte le issue di microsoft/winget-pkgs

Issue simili

Altre issue su DevTools

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.