Windows Search service will not start on Windows server 2022.

Question

Good evening,

We are having problems with the Windows Search service on Windows Server 2022 Datacenter.

After having weeks of trouble with search indexing in outlook (we tried a lot of things, reinstalling outlook etc, updating the search index constantly, install filters), we could not get the search indexing in outlook to function without errors, even on the administrator account where rights shouldn't be an issue, at least we assume.

Now it's gotten even worse, after a recent update it seems like the windows search service has broken completely. We had a look in its registry and comparing it to a virtual machine of Windows server 2022, it seems like the entire registry of Windows Search is broken. Every time we try to start Windows Search we get error 1607, with no good description we, as of now, couldn't find any fix.

There seems to be a CrawlScopeManager_Previous version (location: **Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search**) . The rest of the folders are all empty. When I try to put anything inside the folder/registry, I get an error when the Windows Search service is trying to start.

When I force the search service to not automatically start and remain in an off state, I can put registry keys in the registry. When I do that, the next time I start the service everything gets automatically deleted again.

We do have some backups, but the customer is working with data that gets updated on a daily basis and we'd like to avoid that option for now. We also aren't sure if backing up is going to go well, since the backup for Windows Server 2022 doesn't seem to be officially supported by the hosting provider.

It concerns us a lot that the registry folders are there, but the values are empty. Search is still possible, but with indexing errors and it's just not the way we'd like it to be.

We’d really appreciate some help. Thanks in advance.

Answer 1

Hello,

Thank you for posting in Microsoft Community forum.

Based on the description, I understand your question is related to Windows Search service.

Sometimes, you can resolve Windows Search issues by restarting Windows Font Cache Service. To do this, follow these steps:

1. In the search box on the taskbar, enter services.msc to open the Services console.
2. In the right pane, right-click Windows Font Cache Service, and then select Stop.
3. Try to search again.
4. In the Services console, right-click Windows Font Cache Service, and then select Start.

You can also try use the Windows Search and Indexing troubleshooter to try to fix any problems that might arise. To use the troubleshooter, follow these steps:

1. Open a Command Prompt window, and then run the following command:

    msdt.exe -ep WindowsHelp id SearchDiagnostic
   

2. Run the troubleshooter and select any problems that apply. Windows tries to detect and solve those problems.

Have a nice day. 

Best Regards,

Molly

Answer 2

Hi,

Unfortunately disabling and enabling Windows Front Cache Service did not resolve the issue of the Windows Search service not starting. Even when the Front Cache Service is turned off, I can't start the Windows Search service.

The trouble shooter couldn't fix anything, but it did note the following issues:

Roughly translated, the rights to Windows Search-folders are incorrect (on the Administrator account)

And the Windows Search-service isn't running.

We look forward to hearing from you.

Answer 3

Also,

This is the error I get when starting the Windows Search service.

Fault 1067: The process closed unexpectedly.

Answer 4

Hello,

It seems there is problem with search service.

Go to Control Panel > Indexing Options > Advanced, and click on "Rebuild", this can rebuild the search index.

Best regards,

Molly