Search all files (ctrl+shift+f) doesn't find results in files with very long filepaths unless opened in the editor

• VS Code Version: 1.53.1 5d424b828ada08e1eb9f95d6cb41120234ef57c7 x64
• OS Version: Windows 10 Pro - Build 19041

Steps to Reproduce:

1. Make a new file with a very long filepath in vs code.
2. When the file is not open in the editor, use ctrl+shift+f to search for any content in the file. No results appear.
3. Open the file and search again. Results appear.

Specific steps to reproduce on Windows 10:

1. Make a number of nested folders in windows explorer until this error appears:
2. Add more nested folders/files to this directory using VS code.
3. Make a txt file with a specific string in it and search for this string when the file is not opened in the editor.

The error seems to occur with filepaths exceeding the max filepath length of windows explorer.

Examples: The bug in action:

Example Path: C:\Users<MY-USERNAME>\Desktop\long-named-foler-to-reproduce-bug-of-eternal-destruction\long-named-child-foler-to-reproduce-bug-of-eternal-destruction\long-named-child-foler-to-reproduce-bug-of-eternal-destruction\another-long-nameanother-long-nameanother-long-nameanother-long-name\deep.txt

Does this issue occur when all extensions are disabled?: Yes

Console output:

[starky27]

Same issue. Can’t resolve it using @BrandonClapp approach, because the project itself has deep file structure. Those part (with long paths) is developed by another team using Mac, so they don’t have any issues. As a result, I forced to switch to Atom when I need to find something across the whole project.

[yuriy-bezrukov]

Is there any update?

I love vsCode. But looking for text in files in Atom

Please, help