[German]On August 16, 2019, Microsoft released updated updates for Windows to fix issues with VB6, VBA, and VBScript. On August 17, and 19, 2019 more updates for Windows 10 has been released.
What's the point?
With the updates of August 13, 2019, Microsoft cut VBScript support in Internet Explorer. A short time later, users noticed issues with Visual Basic support (VB6, VBA and VBScript). Corresponding modules caused errors in certain constellations. I had mentioned this in the blog post August 2019 Updates: Issues with VB6, VBA and VBScript.
Microsoft releases new Updates
Blog reader EP has left this comment (thank you) mentions that Microsoft released updated updates for Windows on August 16, 2019 which are supposed to fix the issues with VB6, VBA and VBScript.
- KB4517297 for Windows 7 und Windows Server 2008 R2,
- KB4517301 for Windows Server 2008 SP2,
- KB4517298 for Windows 8.1 und Windows Server 2012 R2
- KB4512494 for Windows 10 V1709
For other Windows 10 builds (1809, 1903) Microsoft has partially released new updates on August 17, 2019 with VBA fixes.
- KB4512534 for Windows 10 Version 1809
- KB4512495 for Windows 10 Version 1607
- KB4517276 for Windows 10 Version 1507
Addendum: On August 19 2019 Microsoft also released an update for Windows 10, that fixed the VB6, VBA and VBScript issue.
- KB4512509 for Windows 10 Version 1803
Now the updates for Windows 10 Version 1903 is still missing. Note also the known issues documented within the linked support articles. I also received user feedback, that the issue isn't completely fixed.
Cookies helps to fund this blog: Cookie settings
Pingback: More fixes for the VB/VBA/VBScript bugs in this month’s patches @ AskWoody
MS has released the KB4512509 update for Windows 10 version 1803 Mon. 8/19, which includes the VBA/VB6 fixes:
that now leaves only v1903 w/out the VBA/VB6 fixes
1903 users will now get the VB fixes only in the RP ring 8/21 with KB4512941 (build 18362.325). it may get a public release either by the end of this week or the start of next week.
In some scenarios this breaks Printing from 32bit Applications…
To Easily Reproduce:
Launch 32bit Notepad
Attempt to Print
The process sits and spins, killing splwow64 brings him back but that doesn't help us.
Thank you , it helped