Do I need administrative privileges or the Everything service to index folders?
No, folder indexing does not require administrative privileges or the Everything service.

Why is indexing so slow?
Folder indexing uses the same approach as the Windows search.
This can be a lot slower than NTFS indexing.
Everything can take a couple minutes to scan a folder and all it's subfolders and files.

Will Everything detect all file name changes made to this folder?
No, not all file name changes can be detected.
Changes made remotely are not detected.
Lots of changes in a small amount of time can be missed.

You can specify an update time or update interval to rescan the entire folder for changes that might have been missed.

What happens if the indexed folder is offline or not available?
The folder index will remain unchanged.
However, forcing a index rebuild will show the folder as empty.

Everything will continue to re-scan the folder at the specified update time or update interval and only update the folder when it is online.

Displaying icons and file information of offline folders can take several seconds to time-out.
You can press F5 to refresh this cache when the folder is back online.

Was wondering – if there's no journal in FAT32, aren't there some system messages, like there are mouse's, windows' and all other, that the file system's driver sends up, so all file changes could be caught? At least in realtime with the background service.

everything is not responsive with folder indexing until it is completed. I'm using this feature to index manually remote drives (about 6TB) in NAS. It take too many times. It would be better if it is possible to do the folder indexing in background. While indexing, the preferences window is always on top status.

I just wonder if there is any way to support everything in NAS like ETP server usage.

I have to drives that are network connected, and I cannot get them recognized by Everything Search. Here is how they look in MS File Explorer (Win8): "Public (\\MYBOOKLIVE2) (U:)". Any ideas how to access them??

Same here as some other posters' comments... Trying to index a network attached 6TB drive, the indexing process just seems to take forever and/or the Everything GUI just hangs "not responding".

Are there any log entries or other behaviour that can be monitored so I can see if the folder indexing is actually doing... anything? After a few retries it's now been sitting there for 2 hours "Scanning...".

During this time the regular Everything behaviour/DB seems offline so it's a bit frustrating not being able to figure out if the tool is doing something productive yet taking a long time, or just spinning its wheels doing nothing good.

Please try to reproduce this in debug mode. What is displayed in the debug console when Everything is not responding?

Unfortunately, there is no progress indicator other than the scanning... status.

Usually 1 million files takes about 6 minutes to index with folder indexing.
Is there any disk or CPU activity from Everything after several minutes?
Do you have any reparse points? Circular reparse points would cause Everything to index forever.

Hi, just started using your software (v.1.3.4.686) in Windows 7 (64bit) and the search speed for local HDs is impressive.

However, I also have a NAS (WD mybooklive) on my network which is obviously recognised by Windows via the network tree. I am trying to add this drive via tools/options/folders -> add, the drive is not recognised when I drop the network tree.

The indexing take forever on my computer. I am able to index one network drive (491GB) over a course of 2-3 days ( I had the computer turn off at night) now it is scanning a second drive which is 335GB. My question is what happen when I turn off the computer while the program is still indexing? Will the program pause the indexing and start where it left off when the computer is turn on again? Also, is this the normal speed for a drive this size? If not, is there anything I can do to speed up the process.