“This week’s Windows updates fix critical ‘wormable’ [Bluekeep] flaws but may also break Visual Basic apps, macros, and scripts,” warns ZDNet:
“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 says. The issue affects all supported versions of Windows 10, Windows 7, Windows 8.1, and their corresponding server versions. “Microsoft is presently investigating this issue and will provide an update when available,” the company said.
Microsoft didn’t offer an explanation for the problem but it did flag earlier this month that it will move ahead with sunsetting VBScript, by disabling it in IE11 by default via an update in this week’s patch. “The change to disable VBScript will take effect in the upcoming cumulative updates for Windows 7, 8, and 8.1 on August 13, 2019,” Microsoft warned in a blog post. The change brought these versions of Windows in line with Windows 10. However, it’s not clear that the issues under investigation are related to this measure. Regardless of the cause, the error could be a hassle for organizations that rely on Microsoft’s various incarnations of Visual Basic…
In a blog post shared by Slashdot reader CaptainDork, Microsoft warned that “any future malware that exploits these could propagate from vulnerable computer to vulnerable computer without user interaction.”
“The affected versions of Windows are Windows 7 SP1, Windows Server 2008 R2 SP1, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, and all supported versions of Windows 10, including server versions.”
of this story at Slashdot.
Source:: Slashdot