Rogue SearchIndexer Process

Son of a nutcracker! I mean, really! Take a look at this screen shot from my services applet.

The back story on this is that I had manually disabled the Windows Search Service (not set it to manual, mind you) because it sucks up enough resources to choke a Cracker Barrel regular. After turning the service off and disabling it, I went about my merry business until I noticed my machine was acting like a pig again. The only thing I can think of that might have kicked off the service was when I ran a search in Outlook, but remember the disabled part?

Does this mean that the Outlook team ignored the service settings for the search indexer when spooling up their search or does it mean the Windows search team ignored it? Well, someone did and that is just bad behavior.

Thanks a lot.