The latest Patch Tuesday update from Microsoft included many crucial security fixes. Unfortunately, as Microsoft has now confirmed, it also burked some things.
If you haven’t applied that August 13 update and are running on Windows 10, Windows 8.1 or Windows 7, you may want to read this before you do.
Microsoft has confirmed a bunch of “known issues” with the August thirteen Windows update. Some, like the “black screen during the first logon after installing updates” issue, have hit users after previous updates. That can be filed in the annoying however ultimately not abundant to fret concerning folder: it solely impacts a “small number” of users and only the first time they logon after the update. Anything that impacts millions of users is a way more serious thing. And so, it’s that Microsoft has confirmed that this Patch Tuesday update does simply that.
“After installing this update, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an “invalid procedure call error,” Microsoft has stated.
Don’t assume that VB6 is not something that concerns you as a non-programmer Windows user. It almost certainly does if you, or your organization, use Microsoft Office. VBA apps along with with VB6 still power office scripts, macros and processes that are essential for several businesses.
The issue has been found to affect users of the following Windows versions:
Windows 7 and Windows Server 2008 R2, Windows 8.1 and Windows Server 2012 R2, Windows 10 version 1507, Windows 10 version 1607 and Windows Server 2016, Windows 10 version 1703,
Windows 10 version 1709, Windows 10 version 1803, Windows 10 version 1809 and Windows Server 2019, Windows 10 version 1903 and Windows Server 1903.
