[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

Flameshot was originally installed system-wide using the following command:

winget install flameshot --scope=machine -e --source winget

When upgrading Flameshot using "winget upgrade --all" or "winget upgrade Flameshot.Flameshot", WinGet does not install the new version at all. The existing version remains, and WinGet continues to report an available update.

Only when using a forced install ("winget install Flameshot.Flameshot --force") does the newer version install — but the older version remains registered, resulting in duplicate Flameshot entries in Windows Apps (for example, 13.1.0 and 13.3.0).

Further testing confirmed that the manifest for 13.3.0 does not include a machine-scope installer entry, which causes WinGet to fall back to the older 13.1.0 build when installing with --scope=machine.

This behavior has persisted for several weeks and affects each new Flameshot release.

Steps to reproduce

1. Install Flameshot system-wide:

   winget install flameshot --scope=machine -e --source winget

2. When a new version is available, run:

   winget upgrade --all

3. Observe that:

   • The new version is not installed.
   • "winget upgrade" still lists Flameshot as needing an update.

4. Then run:

   winget install Flameshot.Flameshot --force

5. Observe that:

   • The new version installs successfully.
   • The old version remains registered, creating two installed entries (e.g., 13.1.0 and 13.3.0).
     Windows 11 > Settings > Apps > Installed apps shows both versions are installed:
     

6. Attempting to reinstall system-wide:

   winget install flameshot --scope=machine -e --source winget

   results in 13.1.0 being installed again instead of 13.3.0, confirming the missing machine-scope installer in the latest manifest.

Actual behavior

• "winget upgrade" alone does not install the new Flameshot version.
• WinGet continues to indicate an available update even after running the upgrade command.
• Using "--force" installs the new version but leaves the previous version registered, resulting in duplicates.
• The 13.3.0 manifest appears to lack a machine-scope installer entry, so any system-wide install defaults back to 13.1.0.
• Administrators cannot currently upgrade Flameshot for all users of a workstation using WinGet.

Expected behavior

• "winget upgrade --all" (or "winget upgrade Flameshot.Flameshot") should correctly detect and upgrade machine-scope installations when a new version is available.
• The latest manifest should include a valid machine-scope installer so administrators can deploy upgrades system-wide.
• After the manifest is corrected, I assume winget upgrade --all will upgrade Flameshot normally for all users of the workstation, as expected.

Current Workaround / Resolution

For now, I’m leaving version 13.1.0 installed and ignoring the 13.3.0 update until a machine-scope installer is added to the manifest.
This ensures Flameshot remains available to all users without creating duplicate or per-user installs.

Environment

Windows 10 Pro 24H2 (Build 26100.1)
System Architecture: x64
Windows Package Manager (winget): v1.12.350
App Installer Package: Microsoft.DesktopAppInstaller v1.27.350.0
Package ID: Flameshot.Flameshot
Installed Versions: 13.1.0 (current), 13.3.0 (update available)
Install Scope: Machine

[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.

[Lonniebiz]

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.

@Dragon1573: The original install command was exactly this:
winget install flameshot --scope=machine -e --source winget

Note: I edited my original post to reflect this detail, and a few other elaborations.

[Lonniebiz]

Additional Findings (Updated)

After further testing, I confirmed that when installing per-machine, WinGet installs an older version of Flameshot and cannot apply the latest update.

winget uninstall flameshot
winget install flameshot --scope=machine -e --source winget

Results:

• WinGet installs version 13.1.0, not the latest 13.3.0.
• Running winget upgrade --all then reports that an update to 13.3.0 is available.
• Running winget install flameshot --scope=machine -e --source winget again produces:

  Found an existing package already installed. Trying to upgrade the installed package...
  No applicable upgrade found.
  A newer package version is available in a configured source, but it does not apply to your system or requirements.
  

• Running winget show Flameshot.Flameshot --scope=machine shows:

  Version: 13.3.0
  Installer:
    No applicable installer found; see logs for more details.
  

This confirms that the 13.3.0 manifest lacks a machine-scope installer entry, causing WinGet to fall back to the previous machine-scope version (13.1.0). As a result:

• Administrators cannot install or upgrade Flameshot system-wide to 13.3.0.
• WinGet permanently reports an upgrade as available but cannot apply it.

Why this matters

I’m an administrator attempting to install or upgrade Flameshot for all users of the workstation.
Installing without --scope=machine only installs the new version for the current user, not system-wide — which defeats the purpose of upgrading in an administrative environment.

Current Workaround / Resolution

For now, I’m leaving version 13.1.0 installed and ignoring the 13.3.0 update until a machine-scope installer is added to the manifest.
This avoids user-specific installs and ensures Flameshot remains accessible to all users on each workstation.

Once that happens, I assume winget upgrade --all will upgrade Flameshot normally for all users of the workstation, as expected.