Congratulations for a wonderful utility.
Now, the report: BRU (184.108.40.206) unnecessarily goes deeper inside sub-folders when the user specified max path length was already exceeded. That results in a waste of time and, worse, breaks BRU when the Windows API file path length limit is exceeded.
So, it would be better to double check: never exceed both the user maximum and the windows API limit (about 250 Bytes).
I have a file structure at exceeds the silly Windows API path length limit. Probably that happened when file trees were moved inside others. I don't think it is a rare situation.
It is amazing, but not a surprise, that in Windows one can create a file structure that can not be parsed by the file system.