August goes to be a dangerous patching month.

We’re monitoring down credible stories of the Server 2012 R2 Month-to-month rollup breaking RDP logins, a battle between the Win10 1903 cumulative replace and final month’s model of Outlook 365, confusion about Win7 patches being branded as “IA64 solely,” coping with the lack of telemetry (!) within the August Win7 Safety Solely patch, a lot mayhem making an attempt to put in SHA-2 signed patches (together with the Win7 Month-to-month Rollup) on methods utilizing Symantec Endpoint Safety, even extra confusion over the distinction between Symantec Endpoint Safety and Norton Safety Suite, and many the standard set up failures and rollbacks.

I’m personally fuming about loads of press-generated humbug about the necessity to set up all of the August patches immediately, to guard towards DejaBlue (also called BlueKeep II, III, IV and V). The Hen Littles are successful the clickbait wars. There’s nonetheless no publicly available exploit for BlueKeep, fer heaven’s sake, and there isn’t any manner the DejaBlues are an “quick, viral” risk.

Whereas all of that was swirling round, Microsoft quietly launched an replace to the “Identified points” part of each August Home windows patch. It says:

After putting in this replace, functions that had been made utilizing Visible Fundamental 6 (VB6), macros utilizing Visible Fundamental for Purposes (VBA), and scripts or apps utilizing Visible Fundamental Scripting Version (VBScript) might cease responding and chances are you’ll obtain an “invalid process name error.”

That’s a shocking error for Microsoft’s ubiquitous (if historical) programming language.

Much more spectacular: I can’t discover impartial stories of the bug. The German-language deskmodder.de web site mentions the “Identified points” itemizing, however has no particulars. I am unable to work out the place the error got here from, how widespread it may be, why it seems, or if it may be labored round, besides by uninstalling the patch. 

“Invalid process name” errors in VB are a dime a dozen. What occurred on this month’s Home windows patches to set off them? And why wasn’t the bug caught earlier than it was launched?

One final query. Aren’t you glad you delayed updating this month?

If you recognize, tell us on AskWoody.com

Copyright © 2019 IDG Communications, Inc.