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-20T08:02:34+00:00

    Thanks for the suggestions - will have a go on a "control" machine and see how it goes. We only found the update was a problem on Windows 7 (32 & 64 bit) - XP and Vista went through just fine.

    We tried replacing the OCX with earlier versions, but looking through the udpate notes it appears that MS have issued a "killbit" for earlier versions.

    System restore was the only work around that seemed consistently to work for us, followed by turning off critical updates.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-08-20T04:19:11+00:00

    I'm skeptical Microsoft cares about those of us using 10+ year old technology. :(

    I have got a patient ear and considerable time from Microsoft support, India re these issues.  However, we have to reach the 'ears' of the development team.  We cannot be sure that the support team 'escalates' the issue - while there is no reason to doubt that they will, how long this 'escalation' process takes is a mystery.

    For the mid-April issue I wrote about, support advised me that the development team needed 45 days to resolve the issue and temporarily archived the support ticket.  There was no resolution from Microsoft and I solved my specific problem by removing the Listviews from the designer and creating them at run time instead.  This solution lasted till the August 14th -17th  fiasco.

    They have to improve upon their suite of tools they use for checking the updates or

    if they are good enough, they ought to use them properly before they upload any updates.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-08-19T19:49:23+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. 

    HERE! HERE! Some years ago I spent considerable effort to circumvent this sort of DLL/OCX \*\*\*\* - this is the first time I've been caught for ages. I've only got around 30 PCs to manage: pity those on this thread who have 100+!!!  Dear Microsoft, sorry our clients won't pay for us to migrate all their legacy applications to C#5 and .Net 4.5... that's not real life

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-08-19T13:19:00+00:00

    I'm skeptical Microsoft cares about those of us using 10+ year old technology. :(

    Was this answer helpful?

    0 comments