Windows 10: vbscript.dll class_terminate bug since KB4524570 November 12, 2019 Windows 10 1903

Hi,


there seems to be a bug in vbscript.dll since cumulative update 4524570. When I create a instance of a class inside a class member function and assign it to a local variable the instance is not directly destroyed when this member function is left as it was before this update. See the following example code:


Option Explicit

Class CTest

Sub Class_Initialize

WScript.Echo Timer & ": CTest::Class_Initialize"

End Sub


Sub Class_Terminate

WScript.Echo Timer & ": CTest::Class_Terminate"

End Sub

End Class


Class CFoo

Sub Work

WScript.Echo Timer & ": CFoo::Work started"

DoWork

WSCript.Sleep 3000

WScript.Echo Timer & ": CFoo::Work done"

End Sub


Sub DoWork

WScript.Echo Timer & ": CFoo:oWork started"

Dim obj

Set obj= New CTest

WScript.Echo Timer & ": CFoo:oWork done, CTest::Class_Terminate should be called now without delay"

End Sub

End Class


Dim objFoo

Set objFoo= New CFoo

objFoo.Work

WScript.Echo Timer & ": objFoo.Work done"


When executing using cscript.exe the following output is generated:


80547,52: CFoo::Work started

80547,52: CFoo:oWork started

80547,52: CTest::Class_Initialize

80547,52: CFoo:oWork done, CTest::Class_Terminate should be called now without delay

80550,52: CFoo::Work done

80550,52: CTest::Class_Terminate

80550,53: objFoo.Work done



When executing with a prior version of vbscript.dll the output looks correct like this:


79971,76: CFoo::Work started
79971,76: CFoo:oWork started
79971,76: CTest::Class_Initialize
79971,76: CFoo:oWork done, CTest::Class_Terminate should be called now without delay
79971,76: CTest::Class_Terminate
79974,76: CFoo::Work done
79974,76: objFoo.Work done

I think this will lead to problems in any kind of code that count on the fact that objects referenced by local variables are destroyed when the scope is left.


The same bug is there on Windows 7 since KB4524535 November 12, 2019 Monthly Rollup.


Is there any reason for this change in this behavior? I hope there will be a bugfix for this soon...


Regards,

Steffen.

:)

 

November update kb4524570

I have 3 PCs - one running Windows Pro 10 1903 x32 (up to November 2019), one a dual boot which both used Windows 10 1903 pro x64 again up to November, and one running Windows 10 Enterprise 1903 x64.

The November update kb4524570 installed without trouble on the Enterprise system.

It installed OK on the dual boot secondary OS (not the default boot OS)

However on the Windows x32 and the default OS of the dual boot PC (x64), the update consistently fails to install with the error 0x800f081f

On both failed updates, the process gets to 20%, then jumps to 44%, then jumps to 100% and then fails.

NONE of the suggested fixes or remedies work, including re-installing the net.frameworks.

Both also shows the optional update to 1909, download it OK and again fails to install with the same error 0x800f081f

And this is the Windows update ???

 

KB4524570 Error 0x800f081f

November update kb4524570

I have 3 PCs - one running Windows Pro 10 1903 x32 (up to November 2019), one a dual boot which both used Windows 10 1903 pro x64 again up to November, and one running Windows 10 Enterprise 1903 x64.

The November update kb4524570 installed without trouble on the Enterprise system.

It installed OK on the dual boot secondary OS (not the default boot OS)

However on the Windows x32 and the default OS of the dual boot PC (x64), the update consistently fails to install with the error 0x800f081f

On both failed updates, the process gets to 20%, then jumps to 44%, then jumps to 100% and then fails.

NONE of the suggested fixes or remedies work, including re-installing the net.frameworks.

Both also shows the optional update to 1909, download it OK and again fails to install with the same error 0x800f081f

And this is the Windows update ???

 

Windows 10 update finishes on 12 November 2019 but on 1903

Hello,
A client of mine has updated his PC to 1903 (running winver confirms this) but he is getting messages saying that updates will cease on 12 November 2019. From a quick google that's when an earlier version of Windows 10 ends. I've attached a couple of photos he sent me.
Any help appreciated thanks.