While we cannot overlook the fact that the CPU usage may spike while rebuilding the index, this service should not consume CPU when the search process is not in operation. Ideally, it should only consume a few percent when using the search feature. The service starts consuming higher CPU resources due to corrupted index databases and misconfigured lookup locations and indexing type. This article will guide you through different methods to solve when Windows Search Indexer has a high CPU consumption.
How to Fix Microsoft Windows Search Indexer Having High CPU Usage
Before you start with the fixes, please note that it is normal for the search indexer service to consume a high CPU if you have just rebuilt the index. You need to wait until the indexing is complete. Otherwise, you can tweak a few settings, like restarting the search service and reducing the lookup location to sort out the problem.
Disable or Restart Search Service
If your computer runs over an SSD, disabling the search service may not significantly impact your PC’s performance. This is because SSDs are robust enough to locate your files instantly. So, in such cases, it would be a good option to disable it. However, it is not recommended to disable the Search service on computers with HDDs.If you use search feature regularly, you can proceed with a simple service restart rather than disabling it. A restart would fix the issue if the service consumed a high CPU due to halting or freezing. To restart the Windows search service, you should first disable it by following the same steps above.
Run Troubleshooting Tool
Next, there is a troubleshooting tool integrated into Windows itself that helps to diagnose and troubleshoot if there is any error with the Searching and Indexing feature. You can run the tool and act accordingly as per the diagnostic results.
Reduce Lookup Location For Indexing
If the indexing settings are set such that it needs to look up in a wide range of locations for searching a file, it can consume a considerable amount of time. For instance, if you frequently search for files located in Local Disk (C:), you can adjust the settings so that Windows will search only for disk C.
Change Indexing Type
Windows can basically perform two types of indexing. The first one is indexing based on file properties only, and the second is indexing based on file properties and contents. With the latter option, CPU consumption can suddenly spike as it begins to search for the contents of the file too. Many of us search with a filename rather than content, so it would be helpful if you disable content indexing.
Recreate Search Database
Windows utilizes a database file, namely Windows.edb, to store indexing information, specifically for content indexing. However, when the database size goes on increasing, chances are there that it might get corrupted. As a result, search features can not locate the files and begin consuming higher CPU. Therefore, deleting the old index database and recreating it can help solve the problem.
