microsoft / microsoft/winget-pkgs

[Package Issue]: EpicGames.EpicGamesLauncher adds desktop shortcut

Open
#235,565 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

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

Installation issue.

Brief description of your issue

There's a desktop shortcut added which is unexpected and unnecessary.
If this is not a bug could there be a command line switch added to toggle this behavior?
(This also happens for Ubisoft.Connect (will open an issue for that one based on the outcome of this one) but not for ElectronicArts.EADesktop). Also happens for Zen-Team.Zen-Browser so I created a bug here for that https://github.com/zen-browser/desktop/issues/6784 and here https://github.com/microsoft/winget-pkgs/issues/243546 and got a PR merged here to fix it https://github.com/microsoft/winget-pkgs/pull/243547

Seems to be an instance of https://github.com/microsoft/winget-cli/issues/1545 but not sure if the specific installer has a flag for it. And the antithesis of https://github.com/microsoft/winget-cli/issues/3314

Steps to reproduce

Run winget upgrade --all when there's an update available for EpicGames.EpicGamesLauncher and the installer adds a desktop shortcut.

(I suspect this is reproducible with winget install EpicGames.EpicGamesLauncher as well)

Actual behavior

A desktop shortcut is added

Expected behavior

A desktop shortcut is not added

Environment
Windows Package Manager v1.10.340
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.5487
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.25.340.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
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
DefaultProxy                              Disabled
Screenshots and Logs

No response

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 behavior with winget install EpicGames.EpicGamesLauncher or winget upgrade --all, then inspect the EpicGames.EpicGamesLauncher package manifest and the referenced winget-cli issues. Determine whether the installer exposes a shortcut-control option; done means the package no longer adds the unexpected desktop shortcut or the limitation is documented.

Written by the indexing model from the issue text.

Assessment

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.