Who are the Moderators? Anybody read this? VBA Macros are Broke, Formulas up 30% Slower.

RAINFIREReceived the info below from a friend. Microsoft Updates Catalog shows KB4512941 2019-08 **bleep** Update for 1903 x64 8/29/19 that purportedly contains the fix but when attempting to download it from the Catalog, generates the msg "the update is not applicable to your computer"

"No doubt, you recall the first wave of pain inflicted by the August 2019 patching regimen. Microsoft somehow managed to mess up Visual Basic (an old custom programming language), Visual Basic for Applications (for Office macros) and VBScript (a largely forgotten language primarily used inside Internet Explorer). Folks running applications in any of those languages would, on occasion, receive “invalid procedure call error” messages when using apps that had been working for decades.
Some companies’ commercial applications stopped working intermittently. More importantly, many large corporations’ internal custom programs turned belly-up.

The bug affects every single version of Windows – all the way from Win7 to Win10 version 1903. I think of it as Patching as a Keystone Kops Service.
If you’ve been following the details, you know that on Aug. 16, three days after Patch Tuesday, Microsoft released fixes for the bug in:

Win10 version 1709

Win7
Server 2008
Server 2008 R2
Server 2012
Server 2012 R2
Then on Saturday Aug. 17, we got fixes for:

Win10 1809

Win10 1703
Win10 1607
Win10 1507
Server 2016
Server 2019
And on Monday, Aug. 19, Microsoft released a fix for:

Win10 1803

As of today, Aug. 30, we still don’t have a fix for Win10 1903, the latest version of the last version of Windows. It’s not clear why, but I have a guess that Microsoft’s so wrapped up in beta testing Win10 1903 that it somehow fell through the cracks. We still don’t have the second August cumulative update for Win10 1903 – the one that’s common called “optional non-security,” with varying degrees of accuracy. And therein lies a tale."