ES shows non-existent files on non-existent drives.

[Darryl_Gittins]

ES shows files that do not exist. I think I have connected external drives in the past that have had these files, but the drives are no longer connected. Yet ED still remembers the files and shows them in a search.

For example, if I search for OutlookConvert-Full, I see the following entries, but only the E:\Software\ is a valid path.

E:\Software\Email\convert pst to eml\OutlookConvert-Full.exe
G:\software\Email\convert pst to eml\OutlookConvert-Full.exe
M:\software\Email\convert pst to eml\OutlookConvert-Full.exe
N:\software\Email\convert pst to eml\OutlookConvert-Full.exe

[therube]

Are you using File Lists or Folders or otherwise disabled updating of the drives in question?

If none of that, might need a Force Rebuild of the indexes?


(There are some instances where non-existent file [better said, renamed/moved files, generally associated with long filenames] incorrectly persist.)

[Darryl_Gittins]

I'm not sure how to answer the questions. I don't know what you mean by "using File Lists or Folders" or if I've "disabled updating of the drives in question". I would not have intentionally done that, nor do I know how to do that. AFAIK, I'm just using the default installation of SE.

How do you "Force Rebuild of the indexes"? Doesn't a reboot do that? After a reboot, the files still appear in SE.

[therube]

ES command line, only reads an existing Everything.db file.

Changes to Everything.db or things like File Lists, are affected by the Everything GUI/Service itself.


(And in that regard, how does ES know where or which Everything.db to use?)
[At least that's how I've assumed things worked, but... hmm... don't think ES reads the MFT directly, but... hmm... ?]