Microsoft is currently investigating a new known Windows issue originating from a recently installed cumulative update, a bug that may cause some VB6, VBA, and VBScript apps to stop responding and throw an error.
Some of the applications made using Visual Basic 6 (VB6), the macros created with Visual Basic for Applications (VBA), as well as the scripts or the apps made using Visual Basic Scripting Edition (VBScript) may stop responding and will display an “invalid procedure call error” on affected systems.
The client and server platforms impacted by this issue are listed in the table below, together with the originating cumulative updates causing the problems after being installed:
|Windows 10, version 1903||Windows Server, version 1903||KB4512508|
|Windows 10, version 1809||Windows Server, version 1809/Windows Server 2019||KB4503327|
|Windows 10 Enterprise LTSC 2019||N/A|
|Windows 10, version 1803||Windows Server, version 1803||KB4512501|
|Windows 10, version 1709||Windows Server, version 1709||KB4512516|
|Windows 10, version 1703||Windows Server 2012 R2||KB4512507|
|Windows 10 Enterprise LTSC 2016||Windows Server 2012||N/A|
|Windows 10, version 1607||Windows Server 2016||KB4512517|
|Windows 10 Enterprise LTSC 2015||N/A|
|Windows 8.1||Windows Server 2012 R2||KB4512488|
|Windows 7 SP1||Windows Server 2008 R2 SP1||KB4512506|
Microsoft says on the issue’s Message center entry that the acknowledged is currently under investigation and that an update will be provided for to patch any impacted Windows devices when available.
At the moment all Windows versions seem to be affected from the information provided by Redmond related to this known issue.
BleepingComputer also tried reproducing the issue but failed to reproduce it. According to some user tips received by German blogger Günter Born, “The problem occurs when assigning arrays to VARIANT variables. Then the program crashes with Error 5,” while another one commented that “It seems to me that only applications that use ParamArrays in a certain way are affected.”
VBScript also disabled in Internet Explorer by default
In related news, Microsoft announced that it will disable VBScript by default in Internet Explorer for Windows 7, 8, and 8.1 on August 13th, as part of this month’s Patch Tuesday.
This measure is part of a Microsoft initiative which started back in 2017 with the end goal of disabling VBScript in Internet Explorer for a more secure user experience.
Microsoft also stated that VBScript has already been disabled by default in Internet Explorer 11 on Windows 10 for customers who have installed the July 9th cumulative updates.
However, this doesn’t indicate that VBScript will be removed completely since enterprises which to need it to run legacy apps can still toggle it on again with the help of the Registry or Group Policies.