Windows could not start the windows search service on local computer

I have 4 internal drives, 3 multiboot, one strictly for data backup. For the purposes of backup protection, at least 2 are always disconnected unless a backup procedure is in progress.

While all 4 disks were connected, I decided to change the indexing folder location from one of the data partitions on the multiboot disk to the the non-multiboot data disk.

Indexing completed, and everything went fine, until I disconnected the other 2 multiboot disks, after which indexing was broken...irretrievable.



I tried all the suggestions here, and elsewhere, except for deleting Windows.edb. Before that, I figured I would reconnect the other drives to see if that was missing part of the puzzle.

Turns out it was. Indexing is back, or at least it is once again operational, however, the index location had reverted to the default C:\ProgramData\Microsoft location.

So I had to rebuild it, which is now in progress, on my data disk



I didn't have this problem when it was located on the other multiboot disk, and the 2 others were not connected. so what changed things this time? What was the "missing component" provided by connecting the other drives.

But what happens when it's done, and I disconnect the other drives? I need to find out.

EDIT: After all this, it turns out that the indexing location was changed from the one I chose, to C:\ProgramData. \Microsoft.

How does this happen?

Keep it simple - indexing will only have been designed to run on a single O/S and related disks.

Given the large number of boot configurations you seem to mention, I would have thought permissions issues would have made a large proportion of the content of other O/S's on other disks inaccessible.

Restrict your index locations to the normal disks you would expect to index from that one O/S.

dalchina said:

Keep it simple - indexing will only have been designed to run on a single O/S and related disks.

Given the large number of boot configurations you seem to mention, I would have thought permissions issues would have made a large proportion of the content of other O/S's on other disks inaccessible.

Restrict your index locations to the normal disks you would expect to index from that one O/S.

Hi dalchina,

I I think there is a misunderstanding. This is only about the choosing an alternate location for the "Index Database", "not" a question about locations to be indexed. I think I know, at least partially, what has been a factor here.

These are my original index locations, which happen to be the 2 data partitions on Disk 0, which were reinstated, as was the Search service, after, as I mentioned, I reconnected all 4 disks to see if, in fact that would be the result of reconnecting them.



However, this is what was listed as my Index Database location, which, of course, is the default OS location,



Not here, which is one of two partitions on my "data only" Disk 2, where I had rebuilt the database



The fact is, previous to all this, I already had a working database, which had been relocated here, a data partition, on Disk 1, one of my other 2 multiboot disks.



Bottom line, at a previously point on time, I had this working, with the database relocated on another disk. with no problem, but now, indexing itself is broken.

I just reconnected all the disks one more time see if it will allow me to choose a different database location without breaking.

The database is rebuilding now, on the Disk2 location. Well see what happens after it finishes, and I disconnect the other 2 multiboot disks.

- - - Updated - - -

dalchina said:

Keep it simple - indexing will only have been designed to run on a single O/S and related disks.

Given the large number of boot configurations you seem to mention, I would have thought permissions issues would have made a large proportion of the content of other O/S's on other disks inaccessible.

Restrict your index locations to the normal disks you would expect to index from that one O/S.

Rebuild completed. Disconnected the 2 multiboot disks. Database location I:\ partition. It's working normally, fingers crossed.

Here's another source that may help, if it continues:
https://answers.microsoft.com/en-us/...f-77e842325736