Microsoft’s mega Patch Tuesday update also brought a fix for a several-week-old Cortana bug that was causing high CPU pain for Windows 10 version 1903 users.
- In nostalgic move, Microsoft brings back PowerToys for Windows 10
- FAQ: How to manage Windows 10 updates
- Buying a Windows laptop? Five must-have features for my next notebook
- The Best Antivirus of 2019 to Protect Windows 10 (CNET)
- Windows 10 not working after latest upgrade? Here are the bugs to look out for (TechRepublic)
Microsoft last week finally acknowledged user complaints about the Cortana process SearchUI.exe causing abnormally high CPU usage.
Complaints rolled in after users installed the KB4512941 update that Microsoft released on Friday, August 30, to address bugs from a previous cumulative update that were lingering on in version 1903.
Microsoft promised that a fix for the high CPU usage would be provided by mid-September, but the company actually delivered it a little earlier, as part of its huge September Patch Tuesday update.
“Addresses an issue that causes high CPU usage from SearchUI.exe for a small number of users. This issue only occurs on devices that have disabled searching the web using Windows Desktop Search,” Microsoft said in the security update KB4515384 released yesterday.
Still, a small number of Windows Insiders had reported the same issue through the Feedback Hub in preview testing of the buggy update, which Microsoft missed despite recent efforts to improve its detection of narrowly reported issues
The Patch Tuesday update address two zero-day elevation of privilege flaws that were under attack already. The update included 80 security fixes.
Additionally, Microsoft patched two remote code execution bugs in the Remote Desktop Protocol. However, these don’t appear to be as dangerous as the recent BlueKeep and DejaBlue vulnerabilities, which could be used to create a wormable exploit to automatically infect vulnerable machines on the same network.
“Unlike BlueKeep and DejaBlue, these members of the Blue Bug Group are all client-side. An attacker would need to convince someone to connect to their malicious RDP server or otherwise intercept (MITM) the traffic,” said Dustin Childs from Trend Micro’s Zero Day Initiative.
“It’s good to see these issues patched, but they don’t carry the urgency of the recent wormable bugs.”
More on Microsoft’s Windows 10 updates
- Windows 10 1903: Buggy update slows PCs, breaks Desktop Search, says
- 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
- Microsoft Registry Fix - Guaranteed to Work!
- 4 Benefits of a Microsoft Registry Fix Program Uncovered
- 4 Important Reasons to Get a Microsoft Registry Fix Program Immediately
- Microsoft Registry Fix in Less Than 10 Minutes
- Fix Windows Registry Error With A Registry Cleaner
- How to Fix Windows Update 0x80072ee2-0x80072efd Error Code
- Choose to Fix Window Registry Challenges Now - A Step-By-Step Guide
- Fix Windows XP Error in Few Easy Steps
- How to Choose a Registry Fix Windows in 5 Easy Steps
- How to Fix Windows Error - Sick and Tired of Seeing Windows Error Messages?