B bramnet Contributor Joined Dec 8, 2016 Posts 19 Jan 1, 2017 #21 Um, yes. I changed it to index the drive in entirety (except Windows and ProgramFiles) as well as scan the file itself for its contents. That change was made a while back. (these were not caused by the command you had me run, just to be clear and the command didn't appear to change anything)
Um, yes. I changed it to index the drive in entirety (except Windows and ProgramFiles) as well as scan the file itself for its contents. That change was made a while back. (these were not caused by the command you had me run, just to be clear and the command didn't appear to change anything)
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,670 Location World, Europe, Italy Jan 1, 2017 #22 Not sure I understood. Did you change the indexing options before the problem appeared or not? And by the way, I'd reset them to their defaults.
Not sure I understood. Did you change the indexing options before the problem appeared or not? And by the way, I'd reset them to their defaults.
B bramnet Contributor Joined Dec 8, 2016 Posts 19 Jan 4, 2017 #23 yeah, that didn't fix it (I did restart my machine and cleared and rebuilt the index)
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,670 Location World, Europe, Italy Jan 4, 2017 #24 Did you try to run a check-disk (chkdsk) or scan disk (that should be the same thing)? And to defragment your system drive (using windows default defragmenter)?
Did you try to run a check-disk (chkdsk) or scan disk (that should be the same thing)? And to defragment your system drive (using windows default defragmenter)?