From the problems caused by the deployment of Windows 10 October 2018 Update in Microsoft, the failures in the various updates that “put” on the market were taken very seriously. Not surprisingly, having a system like the Insider Program could theoretically help them prevent failures before they came to light.
From that moment of which we were already acquainted with the story, at Microsoft they took good note and decided to review their policy of launching updates, closely monitoring all that were going to leave to avoid draft errors to the user. That did not prevent cases such as the launch of a Build for internal testing or the most recent update: that could be giving more problems than desired.
A fault not located?
The Build 18362.329 launched by Microsoft under the KB4512941 patch a few days ago apparently and according to some users, is generating more failures than desired. A symptom, if so, that shows that the Microsoft filter is not as efficient as it should.
The companions of WindowsLatest have echoed the complaints that several users have made both on platforms such as Reddit and in the FeedbackHub. And they complain that their computers perform an exaggerated CPU consumption after updating to this patch.
Apparently, after this excessive behavior would be the file SearchUI.exe, part of Cortana, which would be monopolizing an exaggerated consumption of the CPU. The user who opens the thread speaks of up to 90%.
“I just installed KB4512941 and now Windows Search is broken and the Cortana process in the task manager takes 90% CPU. Am I the only one with this problem?”
Others on the other hand, affirm that the consumption, without reaching so much, is exaggerated, with average values close to 40% of the CPU and up to 150 MB of memory.
“Cortana is constantly running above 35% CPU usage and 150 MB of memory as reported by the Task Manager, for at least one day. Despite this fact, when using the Search button next to the Start menu, a dialog box appears that will not show any element when entering a search query, even after waiting several minutes ”,
In addition, the problem and always according to those affected, is that this ruling would have already been communicated to the American company before this Build was launched through the aforementioned Insider Program, which could indicate that Microsoft or did not see the warning or the ignored
Microsoft is aware of the complaints and for the multinational there seems to be no reason for the complaint and the Build 18362.329 works correctly without offering any problem. Is this your case and have you installed Build 18362.329?
In this case some users claim to have a solution that ends by ending up with a “Registry” key, which prevents the search from the Start menu from sending local search queries to Bing:
- Computer \ HKEY CURRENT USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Search
- Registration Name: BingSearchEnabled
- Record Value: 0
In the same way, another option may be to uninstall the update if you are experiencing an exaggerated consumption of your computer’s CPU. To do this, it is necessary to go to the “Configuration”, “Update and security” route and click on “View update history” within it. The next step is to use the “Uninstall updates” option by checking the KB4512941 update and then clicking on the “Uninstall” button .