none
COM problem with Windows Pos Ready 2009 after Windows Update rollout KB4134651 RRS feed

  • Question

  • An ActiveX EXE object exposes a public COM class with events (PippoAux.Connector
    returned as return value of a method, GetConnector, member of another ActiveX COM class of the same component (PippoAux.AppConnector)

    The call from a client to get the class object fails with run-time 430 (interface not found) after Windows Update rollout KB4134651

    Here is the sample code:

    --------------------------------------------------------------------------------------------------------------

    Dim WithEvents pc As PippoAux.Connector

    Private Sub Command1_Click()
    Dim pcloc As Object
    Dim pcc As PippoAux.AppConnector
    Set pcc = New PippoAux.AppConnector
    Set pcloc = pcc.Connect()
    Set pc = pcloc ' HERE ERROR 430
    pc.SayHello
    Set pcc = Nothing
    End Sub

    --------------------------------------------------------------------------------------------------------------

    Uninstalling the hot fix from Control panel, a previous version of oleaut32.dll (8/10/2006) is restored

    In this way the correct behaviour is restored.

    In some cases the uninstallation of the hot fix leaves unchanged oleaut32.dll and the problem still arises.

    Restoring manually the previous DLL fixes the problem too.

    Thanks for your support


    Friday, August 31, 2018 8:37 AM

Answers

All replies

  • Please Install the latest update KB4339291 ( July 2018 ) and it should resolve the issue. There were version discrepancy on the dependent dlls and oleaut32 failed to load.

      Please ack. once verified.

    Thanks

    Sunday, September 9, 2018 8:28 PM
  • Hi DamianoFasoli,

    I think this issue was introduced by the below KB/update (KB4074852).

    KB4074852:

    https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=35f9e6e8-e6aa-4293-85c3-d8781d8aac1f

    The KB/Update (KB4134651) with which you are seeing the issue superseded/replaced the update KB4074852.

    Can you please try the below steps and let me know if the issue still exists? I think it will, but please confirm.

    Steps:

    1. Un-install KB4134651

    2. Install KB4074852 from the above catalog location

    3. Check if the issue still exists?

    Regards,

    Shoeb

    Tuesday, September 11, 2018 11:10 PM
  • Dear Shoeb

    Yes, the problem still arises in this way.

    In fact, with out Hot Line, when KB4134651 was not deployed, we removed KB4074852 to fix the problem, and it succeeded.

    Now the same problem arises with KB4134651  or KB4134651-v2

    l noticed that

    4134651
    deploys
    oleaut32.dll 22/4/2018

    4134651-v2
    deploys
    oleaut32.dll 6/2018


    With
    oleaut32.dll  8/10/2016
    without
    KB4074852 and KB4134651
    there are no problems


    Thursday, September 13, 2018 10:37 AM
  • Hi Sudheer

    We have tried

    It does not resolve the problem

    This update was also deployed by Windows Update but has not solved the problem

    Thanks


    Thursday, September 13, 2018 10:38 AM
  • Thanks Damiano Fasoli. I think the version of the binary oleaut32.dll (8/10/2016) is 5.1.2600.7149 right? This version corresponds to KB3196718. BTW, there was another KB4018556 that was released after KB3196718 and before KB4074852 that updated the binary oleaut32.dll, can you please check if the KB4018556 has this issue?

    KB4018556:

    https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=1444f0a0-d0f1-4f91-a6a4-ee1f7f2b97df

     
    Thursday, September 13, 2018 7:30 PM
  • Hi Shoeb

    Yes, oleaut32.dll (8/10/2016) is 5.1.2600.7149, and with it there are no problems.

    After that, I installed KB4018556, really KB4018556-v2, from here:

    https://www.catalog.update.microsoft.com/Search.aspx?q=KB4018556

    and oleaut32.dll was replaced with the version 5.1.2600.7248 (24/5/2017)

    With it there are no problems too!

    So, maybe problems start from oleaut32 5.1.2600.7424 (6/2/2018) deployed with KB4074852

    Thanks for your support

    Friday, September 14, 2018 8:51 AM
  • Thanks Damiano. We are aware about the issues being caused by the update (KB4074852) and currently investigation around addressing the issues being caused by the update (KB4074852) is in progress.
    Monday, September 17, 2018 7:17 PM
  • Thanks Damiano. We are aware about the issues being caused by the update (KB4074852) and currently investigation around addressing the issues being caused by the update (KB4074852) is in progress.
    We have the same issue and our customers are badly impacted. Waiting for a solution soon.
    Tuesday, October 16, 2018 12:58 PM
  • Hi Shoeb

    Are there news about the matter?

    The problem is still open using Windows Update and also some customers of ours are badly impacted

    Thanks

    Wednesday, October 24, 2018 10:27 AM
  • Hi Damiano,

    KB4466388 should fix the issue, this KB (KB4466388) was released in November2018.

    2018-11
    Security Update for WES09 and POSReady 2009 for x86-based Systems (KB4466388)
     

    Thursday, January 10, 2019 12:37 AM
  • Hi Shoeb

    The fix is successful!

    Thank you

    Monday, January 21, 2019 9:31 AM