KB4512941 for Windows 10 version 1903

[Karlston]

KB4512941 for Windows 10 version 1903

The second cumulative patch for the current version of Windows 10, in this case Windows 10 version 1903, is always late to the party. Microsoft released updates for earlier versions of Windows 10 that it still supports about two weeks ago -- KB4512534 for Windows 10 version 1809 -- to fix a huge number of issues including the Visual Basic issue that was introduced on the August 2019 Patch Day.

 

The update KB4512941 for Windows 10 version 1903 and Windows Server version 1903 is available via Windows Update, Microsoft Update, the Microsoft Update Catalog, and Windows Server Update Services.

 

The update fixes the Visual Basic issue, the long-standing Preboot Execution Environment issue, the Sandbox startup issue, and the issue that caused devices from starting up under certain circumstances if configured to use MIT Kerberos realms.

KB4512941 for Windows 10 version 1903

• Support page
• Microsoft Update Catalog

The following issues are fixed in the update:

• Fixed a black screen issue when using Remote Desktop to connect to a PC running Windows 10 version 1903.
• Fixed a Windows Sandbox start up issue that threw the error "ERROR_FILE_NOT_FOUND (0x80070002)".
• Number of supported interrupts increased to 512 on devices with x2APIC enabled.
• Fixed a Trusted Platform Module issue that prevented some devices from being used for Next Generation Credentials.
• Fixed an issue that caused workstations to stop working when signing in using an updated user prinicipal name.
• Fixed a Windows Defender Advanced Threat Protection issue that prevented it from collecting forensic data when Registry-based proxy configurations were used.
• Fixed a Windows Defender Advanced Threat Protection compatibility issue.
• Fixed a rare issue that affected the driver mssecflt.sys which caused the error message STOP 0x7F: UNEXPECTED_KERNEL_MODE_TRAP.
• Fixed an issue that could lead to excessive memory usage in Windows Defender Advanced Threat Protection.
• Detection accuracy of Microsoft Defender ATP Threat & Vulnerability Management.
• Addressed an issue that prevented the loading of third-party binaries from Universal Windows Platform applications.
• Fixed an issue that caused devices to have truncated device names when names were assigned to the devices automatically using Autopilot provisioning.
• Fixed an issue that caused the production description of Windows Server 2019 to be incorrect when using slmgr /dlv.
• Fixed a reporting issue in Windows Management Instrumentation.
• Fixed a compound documents copying and pasting issue between applications that hosts the RichEdit control and other apps.
• Fixed an issue that prevent some games from using Spatial Audio capabilities.
• Fixed an issue that caused the cursor not to appear when selecting elements using touch.
• Fixed an issue that caused the names of unsupported applications to appear in Start with default text, ms-resource:AppName/Text, after upgrading.
• Fixed an issue that prevented the PIN prompt to appear in Internet Explorer.
• Fixed a DRM files download issue in IE and Microsoft Edge.
• Improved compatibility and user experience of certain Win32 apps so that they work with Windows Mixed Reality.
• Addressed an issue with LdapPermissiveModify  requests.
• Fixed the Preboot Execution Environment issue.
• Fixed the MIT Kerberos issue.
• Fixed the Visual Basic issue.

Microsoft lists no known issue on the update page. Günter Born discovered an issue that causes high CPU load. You can check out his analysis and workaround here.

 

 

 

Source: KB4512941 for Windows 10 version 1903 (gHacks - Martin Brinkmann)

[Karlston]

The second August patch for Win10 1903 shoots one core up to 100% utilization

Is your machine red-lining after installing today’s KB 4512941, the second August cumulative update for Win10 version 1903?

 

Günter Born has a workaround.

 

The problem is caused by a corrupt cache in

c:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\cache\

The solution is to replace that folder with an old, correctly functioning version. Born has links.

 

There’s a reason why I haven’t flipped over to MS-DEFCON 3 or 4 just yet. This patch, in particular, hasn’t been sufficiently tested.

 

 

 

Source: The second August patch for Win10 1903 shoots one core up to 100% utilization (AskWoody - Woody Leonhard)

[Karlston]

Microsoft appears to have shipped a buggy Windows 10 update even after negative Insider feedback

Two days ago Microsoft released KB4512941, after only a day of testing in the Release Preview Ring. At the time the update had no known issues, but it appears that this was merely because Microsoft did not look hard enough.

WindowsLatest reports that a number of users are complaining of high CPU usage by SearchUI.exe, part of Cortana, via the FeedbackHub and Reddit (1, 2).

 

 

The users complain of SearchUI.exe taking 30-40% of CPU usage and despite this being unresponsive.

 

“After installing KB4512941 (OS Build 18362.329) the pop-out window with the search results stays blank, SearchUI.exe is constantly using CPU and ~200MB of memory,” a user documented the problem on Microsoft’s Feedback Hub.

 

“Cortana is consistently running above 35% CPU usage and 150 MB memory as reported by Task Manager, for at least one day now. Despite this fact, using the Search button next to the Start Menu pops up a dialog that will not display any items upon entering any search query, even after waiting for several minutes,” another user complained about the CPU usage on Feedback Hub.

 

More worryingly, it appears Windows Insider testers had already picked up and reported the issue in the Feedback Hub, but that Microsoft failed to respond to this.

 

 

Regular readers will know this is reminiscent of the data deletion bug in the October 2018 Update, which had also been picked up by testers but ignored by Microsoft. More concerning is that Microsoft has said they would make changes to their process to pick up issues which did not have a lot of upvotes but which would still cause issues for end-users. These do not appear to be working.

 

If you're one of those affected the simplest fix may be to uninstall the update. To do this:

