I'm not clear on the status of indexing subst volumes. What I have observed is that moving from 1.3 to 1.4 has made it impossible to see search results for subst volumes, even though according to the NTFS ui dialogs they can be indexed and included in the database. It all looks good, but there are 0 objects included in the database. This used to work. Is there a workaround (besides folder indexing) or is this currently broken?
Thanks for the great product! The new fast size sorting capability is a major win.
Note: I observe the subst issue on Windows Server 2003 R2, running the Everything service. I've tried running subst as administrator since their are no UAC tricks to pull on this OS.
EDIT: Of course, I figure out a solution 10 minutes after posting... After toggling things off/on, I managed to get objects from the source NTFS drive (E:) as well as the subst drive (M:\ => E:\Storate) included in the database. But the remaining trick was getting rid of the E:\ results because when I turned off "Include in database" for E: (but keeping USN Journal enabled!), all the objects on M: would vanish from the results. This used to work. Now the workaround was in Exclude to "Add filter" (not "Add folder") and enter "E:\*". Now on a client computer with a M: mount, everything in the ETP results is accessible quite naturally.
Unable to install Everything as a service On Win 10 64 Bit build 10586(.17)
[Now runing it as Administrator w/o problems]
Messagebox (retranslated from German): Everything system service: 1072 can not be created
-------------------
Event log:
Fehlerbucket 128958149927, Typ 5
Ereignisname: RADAR_PRE_LEAK_WOW64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 1e5b7df8-9dce-11e5-9bdc-0090278e01ba
Berichtstatus: 0
Bucket mit Hash: c1025642d9699f1f75081ae6405adbeb
Not sure if this covered by the SUBST issues listed above.
In my case, SUBST drives are still being indexed after having been deleted. Specifically... earlier today I used SUBST to create S: and T: pseudo-drives mapped to folders which I subsequently deleted with (e.g.) SUBST S: /D. Now when I search for files I am seeing duplicate entries mapped to S: and T: drives which no longer exist.
I tried Tools --> Options --> Force Rebuild and saw "Scanning Removable Disk (S:)" and "Scanning Removable Disk (T:)" messages during the process and the duplicates on S: and T: are still present after the rebuild. Just to be sure, I checked with both SUBST and Disk Manager to confirm that there are no S: or T: drives present on the W7 system.