Microsoft has finally responded to complaints from some Windows 10 version 1903 users that recent cumulative update KB4512941 is causing CPU usage to surge to between 30% and 40% and in some cases 100%.
As ZDNet reported on Monday, Windows 10 users who installed the update believe the CPU spikes are caused by a problem in the Cortana process SearchUI.exe.
SEE: 20 pro tips to make Windows 10 work the way you want (free PDF)
The issues occurred after installing the KB4512941 update Microsoft released on Friday, August 30, which resolved an issue from an earlier update that broke apps using Visual Basic 6, VBA, and VBScript.
Microsoft fixed the Visual Basic issue in earlier versions of Windows 10, as well as Windows 7, and Windows 8 in mid-August, promising to fix it in version 1903 by the "end of August".
It met that timeline. But after testing KB4512941 with Windows Insiders, it also missed a small number of reports of this update causing the CPU issues that 1903 users are now reporting.
Besides CPU spikes, some users also report that the update breaks Windows Search.
But with the US Labor Day Holiday on Monday, Microsoft may have been caught off guard and only responded to user reports on Wednesday.
On the known issues page for 1903 and the page for KB4512941, Microsoft has now clarified that the conditions under which CPU spikes occur and Windows Desktop Search fails to return results.
"Microsoft is getting reports that a small number of users may not receive results when using Windows Desktop Search and may see high CPU usage from SearchUI.exe when searching after installing KB4512941," the company said.
"This issue is only encountered on devices in which searching the web from Windows Desktop Search has been disabled."
Microsoft estimates a resolution will be available in mid-September, so it will probably not be fixed by the upcoming Patch Tuesday on September 10, but by a subsequent optional cumulative update.
Some users report fixing the issues by editing registry keys, while others report that uninstalling the update resolves the problem.
However, Microsoft does not offer any workarounds to resolve the issue, suggesting that affected users just sit tight until the middle of the month.
More on Microsoft and Windows 10 updates
- Windows 10 CPU spikes? 1903 update brings fixes but also high usage issues
- Windows 10: We're now gearing up for 1909 with new throttled release, says Microsoft
- Microsoft: These Windows 10 updates fix broken Visual Basic apps but not for 1903
- Microsoft warns Windows 10 admins: No more patches for 1703 after October 9
- No more buggy Windows 10 updates? Microsoft makes it easier to flag early flaws
- Windows 10 recovery: Microsoft borrows Apple's Mac cloud reinstall feature
- Microsoft releases two new Windows 10 19H2 test builds
- A new look for Windows 10 Start menu: Live Tiles ditched in leaked preview build
- Windows 10 19H2: If you're on 1903, expect 'far faster' update, says Microsoft
- Microsoft starts testing Windows 10 19H2 in the Slow Ring
- Windows 10 updates: We're now using AI to push 1803 users to 1903, says Microsoft
- Windows 10 yields more secrets: Microsoft plan to split OS from shell takes shape
- How to delete the Windows 10 paging file on every shut-down TechRepublic
- Test Microsoft's Chrome-like Edge browser for Windows 10 CNET