The ability to search for a text string within files located in a folder and its subfolders is extremely useful. However, this feature could be improved.
When the program terminates a search before completing the task, it would be helpful if it provided information about why the search stopped and which file caused the issue. For example, when the program encounters a corrupted PDF document, it appears to simply cancel the entire search process without any explanation. As a result, the user is left to determine the cause of the failure.
In my experience, the search often stops when it encounters a corrupted PDF file. Identifying the problematic file can be very time-consuming, especially when it is buried within multiple levels of subfolders containing hundreds of files.
Ideally, if the search fails because of a corrupted or unreadable PDF, the program should skip that file and continue processing the remaining files. At the end of the search, it could generate a report identifying any files that could not be processed, along with their full folder locations and the reason they were skipped. This would make troubleshooting much easier and prevent users from having to manually search for the source of the problem.
