[GH-ISSUE #833] Updating the app maintains the previous version entry in windows "Programs and Features" #657

Closed
opened 2026-02-26 09:32:12 +03:00 by kerem · 6 comments
Owner

Originally created by @darkred on GitHub (Apr 21, 2021).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/833

I had ScreenToGif 2.28.0 installed via ScreenToGif.2.28.Setup.msi installed in win10 x64 20h2.

Today, I wanted to update to the new version, 2.28.1 .
So I tried:

  • downloading ScreenToGif.2.28.1.Setup and running it,
  • (uninstalling+reinstalling 2.28.0 and) updating via the program itself,

and in both cases,
in windows "Programs and Features": the old 2.28.0 entry remained and an additional 2.28.1 created:
2021-04-21_183441

This shouldn't occur because the updated program still has the same ScreenToGif directory:
2021-04-21_183611

Thank you

Originally created by @darkred on GitHub (Apr 21, 2021). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/833 I had ScreenToGif 2.28.0 installed via `ScreenToGif.2.28.Setup.msi` installed in win10 x64 20h2. Today, I wanted to update to the new version, 2.28.1 . So I tried: - downloading `ScreenToGif.2.28.1.Setup` and running it, - (uninstalling+reinstalling 2.28.0 and) updating via the program itself, and in both cases, in windows "Programs and Features": the old `2.28.0` entry remained and an additional `2.28.1` created: ![2021-04-21_183441](https://user-images.githubusercontent.com/723651/115582017-353d3380-a2d1-11eb-8eab-955d72b79931.jpg) This shouldn't occur because the updated program still has the same `ScreenToGif` directory: ![2021-04-21_183611](https://user-images.githubusercontent.com/723651/115581750-f7d8a600-a2d0-11eb-89ae-b4742789ecbe.jpg) Thank you
kerem 2026-02-26 09:32:12 +03:00
Author
Owner

@NickeManarin commented on GitHub (Apr 21, 2021):

Did you install with the option to "all users" ticked or not?

<!-- gh-comment-id:824425389 --> @NickeManarin commented on GitHub (Apr 21, 2021): Did you install with the option to "all users" ticked or not?
Author
Owner

@darkred commented on GitHub (Apr 22, 2021):

There's only one local account in my Windows 10 installation, Administrator [screenshot]

And, during ScreenToGif install/update,
the only option related to "all users" was Add the shortcut to all users, and yes, it was ticked (already, by default) :

screenshots

2021-04-22_111840
2021-04-22_112000

<!-- gh-comment-id:824647139 --> @darkred commented on GitHub (Apr 22, 2021): There's only one local account in my Windows 10 installation, `Administrator` [[screenshot](https://user-images.githubusercontent.com/723651/115681444-3451e380-a35d-11eb-8501-c91e8c5e1732.jpg)] And, during ScreenToGif install/update, the only option related to "all users" was `Add the shortcut to all users`, and yes, it was ticked (already, by default) : <details> <summary>screenshots</summary> ![2021-04-22_111840](https://user-images.githubusercontent.com/723651/115681028-cd342f00-a35c-11eb-877f-f6ed6f69d604.jpg) ![2021-04-22_112000](https://user-images.githubusercontent.com/723651/115681045-d02f1f80-a35c-11eb-9182-311340e884d9.jpg) </details>
Author
Owner

@NickeManarin commented on GitHub (Apr 23, 2021):

Ok, this issue is related to a flag (ALLUSERS) used in the installer.
When the option to install the app to all users is ticked and later in an update is not ticked, it is treated as another separated app.
So it creates another entry in the App list.

One way to go would be to run a custom action removing the current version before installing it on top.

<!-- gh-comment-id:825359872 --> @NickeManarin commented on GitHub (Apr 23, 2021): Ok, this issue is related to a flag (ALLUSERS) used in the installer. When the option to install the app to all users is ticked and later in an update is not ticked, it is treated as another separated app. So it creates another entry in the App list. One way to go would be to run a custom action removing the current version before installing it on top.
Author
Owner

@NickeManarin commented on GitHub (May 23, 2021):

I'm going to close this issue because I'm tracking it via #721.

I have a working solution (it will be ready for v2.30.1) for stopping this issue, but you'll need to uninstall the broken version before installing the new version.

<!-- gh-comment-id:846618896 --> @NickeManarin commented on GitHub (May 23, 2021): I'm going to close this issue because I'm tracking it via #721. I have a working solution (it will be ready for v2.30.1) for stopping this issue, but you'll need to uninstall the broken version before installing the new version.
Author
Owner

@NickeManarin commented on GitHub (May 25, 2021):

I managed to make it work, you don't need to uninstall manually the previous version.
The installer detects that a previous version was installed on the same folder, but with a different access mode (per-user / per-machine) and it uninstalls before installing the new version.

<!-- gh-comment-id:847453229 --> @NickeManarin commented on GitHub (May 25, 2021): I managed to make it work, you don't need to uninstall manually the previous version. The installer detects that a previous version was installed on the same folder, but with a different access mode (per-user / per-machine) and it uninstalls before installing the new version.
Author
Owner

@darkred commented on GitHub (May 27, 2021):

Thank you for fixing this.

<!-- gh-comment-id:849576873 --> @darkred commented on GitHub (May 27, 2021): Thank you for fixing this.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ScreenToGif#657
No description provided.