Windows 10 (unlike Win7) keeps losing index of mounted (virtual) drive

1

For years I have been mounting virtual drives at logon (encrypted drives which are TrueCrypt files). In the drive properties, I set Indexing to ON. Windows 7 used to index those drives properly.

While Windows 10 will build the index, when I restart the machine, the index for the drive is gone (these files no longer appear in Windows search). Also, the drive doesn't appear in Indexing Options, except at the times when I click Rebuild in Indexing Options.

enter image description here

Here's what I've tried:

  • Rebuild in Indexing Options. This works, but I don't want to do that with each restart.
  • On the Desktop, I have made a folder that contains symbolic links to the encrypted drives. Since the Desktop is indexed, I was hoping that the drives would be indexed.
  • Indexing Troubleshooting. This seemed to fix some permissions but the problem remains.

If I can't get it to work, I'll have to kill Windows Indexing and spend hours evaluating third-party software -- not looking forward to that.

Switching away from TrueCrypt drives is not an option I am willing to consider at the moment.

Would someone have insights on this issue?

zx81

Posted 2016-07-08T09:08:49.310

Reputation: 426

Answers

1

At https://veracrypt.codeplex.com/wikipage?title=FAQ it says:

In order to be able to index a VeraCrypt volume through Windows Search, the volume must be mounted at boot time (System Favorite) or the Windows Search services must be restart after the volume is mounted. This is needed because Windows Search can only index drives that are available when it starts.

Try to restart the service: Run: services.msc > 'Windows Search' > Restart

Or from command line, with admin privileges:

net stop wsearch
net start wsearch

I hope this helps.

Babber

Posted 2016-07-08T09:08:49.310

Reputation: 11

Just what I was looking for, thank you. I already have a BAT file that waits for Dropbox, Thunderbird and other applications to start. Adding in net stop wsearch /y and net start wsearch has worked. Also had to run as administratior. Which required a BAT file to run a LNK file (as admin) to run a BAT file. Convoluted, but the startup folder wouldn't run a LNK file set to run as an admin. Hence the series of files. – Anthony – 2019-02-09T11:43:16.020

Asked: 2016-07-08T09:08:49.310

Viewed: 1 191 times

Active: 2016-10-30T12:37:39.050