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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2012-08-17T18:03:08+00:00

    The solution that works for me 100% of the time is as follows:

    1. Disable UAC (if you don't these changes will not work) -- you can turn UAC back on later.
    2. Un-Register the 2012-06-06 dated version of MSCOMCTL.OCX
    3. Rename it to something else
    4. Put a replacement version -- any other version from any other computer that is not dated 2012-06-06 on this computer.

    a) register it

    b) immediately un-register it

    1. Rename that file or delete it.
    2. Rename the original file (the 2012-06-06 version) back to mscomctl.ocx
    3. Register that file

    This procedure has worked for me on all the machines I've tried it on (XP, Vista, Windows 7)

    I've put detailed steps in my blog:

    http://darrenmyher.wordpress.com/2012/08/17/august-14-2012-mscomctl-ocx-security-update-problems/

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-08-17T17:22:01+00:00

    Hi Ronald,

    I'm in the same boat as you.  I had to update 84 computers to fix this problem.  And you know if there are some computers that didn't get the Windows update yet then I'll have to go back later and update them unless Microsoft puts out another update to fix it beforehand.

    I found that there's a Windows Update Twitter account so I left a tweet there.

    I think that if enough developers complain they might get the idea.

    -- John...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-08-17T10:31:29+00:00

    Hi,

    Still not totally recovered from the stress of this second Microsoft disaster (MS12-027 in April en now MS12-060).

    Is there anyone who knows a way or e-mail address from microsoft, where I can best complain about these unnecessary issues with the mscomctl.ocx updates?

    I work at a small company, so we don't have Volume licenses or a Microsoft Sales rep who visits on a regular basis. But there must be a way how I (we?) can complain so that it is HEARD by Microsoft?

    I do think they should already be aware of the problems they cause lots of independent software developers, but there is nog indication of that visible online (f.i. in this thread).

    Ronald (Netherlands)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-08-17T08:36:54+00:00

    I would add that it's best to exit all programmes - not just Access applications - before doing this.  We've had a client where this failed because Quickbooks was open

    Was this answer helpful?

    0 comments