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

Anonymous

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?

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

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)

0 comments

104 additional answers

Anonymous

2012-08-24T16:32:27+00:00

We found that the recommended unregister/register approach didn't work in some (most) cases. More details in this paper we just published:Fixing the Microsoft Windows Common Control Library (MSCOMCTL.OCX) Security Update

Luke,

Thank you for publishing.

Just to document, after I installed SP3 and some other patches I was having a problem with the MS Access External Data - Outlook Folder wizard popping an error "object or class does not support the set of events"

Uninstalling SP3 didn't work, I uninstalled/reinstalled Office 2007 and it worked fine. As soon as I installed SP3 the error came back. After doing a repair off the Office disk the error went away and the Windows Update app listed a number of updates were listed. I installed one at a time until the error came back, which was caused by KB2687441.

I followed your procedures in Fixing the Microsoft Windows Common Control Library (MSCOMCTL.OCX) Security Update and it started working as advertised.

Thank you again!
Was this answer helpful?

0 comments No comments
Anonymous

2012-08-24T12:39:09+00:00

We found that the recommended unregister/register approach didn't work in some (most) cases. More details in this paper we just published:Fixing the Microsoft Windows Common Control Library (MSCOMCTL.OCX) Security Update
Was this answer helpful?

0 comments No comments
Anonymous

2012-08-24T09:37:05+00:00

This is allmost the worst thing ever happed: we have to give solution on it for all our clients (more than 1000). They all contact us at the same time. I don't understand such severe update from Microsoft ! We hope Microsoft will quickly arrange a justification with a new update for instance, ... .
Was this answer helpful?

0 comments No comments
Anonymous

2012-08-22T20:54:56+00:00
We just published a detailed paper describing this issue, some of the symptoms, and how to address it entitled: Fixing the Microsoft Windows Common Control Library (MSCOMCTL.OCX) Security Update

It details how the suggestion in the KB article (MS12-060: Description of the security update for 2007 Office system: August 14, 2012) fails, and a workaround that involves:
- Installing an older version of the control
- Registering it
- Unregistering it, and
- Re-registering the updated one
What a hassle. Hope this helps.
Was this answer helpful?

0 comments No comments