Some folders are not fully indexed?

[Vadim_k]

Some files on my local hard drive cannot be found by name. I Came up with a 4-step workaround:
1. Rename the folder with the file;
2.Create a new folder with the original name of the original folder;
3. Move all files with the original folder to the new folder.
4. Delete The original folder.

After that file is found by name. This problem happens with some files in some folders. What could be a reason to that?
It looks like the original folder is not indexed properly. I tried to restart everything to enforce re indexing, but it didn't help. The only way to get all files In a folder to get fully indexed is to re-create a folder. Problem is I don't know exactly how many folders are not indexed properly.

Any help would be greatly appreciated

[void]

Do you have any exclude hidden or system files, exclude filters, exclude folders or include only filters set in Tools -> Options -> Exclude?

[therube]

I tried to restart everything to enforce re indexing

A restart may not necessarily do that.

Tools | Options | Indexes -> Force Rebuild

[Vadim_k]

@void, I only exclude Recycle Bin. Thanks!

[void]

Do you have any search options enabled from the Search menu?

Does forcing a rebuild from Tools -> Options -> Indexes -> Force Rebuild help?

[Vadim_k]

@void, No search option enabled.
Next time I come across an un-found file, I will test to force rebuild index, since I experience this issue sporadically. I wonder if there is a log file that show what wan indexed to troubleshoot incomplete indexing?

This is a great forum. Fast responses and very relevant!

[Vadim_k]

@therube, Thanks for noting force rebuild

[NotNull]

Just out of curiousity:

Is there a difference in a Force Rebuild versus stopping Everything, deleting the database, starting Everything?

[void]

I wonder if there is a log file that show what wan indexed to troubleshoot incomplete indexing?

To enable debug logging in Everything:
Type in the following search and press ENTER:
/debug_log

A debug log is created in %TEMP%\Everything Debug Log.txt
This will log all file system events which may show what is happening.

Logging will continue until:

• You exit Everything.
• you type in the following search and press ENTER:
  /debug_log

Debug logging.

Is there a difference in a Force Rebuild versus stopping Everything, deleting the database, starting Everything?

There is a small difference, forcing a rebuild will reuse indexes if they are offline. ie: only online volumes are re-indexed.

Deleting the Everything.db will completely wipe the indexes, offline volumes will appear empty after a new Everything.db is created.
Note: Deleting the Everything.db will only work if Everything is not running.

[NotNull]

Yet another to-the-point, accurate and complete answer by @void. I really like your posts! Thanks!!

[Vadim_k]

Here is an update:
While attempting to delete Everything.db, I discovered that I had 2 versions of everything installed with 2 databases:

• - One in folder C:\Program Files (x86)\Everything\, about 2 Mb size,
  - Another one in folder C:\Users\<username>\AppData\Roaming\Everything\ about 10 Mb size.

I uninstall both versions and did a clean install of the latest 64-bit version. Now I have database located in folder

• - C:\Users\<username>\AppData\Local\Everything\ about 23 Mb size.

Hopefully this is a complete and accurate index now.

Thanks for all your help!