[Package Issue]: Flameshot.Flameshot

[Lonniebiz]

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

When upgrading Flameshot using "winget upgrade --all" or "winget upgrade Flameshot.Flameshot", WinGet installs the new version successfully but leaves the previous version registered. This results in duplicate entries in Windows Apps ("13.1.0" and "13.3.0"), and WinGet continues to report an available upgrade. This behavior has persisted for several weeks and affects every new Flameshot release.

Steps to reproduce

1. Install Flameshot:
   winget install Flameshot.Flameshot

2. When a new version is available, run:
   winget upgrade --all

3. After upgrade, open Windows Settings → Apps → Installed Apps
   or run:
   winget list | findstr Flameshot

4. Observe that both the previous and new versions remain installed, and "winget upgrade" continues to list Flameshot.

Actual behavior

• Both the old and new versions of Flameshot remain visible in "Installed Apps".
• The previous version (e.g., 13.1.0) is not removed.
• "winget upgrade" continues to report Flameshot as needing an update even after installing.
• "winget uninstall Flameshot.Flameshot" only removes the latest version, leaving the old registry entry.

Expected behavior

The upgrade process should replace the previous Flameshot installation in place so that only one version remains. After the upgrade, "winget list" should show a single Flameshot entry, and "winget upgrade" should no longer report it as needing an update.

Environment

Windows 11 Pro 23H2 (Build 26100.6899)
System Architecture: x64
Windows Package Manager (winget): v1.12.350
App Installer Package: Microsoft.DesktopAppInstaller v1.27.350.0
Source: winget
Package ID: Flameshot.Flameshot

Screenshots and Logs

[Dragon1573]

Manual validation

😕 Unable to reproduce ...

How did you previously installed v13.1.0? There're scope conflicts between v13.1.0 and v13.3.0.