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-19T13:18:05+00:00

    Yes, but I've had inconsistent results.  In the end I just wrote a batch file to copy and reregister the previous version.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-08-19T13:02:15+00:00

    While it is good that many of us have found a 'solution' to counter the havoc caused by these updates, it cannot reverse the seeds of doubt sown in the minds of our clients about the stability of the software applications they have purchased. (or intended to).

    There has to be a forum available where we can be certain that the Microsoft development team is listening to the demand that the suite of tools used by them for testing their updates include software using the components available in MSComCTL and other such OCXs/DLLs.

    Recent such occurrences -

    mid-April : Component(s) affected - Listview

    mid-July : Component(s)  affected - Combobox

    mid-August : Component(s) affected - Listview

    This simply cannot go on.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-08-18T03:31:48+00:00

    After that I read your replies, I try to overwrite the new version 6.1.98.34 against 6.1.98.33, and re-registration typing like below on %systemroot%\system32 directory then I can load VB6 project source code with MsCommonControl OCX normally!

    %systemroot%\system32> regsvr32 /u MSCOMCTL.OCX

    %systemroot%\system32> regsvr32 MSCOMCTL.OCX

    (above operating system is 32bit Windows OS)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-08-18T03:21:22+00:00

    Hi,

    I encountered the same problem yesterday.

    My VB6 environment cannot load the MSCOMCTL.OCX ver.6.1.98.34.

    I was overwrited the previous revision 6.1.98.33 then it is all OK.

    I can get the previous revision file from Previous Version tab on the property MSCOMCTL.OCX file.

    Was this answer helpful?

    0 comments