How to Fix Search High CPU Usage in Windows 10 version 1903
As you may remember, an optional cumulative update to users of Windows 10 version 1903 'May 2019 Update', KB4512941/18362.329 has a couple of bugs that affect many users. One of them makes the search/Cortana feature broken and causes high CPU usage, the other bug is a broken screenshot feature.
Windows 10 1903 build 18362.329 (KB4512941) has appeared in the production branch after a short period of testing in the Release Preview ring. After installing the latest cumulative update, many users began reporting unusually high CPU usage even when the system was idle. They have been reporting that the high CPU load was caused by the SearchUI.exe process.
Additionally, the affected users have been complaining that the Search flyout was broken for them and was opening without any content.
Microsoft has been investigating the issue, so this led to a working fix. Microsoft has now released a workaround to fix the search problems.
To Fix Search High CPU Usage in Windows 10 version 1903,
- Open the Settings app.
- Go to Windows Update & Security -> Troubleshoot.
- Click on Additional Troubleshooters.
- Click on Search and indexing.
- Run the troubleshooter.
This should resolve the issue automatically.
Alternatively, you can launch the troubleshooter from the command prompt.
Launch Search and Indexing Troubleshooter from Command Prompt
- Open a new command prompt.
- Type the following command:
msdt.exe -ep WindowsHelp id SearchDiagnostic.
- Press the Enter key.
- Once it finish its work, restart the operating system.
Finally, there is a PowerShell script that can be used to resolve the issue.
Using a PowerShell Script
- Download the following PS1 script.
- Extract it to your desktop folder.
- Right-click the file that you saved, and select Run with PowerShell.
- If you are asked "Do you want to allow this app to make changes to your device?," select
- The PowerShell script resets the Windows Search feature. When the word Done appears, close the PowerShell window.
You may need to change the PowerShell execution policy to Unrestricted before running the script.
If the solutions above doesn't help to resolve the issue, you should uninstall the KB4512941 patch.