Microsoft windows search filter host is burning my cpu usage.

Q

Microsoft windows search filter host Microsoft windows search filter host is burning my cpu usage.

✍: Guest

A

Method 1: I would suggest you to run “Search and Indexing” troubleshooter to diagnose the exact issue.

Follow these steps:

a. Press “windows key + W” on your keyboard.

b. Type “Troubleshooting” without quotes in the search box and hit enter.

c. Select “View all” from the left panel.

d. Select “Search and Indexing” and follow the on-screen instructions.

Method 2: I would suggest you to try disabling the .XML file extension from being indexed in the Indexing Options and check if the issue is fixed.

Refer the folowing steps:

a) Press “windows key + c” on the keyboard.

b) Select Settings

c) Type Indexing Options, and select indexing options from the search

d) Click Modify.

e) To add or remove a location, select or clear its check box in the Change selected locations list, and then click OK.

f) If you don't see all locations on your computer in the list, click Show all locations. (If all locations are listed, Show all locations won't be available.) If you're prompted for an administrator password or confirmation, type the password or provide confirmation.

g) If you want to include a folder but not all of its subfolders, click the folder, and then clear the check box next to any subfolder that you don't want to index. These folders will appear in the Exclude column of the Summary of selected locations list.

Method 3: Additionally you may also perform a full system scan using the Microsoft Safety Scanner to eliminate any issues related to virus/malware.

http://www.microsoft.com/security/scanner/en-us/default.aspx

Important Notes:

· The Microsoft Safety Scanner expires 10 days after being downloaded. To rerun a scan with the latest anti-malware definitions, download and run the Microsoft Safety Scanner again.

· Any data files that are infected may only be cleaned by deleting the file entirely, which means there is a potential for data loss.

2016-01-27, 1827🔥, 0💬