After a short stretch in the Release Preview ring of the Insider Program, Microsoft discharged Windows 10 1903 form 18362.329 (KB4512941) to the generation ring – though as a discretionary update. In spite of the fact that the update bundles were the equivalent for the fabricates that were discharged to the Release Preview ring, just the bundle for the May 2019 Update was discharged to generation, since 19H2 is still in testing. In any case, incidentally, however, the total update fixed a lot of issues, a few clients aren’t having an incredible encounter.
Clients on Reddit started announcing that subsequent to introducing the most recent combined update, CPU utilization shot up to high numbers notwithstanding when the framework was inert and wasn’t being utilized. Most clients that revealed this presentation issue saw that the high CPU use originated from Cortana (explicitly the SearchUI.exe procedure as seen in the Task Manager). Moreover, the Search usefulness in the Taskbar to appears to have moved toward becoming non-practical for those that have hit this issue, with the hunt flyout turning clear when tapped on.
Interestingly, a few Insiders did log feedback about this issue in the Feedback Hub. However, since the build was not offered to Insiders for long enough before it went out to production, it seems the problem has slipped through. To add to it, the issue did not gather enough upvotes to gain attention. One would expect that the company would wait to gather more feedback for builds in the Insider Preview to be able to better address any such issues.
Microsoft has not officially acknowledged the bug yet. The KB article for this build did not list any known issues with the build either. While there are a few workarounds for fixing this problem such as tweaking certain registry entries, we recommend that you do so only if you are familiar with editing registry keys. Accidentally deleting or editing the wrong registry entries might lead to further issues.
Alternatively, Windows 10 Pro users can head to Settings -> Windows Update -> View Update History and uninstall the troublesome update. For those that haven’t installed the update yet, it is best to not do so. The next cumulative update should contain fixes from this build and should hopefully also fix the performance issues caused by Cortana. Whether the issues will indeed be fixed before the next round of Patch Tuesday updates is anybody’s guess.
Recent updates, in general, have been troublesome for Microsoft, with latest Surface Pro 6 and Book 2 firmware updates too causing CPU throttling issues. These hiccups are sure embarrassing, as the company explained its renewed emphasis on quality after the Windows 10 October 2018 Update debacle.