I just ran Filefind to look up a certain name which is part of subdirectory-names as well as individual filenames on my file-system as I often do with the intention of getting a quick and grouped overview of all the instances of files/dirs which would contain said name at a glance. Because of this being such an easy and commonplace task I did not bother to formulate a specific, full-syntaxed glob-search but decided to go for a simple substring-search by just entering the bare name and hitting <Enter> instead. As for most searches here the "Everything" box was checked as well as "Archives" and unlimited depth.
The search took longer than expected and to my surprise terminated with "No files found" - search aborted. And yet I was absolutely certain at least a dozen or so matches had to be there! Next thought was that maybe an erratic mouse-move might have triggered the search to stop inadvertently and prematurely and hence come back with the unexpected statement "search aborted". Another try - yet with the same result (the famous Einstein-quote about insanity briefly came to my mind

When investigating the cause of that malfunction I tried, among other variations, to uncheck "Everything" and Voila! The results came back as expected. So the suspicion arose there might be something corrupt within the Everything data-structure. Visiting the Everything-homepage I found out that meanwhile a newer version had become available. So I downloaded and installed. As a quick check I immediately repeated the search again with "Everything"-checkbox ticked. Search performed normally and came back with the same results as the "TC-only-method". Glitch ironed out - system back to normal!
The real frustration set in when after the next re-boot - and with the freshly installed update of "Everything" - the search malfunctioned again!

Could some kind of bug have been introduced with beta7? Has anybody here in the forum had similar experiences? Can anyone confirm the (mis-)behavior described above?