Microsoft windows search filter host is burning my cpu usage.

Anonymous
2012-11-05T09:44:11+00:00

Original Title: Microsoft windows search filter host

Microsoft windows search filter host is burning my cpu usage.

Help me.

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2015-04-13T14:46:53+00:00

Had the same problem and DiaconuDaniel's solution worked for me as well - took a while to recreate the index but then everything was fine - Thanks

Was this answer helpful?

400+ people found this answer helpful.
0 comments No comments

96 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-06-23T08:38:25+00:00

    Hello, all from there for me didin't work.

    But i found fix which working for my surface excellent:

    Right click on your Disk, go to properties and uncheck the option of indexing / it is the second one.

    It take some time, and probably you must do this with all your drives

    After this everything works well.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2016-05-20T09:48:38+00:00

    Reload the system with a clean installation. Do not add programmes or hardware but update the system. I had to do that. I agree with what you say

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2016-05-19T06:26:24+00:00

    This response is worthless.  The troubleshooter rarely finds anything, and in this case, it certainly finds nothing.

    Method 2 is incorrect.  It says "don't include .xml files in the index" and yet there are no steps on how to actually remove .xml files from the indexing list!  All it does it tell you how to remove a directory, never a file type.

    Please remove this worthless answer from the list.

    All, I re-indexed my entire disk as suggested in the other popular answer.  It took 3 days to re-index my disk!  Yes, that is 72 hours!  During which time the "background" low priority index process ate up 100% of my CPU and prevented me from being able to do *anything*.  I couldn't stop the indexing because I had no index, so there was no choice but to continue until the indexing completed (600,000 files total).  And, even when the new index was complete, I have seen no significant improvement in system performance.  Even as I type this note, my CPU is running near 80% usage on searchfilterhost, svchost, and LocalSystemNetworkRestricted. 

    I have seen enough comments in these forums that it is pretty clear 'low priority' background tasks aren't working properly out in the field (even though MS personnel claim it works fine in their lab and Q/A environments).  Remember, it's in the field where it counts, not the lab.  Please take the time and make the effort to fix these rogue tasks in your OS's.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2013-10-22T15:31:43+00:00

    i have this problem too ! please has anyone solved this matter?????

    Was this answer helpful?

    0 comments No comments