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)
I would like to send MS a POLARIS missile up their proverbial for this incompetent update.
Not only have MS caused a great deal of consternation to your clients, i.e. us developers, but also now to our clients.
Your indolence, incompetence and arrogance in releasing this CR*P, untested update has caused untold damage to our reputations as serious developers using your products.
The personal animosity and heat I (and others in this forum) have taken as a result of this merde of a problem could have been avoided with your developers
a.) getting off their jumping bean bags or
b.) lunch time segway adventures for perhaps 5 minutes of serious testing.
Every industry that we developers subscribe to provide worthy solutions to has been decimated by your gross incompetence. TERRIFIC, WELL DONE, GIVE YOURSELVES ANOTHER BONUS...NOT!
I would welcome an audience with the kiddies and morons who put this together. Why is that a MULTI BILLION dollar organisation is silent while little developers like us in this forum fix up your upcox and take the heat for YOUR incompetence. Let's get those of you who are responsible online so we can provide you with free, fair and liberal character assessment of your efforts to date.
If you worked for any of us you would be out of a job.
Not a word of apology, not a fix in sight......
Says everything that needs to be said about your sub standard products.
If you have the bottle, send this to someone that cares in Microsoft. Anyone and all the way to the top.
This once great company has descended to mediocrity now and continues to plummet.
What a shame.
Right-clicking the batch file and selecting Run as administrator eliminates the need to turn off UAC.
I forgot to mention you have to right-click the batch file and select Run as administrator. This also eliminates the need to turn off UAC. I'll update my comment above.
@ProNet Systems
Make sure you're not running with UAC turned on otherwise you'll be virtualizing those commands and they won't actually take any effect. I wasted hours on that until I realized what was happening.
My solution is very similar to SLeepdepD's and is posted on my blog here:
http://darrenmyher.wordpress.com/2012/08/17/august-14-2012-mscomctl-ocx-security-update-problems/
Darren
