Visual Basic issues in Windows August 2019 Updates
Microsoft added a new known issue to all cumulative updates that it released for Windows client and server versions in August 2019.
The issue states that applications may stop responding if they use Visual Basic 6, Visual Basic for Applications, or Visual Basic Scripting Edition. Apps may throw the error "invalid procedure call error" in that case.
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."
Cisco XenApps appear to be affected by the issue according to a post on Born's site.
All cumulative updates that Microsoft released appear to be affected by the issue. The known issue has been added to release pages for all supported versions of Microsoft Windows:
- Windows 7 and Windows Server 2008 R2: KB4512486 and KB4512506
- Windows 8.1 and Windows Server 2012 R2: KB4512488 and KB4512489
- Windows 10 version 1507: KB4512497
- Windows 10 version 1607 and Windows Server 2016: KB4512517
- Windows 10 version 1703: KB4512507
- Windows 10 version 1709: KB4512516
- Windows 10 version 1803: KB4512501
- Windows 10 version 1809 and Windows Server 2019: KB4511553
- Windows 10 version 1903 and Windows Server 1903: KB4512508
Microsoft notes that it is investigating the issue currently and that it plans to distribute an update as soon as the issue is resolved.
Microsoft revealed plans last month to disable VBScript by default on machines running Windows 7, Windows 8.1, Windows Server 2008 R2 or 2012 R2. The company disabled VBScript on machines running Windows 10 a month early already.
Microsoft has not revealed additional information about the issue; it is likely that it is related to the announced disabling of VBScript on all versions of Windows.
Organizations -- and the bug affects organizations for the most part -- who run apps or tools that require a Visual Basic flavor may want to block the August 2019 updates until the issue is resolved. Those who have installed the patches already can uninstall the Windows Updates to resolve it.
An issue that affects all different versions of Visual Basic on all supported versions of Windows, that is a major one. Microsoft really needs to rethink testing and evaluating of updates to avoid major breakage like this from happening especially if it concerns in-house products like Visual Basic.
Now you: what is your take on this issue?Advertisement