This isn't best-in-class, but it isn't the worst either, & as there's a chance it might prove useful on a project I'm just starting, updated my copy since it was graciously offered on GOTD today.
Reading the comments about it deactivating prior Soft Orbits giveaways I was a bit dismayed, but for the developer, not myself, as I've never had this happen. Then one of the replies to a comment caught my attention because it was clearly false -- I wanted to post accurate data rebutting that here as well as in the comments on the download page to increase the odds of people seeing it.
* * *
It was mentioned that Soft Orbits Photo Retoucher adds a LOT of registry entries -- it's most always mentioned that installing a new Soft Orbits GOTD deactivates other Soft Orbits giveaways that were already installed.
Today's GOTD uses the same registry key as the version I already had installed from last summer, though that key contains a few more values or entries: HKCU\ Software\ softorbits\ SoftOrbitsPhotoRetoucher . Today's GOTD did add a 2nd, empty key: HKCU\ Software\ softorbits\ DigitalPhotoSuite . Aside from Uninstall entries in HKLM (HKEY_LOCAL_MACHINE) that's it as far as important, permanent registry entries go. Once it's installed, running Soft Orbits Photo Retoucher added (11) files to the Internet Explorer cache for "activate" & "promos" -- no permanent registry changes were recorded.
Now when I say permanent keys, this is what I'm talking about... Windows adds registry values as part of its normal operations, & also whenever you install &/or run software. Some of those are for things like search indexing & application compatibility, & they'll stick around. There are often lots of more-or-less cache entries, e.g. HKCR\ Local Settings\ Software\ Microsoft\ Windows\ Shell\ BagMRU... MRU means Most Recently Used. And *Sometimes* when installing software in Vista & later versions of Windows, you'll get Component &/or Schema registry keys & values that appear to be temporary -- if you record changes to the registry they're recorded as new additions, but if you open Regedit, you will not be able to find those keys &/or values.
Installing today's GOTD, Soft Orbits Photo Retoucher, I recorded a total of "202858 registry entries added", but most all of that was Component keys/values, and so has no effect on the registry used when starting & running Windows.
If you're concerned about a Soft Orbits software installation deactivating previously installed Soft Orbits software you can set a restore point beforehand, or navigate to HKCU\ Software\ softorbits in Regedit & export that key to a file. You can later double click it to merge it with the registry, restoring everything under that key, or right click the file & select edit, deleting the Photo Retoucher key if it's there, closing/saving the file, then merging it with the registry, so that the new version is activated. From what I recorded however you shouldn't have to bother.
[If you're still curious about those Component entries, read on...
If you check the C:\Windows\ System32\ Config\ folder you'll see that some files named Components have been updated. The file named Components [no filename extension] is another registry file [hive] that isn't normally visible in Regedit, because it mainly has to do with Windows internal workings and Windows Update. In the win7 32 bit VM where I tested installation, the before & after [installing Photo Retoucher] sizes for Component were Exactly the same -- the plain text file with the majority of the recorded 200k entries is 57 MB. The recorded new Component registry entries themselves seem to be the result of a system scan for its current state, & I suspect they're recorded as new entries because the Component registry wasn't loaded when the recording app [InstallWatch Pro] took it's before snapshot. Since the Component hive isn't normally loaded [you have to manually load it in Regedit], I don't see a way to include it in the before snapshot of InstallWatch Pro or Regshot to be able to test this theory.
I don't know what triggers this scan or update of the Component hive -- it happens during some installs & not others... perhaps it's related to a check for the proper versions of something like the C/C++ runtimes in the WinSxS folder, which has close ties [links] to the Component hive? While it shouldn't cause any problems, one way to avoid it might be to use something like TimeFreeze or Shadow Defender, or a VM, install whatever software, copy what you need to, restore everything, then add the files, folders, & registry entries you copied. A final note, don't mess with the Component hive just because you're curious -- it's not as forgiving as the rest of the registry.]