Latest Windows 10 Update Uses High CPU

A cumulative update to Windows 10 caused performance problems for some users. Windows 10 Build 18362.329, released with the cumulative update KB4512941, reported high CPU usage issues.

KB4512941 was released as an optional update on August 30th. Microsoft said in an article that the update would address numerous issues affecting Remote Desktop, Windows Sandbox, and other aspects of Windows 10. The company also announced that the Edge browser will support ePUB files, which are often used for eBooks, within the next few months.

Unfortunately, this is not the way Microsoft hoped. Windows Latest said many people have complained about high CPU usage issues after installing the update. Looks like the problem is in the search. Your virtual assistant searchuı.ex to is reported to have consumed 30-40% of the CPU and 150-200 MB of memory since the update to KB4512941, but these resources are completely wasted. The search window opened from the taskbar is having problems loading.

It is not clear why the search interface decided to become a processor enemy with the KB4512941 update, but it is clear that members of the Windows Insider Program reported these issues to Microsoft through the Feedback Center before the update was made public. It was revealed that these reports were not taken into consideration very much. Now people who install the optional update are sacrificing a significant portion of their CPU to the search interface.

Windows 10 updates are more of a problem than a recent problem:

Such issues have become normal in Windows 10 cumulative updates. An update in April caused performance issues; The May update corrupted Windows Sandbox, and the August update caused network problems on Surface devices. Other bulk updates failed to resolve the issues they were addressing. At this point, it is not unreasonable for people to wait a bit to install these cumulative updates.


Bluetooth Speakers Do Not Work After Last Update to Windows 10 (Solution)

Windows Latest says that some users have solved the problem by deleting a registry key, but it might be a better method to remove KB4512941 until Microsoft fixes it, unless one of the improvements in the update outweighs the performance.