Indexing NEVER completes

Question

_{Monday, June 5, 2017 10:54 AM}

Windows 10 Pro (1703).

Between SearchProtocolHost.exe and SearchFilterHost.exe, about 30% of an i5 CPU is getting used perpetually.

On investigation I found that indexing never actually finishes. Repeated attempts to delete/rebuild the index always results in it reaching the same number of indexed items (plus or minus a few from the previous attempt) but it never actually reports finishing. This is a relatively clean/benign install of Windows. Note also that there is no associated hard drive activity, only aberrant CPU usage.

All replies (9)

_{Monday, June 5, 2017 11:48 AM}

Same here. The last 4 Dell computers we bought for our firm over the past several months all have the same issue. We run win10Pro.

_{Tuesday, June 6, 2017 2:28 AM}

Hi Sunsanvil,

It would seem that an error in the index is causing this high cpu usage. You could try to rebuild the index to check.

Try this:

Go to control panel... choose to view as small icons... then select indexing options

or search for indexing options

Open it

Advanced

Choose rebuild from the troubleshooting section (DOH).

Also try and disabling the .XML file extension from being indexed in the Indexing Options control panel.

Hope it will be helpful to you

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Tuesday, June 6, 2017 11:47 AM}

It would seem that an error in the index is causing this high cpu usage. You could try to rebuild the index to check.

Per my opening post I have already made several passes at rebuilding the index.

I will try removing .xml from the manifest and report back.

_{Tuesday, June 6, 2017 3:59 PM}

To diagnose a performance problem you could use the Windows performance toolkit, the instructions for which can be found in **this wiki
**Close all other programs before starting the trace, makes it easier to find the problem.

_{Tuesday, June 6, 2017 6:56 PM}

To diagnose a performance problem you could use the Windows performance toolkit (...)

We already know what the problem is: **SearchProtocolHost.exe and SearchFilterHost.exe perpetually chew up CPU because the index never completes.

_{Tuesday, June 6, 2017 8:00 PM}

with a trace we could see WHY the processes use so many cylces.
As the problem is not happening on all system, there is obviously something different on yours.
Might be a 3rd party IFilter implementation.

_{Wednesday, June 7, 2017 2:38 PM}

My apologies. I thought you were referring to Performance Monitor. I've never played with the Performance Toolkit but have downloaded it now and will experiment with it against the issue and report back. Thanks.

_{Wednesday, June 28, 2017 9:48 AM}

Hi Sunsanvil,

Any update?

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Saturday, March 23, 2019 9:15 AM}

So this response applies to the title , which is "indexing never completes". I've had this issue ever since the latest WIndows 10 major update was installed. Event viewer showed the error 10023 turning up every 8 minutes. Reading www on the error it was stated that the issue was likely an ifilter, such as the one which is installed to scan pdfs. So I step by step, removed nearlly all the filters, replacing them with index properties only settings. The error kept coming back UNTIL, i took MS outlook out of indexing. Presto, no errors. What;s more, the indexing completed in about 10 minutes instead of goign for days and still not completing  

So in summary try this

a) start indexing options , select modify, select indexed locations, uncheck Microsoft Outlook

b) If you know how to , check there are no further 10023 errors in Event Viewer for search functions

Search inside outlook still works fine for me . I guess this just stops search results coming up from the windows search button outside outlook from Outlook Ost, exchange , whatever