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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2012-08-15T15:57:50+00:00

    We fixed it by doing the following in our DOT file that had the reference:

    1. Removed the reference to MSCOMCTL.OCX
    2. Saved DOT file.
    3. Added new reference to MSCOMCTL.OCX
    4. Saved DOT file.

    Did not even have to Compile. Just changing the reference seems to have made it compatible with the newest OCX build.

    BIZARRE!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-08-15T15:57:59+00:00

    Beat me to it! :-)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-08-15T16:09:16+00:00

    What sucks is this did NOT work for us. So you guys were able to just unregister the updated OCX (from the overnight update) and re-register it?

    I tried that on at least 5 machines. 32bit, 64bit, XP, Win7, with and without Admin Privs. Didn't work for us.

    THANKS AGAIN MS!!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-08-15T16:10:22+00:00

    I have fixed enough computers now by unregistering and registering the mscomctl.ocx component that I've gone ahead and issued a general fix to all my customers.  I will report back to this thread if any report that it doesn't work and what their symptoms and installed updates might be.

    Was this answer helpful?

    0 comments