Newly installed Windows OS updates can sometimes get out of hand and create unexpected bugs during daily operations. In one such instance, updating Windows 10 to KB4512941 (Build 18362.329) has caused Cortana (SearchUI.exe) to consume CPU resources on many PCs. News of this bug has come from Windows Latest, which has received word of at least two recent cases where the problem was undoubtedly obvious. Microsoft, as you can see in this support document, has not yet acknowledged the problem, let’s fix it.

Screenshots of some Reddit users show that Windows 10 Update KB4512941 on some PCs has led to an unexpected, unnecessary increase in CPU usage even when the PC is idle. According to a Reddit user, restarting the PC doesn’t help. Additionally, the update disrupts Windows Search, leaving users looking at a blank white screen instead of their search results in the Start menu. Two temporary solutions have been identified so far and not from Microsoft.

Part of a screenshot shared by Redditor DefinitelyYou

Citing some answers posted by users on Reddit, Windows Latest offers the following solutions for users experiencing this problem. Deleting a registry key that prevents Start Menu Search from sending local queries from Microsoft to the Bing Search service can reduce CPU usage. To do this, you need to access the “Computer \ HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Search” path in the Windows registry (regedit.exe) and make an input. Regi value Of “0” Reggie’s name “BingSearch Enabled”.

If you do not want to risk playing with the Windows registry, you can always uninstall faulty updates. To do this, you can first open the settings (simultaneously press Win + I). Then you can go Updates and security And select View the history of change. In the following screen, you can select Uninstall the update. After that, you will be able to select the update in question (KB4512941) and click. Uninstall. During the uninstall process (and after the restart), you will not have any problems with Cortana and high CPU usage. It may be a while before Microsoft releases a patch for this issue.