This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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)
December 2012 - same problem.
We got the same again. Version 6.1.98.34 dated (2-May-2012) was re-introduced a few days ago with critical update KB2726929. We use up-to-date XP SP3.
The same thing happened this year in August.
On two of our PC's business critical applications stopped working with strange error messages about "unavailable objects on this machine". I lost 3 days over this problem back then, and an hour today.
Note that I have found this chat after I solved the problem myself, by system restore and selective Microsoft update, excluding --for once and for all-- the recent KB2726929 (and the KB2687323 backthen in August). In August I had to do this 8 times before I had found mscomctl as the culprit. This time in December there had been 11 critical updates, but the mscomctl immediately caught my eye, so I needed only one go.
Perhaps the simple here above described solution with unregister/logoff/logon/re-register would have worked, but I'm not going to try it out on these PC's. They will stay as-is.
My question is: what do I do with the other 60 PC's here that do not run this third party software? Shall I wait for them to face some other strange problem in some application? Or do I just execute a preventive unregister/register on all of them?
I have an app that is used by 1000's of users and it involves a lot of list views. When MS came out with MS12-027, we had to come up with a workaround because we had machines with the older ocx and newer ocx. Thankfully, even people with the newer ocx could use the file without issues as long as they didn't have to interact with the listviews. So, I added a check to not allow a person with the new ocx to go inside the dialog with the listviews. All was well until recently when MS **** decided to release MS12-060. This one goes 1 step further and now as soon as one enables macros, various errors come up (compile error, automation error, etc).
We've basically had it with the MSCOMCTL.OCX control. Does anyone know of some control that provides the same functionality as the listview (paid control is just fine)?
They seem to have extended the description of the "workaround" and also provided a "Fix it for me" section on http://support.microsoft.com/kb/2687441/en-us
Hi,
Has Microsoft released any official hotfix for this problem yet?
Thanks,
