starred/ScreenToGif

Fork 0

mirror of https://github.com/NickeManarin/ScreenToGif.git synced 2026-04-25 15:15:51 +03:00

[GH-ISSUE #1349] [Bug] Recursive Startup #993

New issue

Open

opened 2026-02-26 09:33:14 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 09:33:14 +03:00

Owner

Originally created by @MrMendelli on GitHub (Nov 6, 2024).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1349

Originally assigned to: @NickeManarin on GitHub.

Upon starting with my current settings, the program spawns multiple infinite subprocesses of its self.

I have tested with and without my preferences. I can recreate my settings but this issue may be present for other users. I hypothesized it may be from having portable mode with updating enabled but setting the PortableUpdate to False did not change the behavior. Cause is inconclusive.

I have update checks enabled, normally an update is automatically downloaded and opened in my archival software when finished, or the program opens to the main window if no updates are found.

OS: Windows 10 x64
ScreenToGif: v2.41.1 (issue has happened in older versions)

Attached is my current configuration file.

Originally created by @MrMendelli on GitHub (Nov 6, 2024). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1349 Originally assigned to: @NickeManarin on GitHub. Upon starting with my current settings, the program spawns multiple infinite subprocesses of its self. I have tested with and without my preferences. I can recreate my settings but this issue may be present for other users. I hypothesized it may be from having portable mode with updating enabled but setting the `PortableUpdate` to `False` did not change the behavior. Cause is inconclusive. I have update checks enabled, normally an update is automatically downloaded and opened in my archival software when finished, or the program opens to the main window if no updates are found. ![image](https://github.com/user-attachments/assets/e874d7ac-193a-4f86-ac93-bb8f84f9a118) - OS: Windows 10 x64 - ScreenToGif: v2.41.1 _(issue has happened in older versions)_ [Attached is my current configuration file.](https://github.com/user-attachments/files/17641891/Settings.zip)

kerem added the

🔷 Bug 🐛

⬜ Pending

labels

2026-02-26 09:33:14 +03:00

kerem commented

2026-02-26 09:33:14 +03:00

Author

Owner

@pawlos commented on GitHub (Nov 6, 2024):

Based on the --shimgen-noop parameter and this doc looks like it's related to ScreenToGif being install via Chocolatey.

@pawlos commented on GitHub (Nov 6, 2024): Based on the `--shimgen-noop` parameter and [this doc](https://docs.chocolatey.org/en-us/features/shim/#options-and-switches) looks like it's related to ScreenToGif being install via Chocolatey.

kerem commented

2026-02-26 09:33:14 +03:00

Author

Owner

@NickeManarin commented on GitHub (Nov 11, 2024):

Could be due to the app being installed on the root of C:/
The app tries to detect if it was installed with Chocolatey before trying to check for updates.
If so, it doesn't do the check.
The temporary solution is to disable update checks and let the update be done via Chocolatey.

@NickeManarin commented on GitHub (Nov 11, 2024): Could be due to the app being installed on the root of C:/ The app tries to detect if it was installed with Chocolatey before trying to check for updates. If so, it doesn't do the check. The temporary solution is to disable update checks and let the update be done via Chocolatey.

kerem commented

2026-02-26 09:33:14 +03:00

Author

Owner

@pryrt commented on GitHub (Oct 14, 2025):

It would be nice if this bug were fixed.

Mine is installed in c:\usr\local\bin, extracted from the portable, not installed using Chocolatey.

If Options > Application > Allow only a single instance is chosen, then it will run two instances (one with --shimgen-noop and one without), but if Allow multiple instances is chosen, then it will do the infinite loop as shown above.

I did confirm that if I disable update checks, the problem goes away. But since I don't use Chocolatey, suggesting that "let the update be done via Chocolatey" is not a viable solution. (And essentially, I am now in the state that I won't know when there's an update to ScreenToGif... Fortunately, now, at least, GitHub will notify me when this Issue is closed, so I at least know to come look to see if a new version fixes it.)

@pryrt commented on GitHub (Oct 14, 2025): It would be nice if this bug were fixed. Mine is installed in `c:\usr\local\bin`, extracted from the portable, _not_ installed using Chocolatey. If **Options > Application > Allow only a single instance** is chosen, then it will run two instances (one with `--shimgen-noop` and one without), but if **Allow multiple instances** is chosen, then it will do the infinite loop as shown above. I did confirm that if I disable update checks, the problem goes away. But since I _don't_ use Chocolatey, suggesting that "let the update be done via Chocolatey" is not a viable solution. (And essentially, I am now in the state that I won't know when there's an update to ScreenToGif... Fortunately, now, at least, GitHub will notify me when this Issue is closed, so I at least know to come look to see if a new version fixes it.)

kerem referenced this issue

2026-03-01 19:03:10 +03:00

[GH-ISSUE #993] save error v2.34 #2827

kerem referenced this issue

2026-03-01 19:03:13 +03:00

[GH-ISSUE #993] save error v2.34 #2831

kerem referenced this issue

2026-03-01 19:03:17 +03:00

[GH-ISSUE #993] save error v2.34 #2833