In Everything 1.5.0.1400a x64 Portable on my Windows 10 Enterprise 20H2 x64 [10.0.19042] when I delete solely a file [i.e. not delete a folder in which that file happens to reside] and then navigate in FreeCommander to a Recycle Bin like e.g.
M:\$RECYCLE.BIN\S-1-5-21-3797103458-798797042-3558267449-1001
name of that file is shown renamed to a coded gibberish. But when I evoke in that program the overall Recycle Bin
::{645FF040-5081-101B-9F08-00AA002F954E}
then I see its original normal name. But in Windows Explorer I always see its original name, even if I paste in to its bar the same path
M:\$RECYCLE.BIN\S-1-5-21-3797103458-798797042-3558267449-1001
because apparently Windows Explorer always shows to me content of all Recycle Bin folders i.e. I cannot narrow down presented list of items to just one Recycle Bin folder from a particular volume
So... so far so good - i.e. Everything program is not responsible for different behavior by 2 different file explorers. But here comes the bug and / or lack of logic within Everything:
Because what happens if I delete 1st file? It disappears from the main list seen when Filter named Everything is active. And in order to see that deleted file I need to use that Recycle Bin oriented Filter of mine. So still so far so good
But what happens if I switch back to using the Everything Filter and delete 2nd file with exact same name? It also correctly disappears from the list - and refreshing the view does not change what I [do not] see. So now I once again need to switch to using such proper custom made Filter that allows me to see this second [and first] deleted file
But now if I will again switch back to using the Everything Filter, then an entry with that name appears on the list with a location specified as
Recycle Bin
So why those deleted files do not start to appear from the get-go [i.e. after first deletion] but only after second deletion and additionally after me having used Recycle Bin oriented Filter and then also switching back to using the default Filter? And why am I only shown 1 entry on the list [when using now the default Filter], when it represent 2 files from 2 different [source / Original] locations? How is a user suppose to know that this 1 entry represent 2 and not 1 or 3 files? Right now this entry when it shows up is an opaque umbrella hiding whatever amount of files
As for the scenario when files [bearing the same name] get deleted by the means of deletion of folders in which they reside [also sharing a same name but different from the name of files], handling of their naming in FreeCommander and Windows Explorer behaves the same as above i.e. FC shows gibberish within a Recycle Bin folder but normal name withing the system wide Recycle Bin folder, while WE always shows normal name. And the same is true for name of folder
But the appearance in Everything of file deleted in such way and appearance of its folder is not the same like in case of deletion of directly / solely file. Because although its presence on the list when using the Everything Filter needs to be triggered with switching to that custom Filter - it nevertheless does not require a companion file / folder bearing the exact such name i.e. a deletion of second one is not needed
But there are additional issues: after deletion the file shows no data in the Date Deleted column, while its folder does; and also the file shows no data in the Original Location column. I reckon it is not a bug but a feature, due to technically this being logical because the file was not deleted - it was the folder holding that file that got deleted. But then again: how is a user suppose to know that it is not some bug manifesting itself with lack of shown data? An intended lack of data and erroneous lack of data look the same, amiright? And what is more, when I switch back to the Everything Filter then the Path of that deleted folder is shown as
Recycle Bin
but the Path of file it was holding is shown as
M:\$RECYCLE.BIN\S-1-5-21-3797103458-798797042-3558267449-1001\$RFEXXYR
In my opinion this file is shown in an informative way, because colu,m of Path includes the name that this file now has when it is in this local Recycle Bin folder - but at the same time it reveals no connection to Path of its folder it was residing in before deletion of that folder. But then again: how could the deleted folder show a Path of a local Recycle Bin when more than 1 folder bearing the same name got deleted and Everything shows only 1 entry when using the default Everything Filter i.e. how would it pick which source / original location to show?
I know that this report and my reasoning got a bit complicated and way too long, but it all comes down to this: presence of deleted items on lists in Everything is inconsistent, they are displayed with ambiguous info or lack of thereof, plus they might require triggers in form to switching back and forth between Filters in order to show up at all