Ok, I used Fileseek for a while on my old computer and even on that one it kept crashing when searching large numbers of files (most of the files searched were plain old ordinary text files in .txt format easily viewable by notepad) for a text string. I recently built a whole new computer and Fileseek still crashes/freezes when searching a large number of text files for text. This time around I noticed that almost every time it happens when there have been 7070 files searched. When searching a drive/folder that contains 10's or 100's of thousands of files this makes Fileseek completely unusable for the purpose it supposedly was designed for. I don't index these drives with Windows search because the sheer size of the index files created would end up practically crippling my computer (in some instances these drives/folders contain several million files divided up into various folders/subfolders) and besides I am completely content to wait for the results of a search, provided the search program actually works of course, which sadly Fileseek 2.13 does not when handling large numbers of files it seems. Hopefully this problem will be addressed in the next release of Fileseek.

Oh and by the way I can't provide any error messages/logs because none are being generated, Fileseek just freezes/crashes at 7070 files searched and as a result when I reboot my computer Windows wants to scan the hard drive for errors which considering the sheer number of files on that particular drive (a 1Tb SATA drive filled to 95% capacity) takes several hours to completely scan. This is unacceptable in terms of the risk of data loss due to the fact that Fileseek seems to be responsible for causing whatever corruption Windows thinks may have taken place that seems to warrant scanning for errors. While I really do like the features of Fileseek I just can't use it, and certainly can't justify donating money for software that's essentially unusable for the task it was designed for.

So I urge you to please fix Fileseek!