Windows Search Service Terminated Unexpectedly -

Have you been experiencing some random slowness on your system? Are there search queries that are not finding data you know exists? Is your event log full of Service Control Manager 7024? Is the Windows Search Service terminating over and over again?

There is a decent chance that you are experiencing what more and more Windows 10 users are complaining about – A corruption within the Windows Search functionality that is creating issues with the termination and/or start of the service.

Do not throw your machine away just yet – this is one of those things that can generally be corrected fairly easy but does take a few clicks to rectify.

” This event is generated when the Service Control Manager cannot properly terminate a service. The name of the service and the error generated by it are displayed in the event. “Microsoft – https://social.technet.microsoft.com/wiki/contents/articles/13754.event-id-7024-service-terminated.aspx

The errors generated may come in a small variety of options but all of them will list the specific service that is having the issue near the top of the event log item.

In this example, we are having an issue with the Windows Search service. The specific string reports it ended with the service-specific error %%2147749126

How Do I Find What Service It Is?

To review the service-specific error code:

Click the Start button, Run, then type cmd to open a command prompt.
Type sc query service_name (where service_name is the name of the service) at the command prompt to display the service-specific SERVICE_EXIT_CODE error code that the Service Control Manager encountered when stopping the service.

Note: If the service was stopped successfully, the SERVICE_EXIT_CODE field should contain a zero (0). If the service failed to stop when an attempt was made, this field should contain an exit code provided by the service when it could not stop.

Review the related events logged by the SCM

To review the related events logged by the SCM:

Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer. Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.
Click Event Viewer (Local), then Windows Logs and System.
In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.

The error code and related events for this service should help you to further troubleshoot and resolve the issue. Some examples are provided below:

If event ID 7011 is also logged for this service, then extending the service timeout period to resolve event ID 7011 would also resolve this error.
If event ID 7034 is also logged for this service, then restoring the service default settings to resolve event ID 7034 would also resolve this error.

So – How Do I Fix It?

Some users have found their resolution being as easy as going into services.msc and setting the recovery of the faulting service to do nothing, manually start the service and then rebuild the windows index database.

Look under: C:\ProgramData\Microsoft\Search\Data\Applications\Windows. The database file is Windows.edb. With Windows Search service disabled, delete this file, re-enable Windows Search service and let Windows rebuild the database.

Other users have reported that adjusting the service start through registry to not start, then rebooting and processing the above steps.