2.54.2765: Boxcryptor drive not available for Windows Search

chrullrich

Hello,
the change log for 2.54.2765 includes the item "Added: Option to enable Windows Search explicitly". This does not appear to work (for me); the X drive does not show up as available for indexing with this option on (or off, and it did not in previous versions either).
I also noticed that the message that comes up when I enable the option tells me to 'select "Change" in the indexing options'. I'm on Windows 11, so perhaps there has been a change to that dialog, but I don't have a "Change", only "Modify". Am I looking in the wrong place?
Thanks!

upD8R

I'm also currently evaluating Boxcryptor and I'm facing a similar issue on Windows 10 (also w/ previous Boxcryptor version). It seems the Windows Search service is actually starting too fast on my PC. That means it kicks in before the drive letter is available to the OS, therefore it is being ignored/not seen during the indexing.

If I start and stop the search service, Boxcryptor drive can be selected in the indexing options and indexing starts as expected.

I read a few comments about setting a further start delay for services in the registry but I don't have the impression it works. As soon as I login the service is already up and running but Onedrive/Boxcryptor are still starting ... (and no, my PC isn't slow ;-)).

Any ideas how to delay the Windows indexing?

chrullrich

upD8R I have two ideas that do not work:

First, I'd set the Windows Search service to delayed-auto start. This is already the default, so it will not help.

Second, I'd try manual start with a trigger: sc.exe triggerinfo WSearch "start/device/4d36e967-e325-11ce-bfc1-08002be10318/{41D33169-5A81-4b4e-8571-3BE1B64F905B}\VirtualStorage". The first GUID is constant (it just means "Disk drives"), the second may be specific to the PC in front of me. You find it in the device manager, properties of the "Callback Technologies Virtual Storage" under "Disk drives", Details, Hardware IDs. Then it will start when that device has come into existence. Since there are plenty of other things in the system that will start the service when they want, rather than when you want, this does not work either. (I mean, it works to start the service if it is not running yet, but it will be running.)

Also, thanks for the hint with restarting the service. It has no effect here, unfortunately. Even after restarting the WSearch service the X: drive does not show up in the indexing options.

upD8R

As workaround I'm using a batch script triggered by task scheduler to restart the service 1min after logon. Let's see if this is sufficient ...

huhugrub

Same here. The boxcryptor drive is nowhere to be seen under Indexing Options. Drive without being able to search is rather useless.

upD8R

Sorry, missed the responses. Actually, my workaround is working well here. But services restart is a prerequisite and if this is not working in your case my solution obviously won't help. So this might be a different issue then.