It would be nice if greenshot was able to recover unsaved work after a crash
Description
Environment
Window 7, 64 bit
My About Greenshot say 1.1.9 Build 13 but I am not allowed to select such a version
Gliffy Diagrams
Activity
V_S December 5, 2022 at 3:00 AM
I use this type of feature all the time in Notepad++ to avoid losing work.
It saves open and unsaved work so if I need to reboot or the system crashes, I don’t lose things or have to scurry through and do a lot of extra work before getting back to the work I’m already having to do and losing my work-flow on an ever-increasing pile of things I have to do.
I can’t tell you how many times I’ve rebooted for an update and then remembered I had a few screenshots I didn’t finish correlating, saving to a customer folder, an error folder, a how-to I was working on, etc., or just a random power outage that lasted longer than the UPS can handle (set to power off) and lost all the Greenshot screenshots.
Are there workarounds, sure, but also things that require extra work and breaks in other workflows.
It would be nice if the software just handled it.

Serafeimg April 30, 2022 at 5:36 PM(edited)
I also find this feature suggestion really interesting and helpful.
Until a developer can get into the code, I have found the following workaround for Windows.
It consists of two steps. The first is to make Greenshot autosave our shots, the time you take them. The second is to schedule Windows to clean old shots.
A. Enable autosave in Greenshot:
Go to preferences:
In the tab “Output”: set your preferred “Storage location”, e.g.: C:\Program Files\Greenshot\Temp_shots
In the tab “Destination“: activate the option “Save directly“
B. Schedule Windows to clean old files:
Open Task Scheduler
Go to “Task Scheduler Library“
From the right panel, select “Create Task“
In the tab “General”:
1. Set name, e.g.: Delete old greenshot files
2. In the “Security options“, select “Run whether the user is logged on or not“
3. Activate the option “Run with highest privileges“
4. In the drop-down menu of the “Configure for“ field, select the current version of your OS.
Notes:
a. I had to choose options 2 and 3 to avoid console pop-ups when the task was executed. You can first try with the regular option, “Run only when user is logged on“ and see if you have the same issue.
b. Regarding option 4 I am not sure if you really need to change the default option. I did so because I saw some strange log results while I was testing, although the task was executed successfully.In the tab “Triggers”, choose New:
1. Begin the task: I chose “On a schedule“
2. In the settings area, I chose Daily at 11:00 AM and recur every 1 day
3. In the “Advanced settings“ area, make sure that the option “Enabled” is activatedIn the tab “Actions”, choose New:
1. Action: Select a program
2. Program/script: C:\Windows\System32\ForFiles.exe
3. Add argument: /p "C:\Program Files\Greenshot\Temp_shots" /s /d -7 /c "cmd /c del @file"
Notes:
a. The path after the /p argument is “Storage location” you have set on step A (Enable autosave in Greenshot)
b. The number after the /d argument indicates how many days you want to keep those temp files. For example, -7 means that the files will be deleted after 7 days
c. The files are permanently deleted and not moved to the recycle bin
d. The days are calendar days, no matter the time of the shotIn the tab “Conditions”:
Personally, I disabled the option “Start the task only if the computer is on AC power“. We expect negligible power consumption for this task, I haven’t run into massive testing through different scenarios.In the tab “Settings”:
I have activated the option “Run task as soon as possible after a scheduled start is missed“. This option is important if you don’t turn on your notebook every day. I also activated the option “If the task fails, restart every“ with the default values of 1 minute and 3 times. I believe the task is light enough to not cause any unwanted traffic by activating this option.In the tab “History”, you can see the task’s logs. They are useful for troubleshooting in case the task fails. You can activate the logging through the right panel of the Task Scheduler and the option “Enable All Task History“. If the instructions work for you, I suggest keeping the history deactivated.
That’s it! I hope you find this guide helpful
I wish you all happy and backed up greenshoting and looking forward to your comments.
I imagine saving unsaved file in the backgroud to a location where they ca be loaded from next time green shot is started