An instance of Greenshot is already running

Shaul
2012-08-22
2013-03-26
  • Shaul
    Shaul
    2012-08-22

    Thank you for this excellent and useful application. I use it almost daily.  Here is a little problem:
    Whenever I start my computer I get a pop-up saying: An instance of Greenshot is already running followed by two lines:
    1: C:\Program Files\Greenshot\Greenshot.exe
    2: C:\Program Files\Greenshot\Greenshot.exe

    Please tel me how to rid of this. Thank you!

     
  • Mike
    Mike
    2012-08-22

    Check your \Run key in your regedit.  Make sure Greenshot isn't in there twice:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

    You might check your Start/All Programs/Startup to make sure Greenshot didn't get in there as well.

     
  • Robin Krom
    Robin Krom
    2012-10-28

    You might have Greenshot in your startup, and/or multiple times in the registry. This might have happened due to us switching from 32 to 64 bit and having entries in both areas of the registry.

    But what you can do is install our RC5, which we uploaded yesterday, and go into the setting, uncheck the "start at windows startup" press ok. Than go back again, and you can select it again, press ok. All doubles "should" be removed…

    Best wishes,
    Robin

     
  • Jj4ssvYg
    Jj4ssvYg
    2012-12-28

    I had the exact error in Windows 7 x64 Pro. I had to install from zip and run it in a different folder than the automatic setup method. Then I proceeded to uninstall the automatic setup installation. Avoid automatic setup install, stick with the zip.

     
  • Robin Krom
    Robin Krom
    2012-12-29

    No, please don't stick to the zip!! With 1.0.6 most installation issues should be fixed, but if someone still has a very old version the unstaller of this version might forget to remove the entry in the start-menu. You can just delete this manually and you are good. (Start->All Programs->Auto Start)

    There are some benefits of the installer, first it checks pre-requisites and it makes it possible to start Greenshot when starting your PC. Additionally we will register file types with 1.1 (we have our own) and it will optimize the performance of Greenshot. Besides the .zip can cause a lot of problems when people don't know what they are doing… e.g. copy Plugins from a different version.

     
  • Byron
    Byron
    2013-01-22

    I have experienced the same issue with Greenshot and found a solution to the error message:

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

    Solution:
    Right-Click on the Greenshot.exe (found in the Start Menu/All Programs).
    Click on 'Properties' and Click on the 'Compatibility' tab.
    Under 'Compatibility Mode' select 'Run this program in compativility mode for:'.
    Click on the drop-down menu and select 'Windows Vista (Service Pack 2).
    Click 'OK'.

    I hope this helps!

     
    Last edit: Byron 2013-01-22
  • I tried all the above but nothing worked. In the end I deleted Greenshot.exe.config from C:\Program Files\Greenshot. Now I can run the 64 bit executable without issue.

     
  • Robin Krom
    Robin Krom
    2013-03-06

    Hi Joseph, I don't understand why deleting that file helped... Can you tell us how you came to that solution?

    Also I wonder if this problem has anything to do with the .NET version(s) that are available, can someone who has this problem tell me what is installed on his system?

    Best wishes,
    Robin

     
  • This issue came up again in Win 7 x64, so my previous post isn't the answer. No running processes, no startup item for Greenshot in either the startup folder or msconfig, and the Greenshot.exe.config is gone as my previous post noted. I couldn't find Greenshot in the 'Add and Remove Programs' dialogue, which was strange. Ran unins000 manually from the install folder. Going to try the latest version.

     
  • 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