• Hit Windows+I to open the Settings app.
• Click the “Update & security” option.
• On the Update & security screen, click the “View update history” option.
• On the next screen, click the “Uninstall updates” link.
• Select the update (KB4512941), and then click the “Uninstall” button.

At the time of writing “Microsoft is not currently aware of any issues with this update.“

 

 

 

Source: Microsoft appears to have shipped a buggy Windows 10 update even after negative Insider feedback  (MSPoweruser)

[Kalju]

It must announce, with deep sorrow that something is wrong.
I currently have three different computers (different companies, different computers and also very different ages), all with KB4512941 installed, but there is no problem. No such a problem again! I'm so sad, what I should do? What if there is no such problem again?

[Karlston]

9 minutes ago, Kalju said:

No such a problem again! I'm so sad, what I should do? What if there is no such problem again?

 

You should be grateful that Microsoft's bugs don't affect everyone.

[Jerry]

I cant install that update I get error code 0x800f081f which sounds like its a good thing 

[Kalju]

18 minutes ago, Jerry said:

I cant install that update I get error code 0x800f081f which sounds like its a good thing 

• You have no reason to rejoice.
• This indicates that your computer is having problems. You should look for the cause and eliminate it before it is too late.
• There were no problems installing this update, but once it has beeninstalled. But problems may occur after uninstalling. 
• So, I'd rather be careful with removal, especially if there is no backup copy of the previous files, which this time was quite large, quite a few GB. Can't remember exactly, but more than 2GB anyway.

[Radpop]

9 hours ago, Karlston said:

The users complain of SearchUI.exe taking 30-40% of CPU usage and despite this being unresponsive.

 

Yes, I got hit of this. After update searchindexer.exe CPU usage was 40-50 % and also big watts was consumed. Search box was blank with blue dots running in upper corner. 😅

 

I didn't remove KB4512941. Fix was to delete registry key 'Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search' and then reboot computer. Search is working now, watts and CPU percents are back normal. 😁

[Kalju]

I haven't made any changes there.
The only thing I've done (I've posted it also before) is this:

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search]
"AllowCortana"=dword:00000000

 

[steven36]

I fixed mine for good  When i installed Red Stone 3  using windows defender and using Windows 10 Firewall control it made my PC crawl and the fix was disable windows defender and it ran OK.  Windows 10 was a lot of work  getting it were it was usable for me for them to just push out a update  6 mths latter and have to start over . So when Redstone 4 came out  i booted  into Linux and got my Windows 8.1 key out the BIOS, Then wiped windows 10 off my PC  for good then installed Windows 8.1 and  Ubuntu 18.04  LTS  That was  April  2018 and  I never had to reformat again or had any problems .

 

It was once said People use software on  and OS , if If people start talking about and OS all the time instead of the software that used on the OS it means there something is wrong with the OS.  That pretty much  explains Windows 10 and all the  Trouble Shooting articles  posted since June 2015.  Computers are meant to be used  and not have to worry about Trouble Shooting  every time there's a Windows update .  KB4512941 was a bug fix for them breaking visual basic ,  because of  a update they pushed to patch a wormhole . they done caused 2 sets of bugs trying to patch one .

[zanderthunder]

On 9/2/2019 at 4:25 AM, Karlston said:

Microsoft appears to have shipped a buggy Windows 10 update even after negative Insider feedback

Two days ago Microsoft released KB4512941, after only a day of testing in the Release Preview Ring. At the time the update had no known issues, but it appears that this was merely because Microsoft did not look hard enough.

WindowsLatest reports that a number of users are complaining of high CPU usage by SearchUI.exe, part of Cortana, via the FeedbackHub and Reddit (1, 2).

 

 

The users complain of SearchUI.exe taking 30-40% of CPU usage and despite this being unresponsive.

 

“After installing KB4512941 (OS Build 18362.329) the pop-out window with the search results stays blank, SearchUI.exe is constantly using CPU and ~200MB of memory,” a user documented the problem on Microsoft’s Feedback Hub.

 

“Cortana is consistently running above 35% CPU usage and 150 MB memory as reported by Task Manager, for at least one day now. Despite this fact, using the Search button next to the Start Menu pops up a dialog that will not display any items upon entering any search query, even after waiting for several minutes,” another user complained about the CPU usage on Feedback Hub.

 

More worryingly, it appears Windows Insider testers had already picked up and reported the issue in the Feedback Hub, but that Microsoft failed to respond to this.

 

 

Regular readers will know this is reminiscent of the data deletion bug in the October 2018 Update, which had also been picked up by testers but ignored by Microsoft. More concerning is that Microsoft has said they would make changes to their process to pick up issues which did not have a lot of upvotes but which would still cause issues for end-users. These do not appear to be working.

 

If you're one of those affected the simplest fix may be to uninstall the update. To do this:

• Hit Windows+I to open the Settings app.
• Click the “Update & security” option.
• On the Update & security screen, click the “View update history” option.
• On the next screen, click the “Uninstall updates” link.
• Select the update (KB4512941), and then click the “Uninstall” button.

At the time of writing “Microsoft is not currently aware of any issues with this update.“

 

 

 

Source: Microsoft appears to have shipped a buggy Windows 10 update even after negative Insider feedback  (MSPoweruser)

 

According to a Reddit user (4wh457), there's a workaround to fix the high CPU issue after installing the optional Win 10 KB4512941 update. 

 

 

This is what it looks like in action, explained in this video: https://streamable.com/skzcf

 

Some users reported that this workaround fixes the problem. You might can try to test the workaround and feedback to the original developer through Reddit.

 

Anyway, let us hope that Microsoft fix this bug before usual Patch Tuesday comes.

 

Update: Microsoft has finally acknowledged the high CPU usage bug caused by the optional update. Hope they can fix it before the mandatory Patch Tuesday comes.