Constantly have to "Force Rebuild"

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
fury
Posts: 7
Joined: Tue Jun 10, 2014 1:14 am

Constantly have to "Force Rebuild"

Post by fury » Mon Apr 08, 2019 2:57 am

I'm running Everything 1.4.1.935 (x64) under Win10 Pro x64 1809. I started having issues recently. Frequently, new files won't show up until I manually do a "Force Rebuild".

It's not the search string at fault, because I leave that as-is, and the files appear after the rebuild is complete.

This happens on all my drives, and I've run CHKDSK, to no avail.

void
Site Admin
Posts: 4769
Joined: Fri Oct 16, 2009 11:31 pm

Re: Constantly have to "Force Rebuild"

Post by void » Mon Apr 08, 2019 3:29 am

I suspect this is due to short filenames being used in the USN Journal.
I would need to see debug logs to be sure.

Please disable short filenames and let me know if the issue persists.

To disable short filenames:
  • From a admin command prompt, run the following command:
    fsutil.exe behavior set disable8dot3 1
This operation takes effect immediately (no restart required).
https://support.microsoft.com/en-au/help/121007/how-to-disable-8-3-file-name-creation-on-ntfs-partitions

Resolving shortnames in the USN journal is on my TODO list.

fury
Posts: 7
Joined: Tue Jun 10, 2014 1:14 am

Re: Constantly have to "Force Rebuild"

Post by fury » Wed Apr 10, 2019 2:22 pm

Thank you.

I disabled 8.3 creation (and verified the registry setting), but it seems the issue persists.

I'll look into enabling debug logging.

void
Site Admin
Posts: 4769
Joined: Fri Oct 16, 2009 11:31 pm

Re: Constantly have to "Force Rebuild"

Post by void » Thu Apr 11, 2019 4:41 am

Thanks for the reply.

Could you please check "monitor changes" is enabled for all your NTFS volumes:
  • In Everything, from the Tools menu, click Options.
  • Click the NTFS tab on the left.
  • For each NTFS volume:
    • Check Monitor Changes.
  • Click OK.

fury
Posts: 7
Joined: Tue Jun 10, 2014 1:14 am

Re: Constantly have to "Force Rebuild"

Post by fury » Thu Apr 11, 2019 4:45 am

Thanks. It's enabled for all, and was previously.

void
Site Admin
Posts: 4769
Joined: Fri Oct 16, 2009 11:31 pm

Re: Constantly have to "Force Rebuild"

Post by void » Fri Apr 12, 2019 1:44 am

Thanks for the reply.

Please try enabling debug logging:
  • In Everything, type in the following search and press ENTER:
    /debug_log=1
  • Restart Everything:
    Type in the following search and press ENTER:
    /restart
Notes:
Debug logs can grow very large.
Debug logs are overwritten when you start Everything.

After you have detected Everything has missed a file system change, could you please send your %TEMP%\Everything Debug Log.txt to support@voidtools.com

Please compress this file before sending. If the compressed file is larger than 10MB, please let me know.

To disable debug logging:
  • In Everything, type in the following search and press ENTER:
    /debug_log=0
  • Restart Everything:
    Type in the following search and press ENTER:
    /restart

fury
Posts: 7
Joined: Tue Jun 10, 2014 1:14 am

Re: Constantly have to "Force Rebuild"

Post by fury » Fri Apr 12, 2019 2:15 am

I apologize (well, potentially). Before I posted previously, Everything did fail to index a new file I'd just created. But since then, I haven't had an issue. So the previous fix may have at least partially solved the problem.

Sorry--I only use it a few times a day, so it takes time for me to establish patterns. I test for a living, and don't have the wherewithal to do it off-hours as well.

I'll follow your advice if needed, and will follow up either way.

void
Site Admin
Posts: 4769
Joined: Fri Oct 16, 2009 11:31 pm

Re: Constantly have to "Force Rebuild"

Post by void » Fri Apr 12, 2019 6:11 am

Thanks for the reply.

I should note that disabling 8.3 filenames will only effect new files.
Old files will still have 8.3 filenames which might be used in the USN change journal.

Post Reply