#1472 Win7 x64 - "An instance of Greenshot is already running" after fresh install

1.0.6
open
nobody
win7 x64 (1)
none
5
2014-03-03
2013-03-06
Brian Pothier
No

Win7 x64 (64-bit)
Greenshot 1.0.6
Re-open support-request #47 - https://sourceforge.net/p/greenshot/support-requests/47/

After install of Greenshot 1.0.6 on Win7 x64, it refuses to start with error:

---------------------------
Error
---------------------------
An instance of Greenshot is already running.
1: C:\Program Files\Greenshot\Greenshot.exe

There is no previous installation, and no previous process running.
Selecting OK terminates Greenshot leaving no process running (confirmed in taskmanager).
Running Greenshot again produces same error dialog.
Uninstall and re-install does not resolve issue.

Workaround proposed in discussion thread https://sourceforge.net/p/greenshot/discussion/676082/thread/bd80547a#e932 by Joseph Ridenhour works:

In C:\Program Files\Greenshot
delete or rename file:  Greenshot.exe.config

Greenshot will then start normally - but will not recreate "Greenshot.exe.config" file. (I suspect this file is not required?)
I have not (yet) tried any of the 1.1 beta builds to see if they have the same issue.

Another user (https://sourceforge.net/p/greenshot/support-requests/47/#cda1) mentioned 0.8.1.x did not have this issue, though I believe 0.x was not officially 64-bit...
Brian

Discussion

  • Brian Pothier
    Brian Pothier
    2013-03-07

    Uninstalled 1.0.6.2228
    Installed 1.1.0.2515 using installer and it started with no error.
    Uninstalled 1.1.0.2515
    Installed 1.0.6.2228 and it again had instance already running error.

    It appears that the issue is fixed in at least the 1.1.0.2515 build...
    The immediate difference I see is that the 1.0.6.2228 build's Greenshot.exe.config contains:
    supportedRuntime version="v4.0" sku="client"
    But the 1.1.0.2515 contains:
    supportedRuntime version="v4.0"
    Unfortunately, editing the 1.06 config or even copying in the 1.1.0 config file, does not resolve the already running error.

    Hope this helps,
    Brian

     
  • Robin Krom
    Robin Krom
    2013-03-07

    Thanks Brian!

    I don't know what could cause the "double" starting issues, but I do know that I cleaned up some issues. I'll check if I can find something, as I am curious, but I'm glad the issue is gone with 2515.

    Best wishes,
    Robin

     
  • Brian Pothier
    Brian Pothier
    2013-03-08

    Just to be clear, this is not a "double" starting issue -- e.g. those that have a similar error box with a "1: C:..." and a "2: C:...". This issue only lists a single "already running" instance.
    Just tried on another Win7 x64 (but with Home Prem) and 1.0.6 installed & started correctly. It did prompt for language selection on first run(of greenshot.exe), which I had not seen before(the setup.exe always started with selecting install language).
    The other win7 x64 I had issues with was Win7 x64 Corp version (and likely lots of other differences).
    Brian

     
  • Ok, so the problem came up again after uninstalling, re-installing with the latest. I edited the Greenshot.exe.config rather blindly, and updated the following:

    • <?xml version="1.0" encoding="utf-8" ?>

    To:

    • <?xml version="2.0" encoding="utf-8" ?>

    Strangely enough, I can repeat this issue by editing back to 1.0, problem goes away when I edit it to 2.0 again.

     
    Last edit: Joseph Ridenhour 2013-03-26
  • Robin Krom
    Robin Krom
    2013-03-26

    Hi Joseph,

    What is the latest version for you? I guess that by changing the .config xml version to 2.0 you make it invalid, renaming the file to something else might also work.

    I'm still confused why this problem occurs in the first place.

    Best wishes,
    Robin

     
  • Robin Krom
    Robin Krom
    2013-03-26

    I just want to make sure we are not chasing ghosts... You don't have an entry to the application in the windows startup? Or do you use citrix, or anything like that?

    Does this happen with every reboot? What happens if you start Greenshot manually?

     
  • Brian Pothier
    Brian Pothier
    2013-03-27

    Robin,
    For my testing (I'm using the UNSTABLE releases successfully now) of 1.0.6, it was a fresh/first install directly on a local machine.
    The issue happened when GS tried to start at the end of installer and also when I manually ran it from start menu. I don't recall if I tried rebooting... I did uninstall and re-install.

     
  • Robin Krom
    Robin Krom
    2013-10-30

    Hi Brian,

    we just release 1.1.6, wanted to know if everything works?

    Best wishes,
    Robin

     
  • Brian Pothier
    Brian Pothier
    2013-10-31

    I just uninstalled my 1.1.5 UNSTABLE version and successfully re-installed 1.0.6 without the issue I had been experiencing previously. I then uninstalled 1.0.6 and installed the new 1.1.6.2779 also successfully.
    Not sure what changed on my system since March, but the old version started working as well... but no issue with 1.1.6 build, so can likely close this bug.
    Thank you for a great project!
    Brian