Security Update for mscomctl.ocx (KB2597986 MS12-060) August 2012 Updates: Listbox double-click no longer works

Anonymous
2012-08-15T12:25:26+00:00

After installing the August 2012 round of patches (MS12-060: Vulnerability in Windows common controls could allow remote code execution), an Access 2010 application using the Windows common controls Listbox no longer responds to a double-click.

The update installs MSCOMCTL.OCX 6.1.98.34 dated 6 Jun 2012.

Reverting to the previous version of the file (version 6.1.98.33, variously dated 7 or 14 Feb 2012 solves the problem.

I think this probably applies to Win XP as well.

Anyone else come across this? Any other issues with this update?

Windows for home | Previous Windows versions | Apps

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
Answer accepted by question author
Anonymous
2012-08-15T16:40:53+00:00

We had the problem and the way round it is to unregister mscomctl.ocx, log off, log back on and then register mscomctl.ocx.  The log off stage is important.  Without doing this unregistering and registering doesn't work.

This 'fix' has worked for us on PCs running Office 2003, 2007 and 2010 (Windows 7 64bit, Vista and XP)

Was this answer helpful?

7 people found this answer helpful.
0 comments

104 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-08-16T14:51:29+00:00

    FYI, My systems have ranged from Windows XP to Vista to 7. But all were running Word 2007. No 2010 run ins yet.

    But you CANNOT uninstall the patch via Add/Remove Programs. Working on a file I can distribute that will unreg ocx file, copy one from May, then register it.

    Ugh. Come on MS!!!!

    I found a solution for Office 2007, which worked on Windows 7 (32-bit) and Windows XP. There is a registry key which has a new version number after the update, but Microsoft 'forgot' to delete the old key.

    Beware: make a backup of your registry, no warranty is provided ;-)

    HKEY_CLASSES_ROOT\TypeLib{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}The systems had a 2.0 key and a 2.1 key. Only the 2.1 key had a subtree. After deleting the 2.0 key, my DOT-file worked again.

    Original credits go to:

    http://intellipoint.wordpress.com/2012/08/16/ms-zerstort-durch-kb2687441-die-kompatibilitat-von-mscomctl-ocx/

    Still working out the details on other Windows and Office versions.

    Ronald

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-08-16T14:51:25+00:00

    Looks like unregistering and registering mscomctl.ocx is working for us!!!

    Yeah!!

    here is the code:

    regsvr32 /u mscomctl.ocx

    regsvr32 mscomctl.ocx

    Many thanks - this is working for us also, after hours of stripping out recent updates only to find the one that caused it cannot be removed!!!

    Thanks again.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-08-16T13:55:26+00:00

    Solution: Delete the following Registrykey: HKEY_CLASSES_ROOT\TypeLib{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0

    Then register %SystemRoot%\system32\mscomctl.ocx again. A Key HKEY_CLASSES_ROOT\TypeLib{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.1 should be created for the updated Version of the mscomctl.ocx.

    Should work then.

    Best regards

    Jonas Saleh

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-08-16T13:37:27+00:00

    We found that if our problems users were on an Access 2003 runtime, they would still have issues after re-registering mscomctl.ocx. The only solution that permanently resolved the problem in those cases was to upgrade their runtime to Access 2010.

    edit: we are no longer replacing runtimes since deleting HKEY_CLASSES_ROOT\TypeLib{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0  resolves the problem.

    Was this answer helpful?

    0 comments