Quick, but could not delete all-bar-one, which makes sense when you think about it. Not everyone is going to be wanting some kind of hesitant, multiple locations cautious approach, most are likely to have all in one location either downloaded from their cloud, or self-managed and moved over manually each upgrade-up.

And even-if one was wanting to filter by location, or other attributes, to deliberately keep SOME but not all of the duplicates found, there was no custom / fiddly filtering if you did need that.

A couple of parallel useful functions, like delete empty subdirs (subdirectories but not initial directory highest-level 1st directories, only 2nd onward) ... but one was then needing to ALSO delete the 1st level - one needed to manually find the USERS/ location for them anyway, to remove the highest level.

mm... program permissions? not asking for administrator confirmation? 1st level has runtime carried-over, passed-on executed BY user permissions, but subsequent do not, and are more easily reversed? something. not really a timesaver, when then unless you were OK with STILL HAVING most of the upon-1st-mouse-hover drop-down list (lvl1 depth) ... STILL being as clogged as it was before having clicked delete empty directories,.. but did want to say,.. ONLY reduce the number of extra directories for things like reducing the amount of empty directories on one's computer for shortening how long windows search catalogs user directories for the Index? sigh... then yeah, OK, some might find that useful,.. but coincidentally? The main POINT, of a duplicates manager/handler, should be for the VARIETY of reasons and needs, different people will be needing to do DIFFERENT, things, while doing that. i didn't ... i only needed to leave 1-of-everything ... but i also couldn't do that.

Essentially, the extras did not compensate for not being able to filter , sort, etc, nor select-all , nor in my case, select-all-but-1