[ad_1]
Microsoft has confirmed that it is currently investigating a second problem with its Windows 10 search service, apparently caused by a published patch to fix a previous CPU-related problem in the same service.
Reports reporting a problem related to the Windows 10 search subsystem, integrated with the company's Cortana Virtual Assistant platform, began to surface as a result of a security reminder released last month. Once installed, the fix brought the SearchUI.exe process on the selected systems to constantly drain processor resources, which accounts for up to 30 to 40 percent of the total CPU time of the system, even in the system. lack of active research. Embarrassing for Microsoft, and not just on its own, the blame had already been reported via the beta testing program of Windows Insiders – but, as for a serious data loss problem in the October 2018 update, it was ignored and the corrective made public. independently.
The good news for those affected by the update is that Microsoft has discovered the problem and released a patch, released earlier this week as part of Patch Update's regular update cycle. The bad news: the cure seems to be worse than the disease, users now complaining that the search is completely interrupted as a result of the patch.
After the installation of KB4515384, users reported that the search subsystem and the Start menu itself were not working properly. Frequent errors, including a useful warning stating that & # 39;your boot menu does not work.& # 39;
Strangely, the Microsoft technical support page for the update states that there is no known problem, which is contradicted in a separate document on the company's website. & # 39;Microsoft has received reports that some users have problems with the Start menu. [sic] and Windows Desktop Search,confirms the company. & # 39;We are currently studying and will provide an update as more information becomes available.& # 39;
In the meantime, Microsoft is providing people with a guide to resolving Windows Search issues, but does not guarantee that they will resolve it. The alternative, of course, is to uninstall KB4515384 – although this leaves users exposed to the risk of being attacked by various security flaws for which the fix has been designed.
[ad_2]
Source link