OK, I can see how that could be disconcerting, for a stopped process to pop on when you had thought you had actually stopped it. But anyway, I tried to duplicate what you describe, and the service named "Windows Search" remained in the disabled
state, as I have had it for a while. I have no clue why it does not behave the same for you. Some kind of weird thing going on there. (The doctors thing -- I'm just saying don't expect ordinary users here to know about these things, especially of some background
process that is not readily apparent.)
I didn't disable it. If you disable it, then it will not run; my point is that Explorer
tries to run it every time you open a folder, but if it is disabled, then it fails. That’s particularly dumb because if it is disabled, then it should not even attempt to run it. My point is that disabling the service does not turn it off, it only prevents
it from working.
The goal is to turn it off so that Explorer does not even attempt to use the Indexer because the user specified that they don’t want it.
It’s like tying a car that is in gear to a post with a chain. It might successfully stop the car from moving, but it’s only a hack/workaround (and likely with undesirable side-effects). The proper solution would be to turn the car off altogether so that
the chain isn’t even necessary.
What’s worse is that you can even “remove/uninstall” the Indexer by deselecting it from Windows Features and yet, Windows
still uses the indexer (or at least tries to).
Others have grappled with this issue without success. :-\