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-17T19:26:02+00:00

    I'm having an issue with the TreeView control being broken after the update as well.

    Was this answer helpful?

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

    FYI: I was able to get by with a log off-log on instead of a full reboot...i know that doesn't help much but maybe it's worth something :)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-08-17T19:01:55+00:00

    John,

    I started off doing what you suggested (only un-registering and re-registering the file) and that procedure only worked on 1 of the computers we tried.  (We've also done just under 100 so far).

    I've found that swapping out the file with another version always works.

    So I'm glad your simple procedure worked for you, but it doesn't work for me but my procedure does.

    Darren

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-08-17T18:32:24+00:00

    Darren,

    Your steps are way unnecessary and overkill.  You're making it way too complicated.  You don't need to change out the version of the OCX, just register ithe new version.

    I've updated 84 computers for several custom applications that stopped working after the windows update, AND it worked fine with my steps above.  See my previous message above for the steps.

    -- John...

    Was this answer helpful?

    0 comments