Share via

KB3139940 breaks VB6 application with error about MSCOMCTL.ocx

Anonymous
2016-03-14T20:47:00+00:00

We recently installed KB3139940 on some of our Windows 7 x64 systems and ran into a strange issue.

One of our VB6 application suddenly stopped working with the following error:

Failed to load control 'ImageList' from MSCOMCTL.OCX.  your version of MSCOMCTL.OCX may be outdated.  Make sure yo uare using the version of the control that was provided with your application.

I have compared the file version from a known good system and the version matches (6.01.9846) so I don't think it is a problem with the OCX file.

Removing this update allows the program to work again.  I have looked online and found instructions about unregistering it before copying it over and about removing a registry entry ([HKEY_CLASSES_ROOT\TypeLib{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0]) and neither seemed to have any positive effect.  I tried removing that key completely (2.0, 2.1 and 2.2) and then re-registering the OCX file and same problem.

Any thoughts on what I can try next?

Also, sorry if I posted this in the wrong location, I thought it fell under windows update.

Thanks

Brian

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

21 answers

Sort by: Most helpful
  1. Anonymous
    2016-04-07T12:52:27+00:00

    I agree with your comments about OLE32 or OLEAUT32 being responsible.

    We now know its the images that are the culprit. Concerning our latest problem with error 5003, we traced it down to a DBGRid component, but the problem wasn't with the grid itself, as putting a new one on the form didn't  trigger the error. There was an icon attached to the DBGRid in its DragIcon property. Because of the way VB embeds images, it was impossible to say what size the original icon was, but pointing to a new icon or removing it altogether cured the problem.

    To recap, although our original problem, and that of many others here was with an imagelist, it's not the component itself that's at fault but rather the type/size of image that's associated with it. This has been mentioned by other contributors and is definitely the case. I've passed the info on to our latest contact at Microsoft.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2016-03-15T15:42:30+00:00

    Hi,

    Thank you for the update.

    Please do let us know if you need any other assistance with Windows in future. We will be happy to assist you.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-03-15T14:11:36+00:00

    We are connected to a domain network.

    We found a potential solution but I am not sure it is a good permanent solution:

    we upgraded one of our developer boxes to have that KB installed and then recompiled the code afterwards.  After we did this, the program appears to function properly.

    The reason I am not sure if this is a good permanent solution is VB6 IDE is not supported in windows 7 and that update applies to windows 7 but not XP and older.  So we are working in an unsupported setup right now.

    EDIT - posting on technet right now.

    Thanks

    Brian

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-03-15T13:03:43+00:00

    Hi,

    Thank you for posting your query on Microsoft Community.

    I would like to know some information.

    1. Are you connected to a domain network?

    If you are connected to a domain network, I would suggest you to re-post your query on TechNet Forums as we have experts working on such type of issues and to help you in a better way.

    Refer to the link.

    https://social.technet.microsoft.com/Forums/windows/en-US/home?category=w7itpro

    Hope this information helps. Please let us know if you need any other assistance with Windows in future. We will be happy to assist you.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-03-15T11:39:31+00:00

    We have the same issue. Have contacted MS support (via Twitter initially). Awaiting their phone call as we speak. This must be a widespread problem.

    Was this answer helpful?

    0 comments No comments