microsoft / microsoft/winget-pkgs

[Package Issue]: Greenshot.Greenshot Upgrade not working

Open
#299,930 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

### Please confirm these before moving forward

- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] 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

Upgrading Greenshot.Greenshot from 1.3.300 to 1.3.301 doesn't work, logs describe the issue perfectly

### Steps to reproduce

```
winget install greenshot.greenshot
# wait for new release
winget upgrade --all
```

### Actual behavior

installation failed with exitcode: 1

### Expected behavior

Upgrade succeeding

### Environment

```raw
Windows-Paket-Manager v1.11.430
Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

Windows: Windows.Desktop v10.0.26100.6584
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.26.430.0
```

### Screenshots and Logs

```
2025-10-01 10:25:03.218 Defaulting to Cancel for suppressed message box (OK/Cancel):
Das Setup hat entdeckt, dass Greenshot zurzeit ausgeführt wird.

Bitte schließen Sie jetzt alle laufenden Instanzen und klicken Sie auf "OK", um fortzufahren, oder auf "Abbrechen", um zu beenden.
2025-10-01 10:25:03.218 Got EAbort exception.
```
This is German for: "the application is currently running, please close all instances and click "ok" to continue.

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

Start by reproducing the upgrade with `winget install greenshot.greenshot` followed by `winget upgrade --all`, using the Windows Package Manager environment described in the issue. Review the installer log showing Greenshot is still running and determine the package or upgrade behavior involved; done means upgrading from 1.3.300 to 1.3.301 completes successfully.

Written by the indexing model from the issue text.

Assessment

Domain
operating-systems, release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.