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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2012-08-20T11:08:15+00:00

    Please read all the posts in this thread.  You will see details of fixes posted by me and others that work where the simple unregister/register don't

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-08-20T16:15:44+00:00

    Ok lets come up with a consensus and a summary of the solution to this issue.

    First and foremost, evidently there is no single solution that works for all, I'm assuming it depends on the functionality of the mscomctl.ocx the affected application is using and the version the old ocx was prior to the Microsoft Update.

    Now, it has to be said you always have the option to run a System Restore and turn off Automatic Updates, however if you can't restore or automatic updates is a must, then you have to start dealing with the registering un-registering remedy.

    Before you try anything keep in mind that in Windows 7 (and alike i.e. Vista, Server 2008, etc) you must run the script in elevated rights as administrator.

    Lets start:

    First run this script:

    regsvr32 mscomctl.ocx /u

    regsvr32 mscomctl.ocx

    That alone fixed it for many.

    If this didn't solve it:

    Run only this line:

    regsvr32 mscomctl.ocx /u

    Log off/on

    Run this line:

    regsvr32 mscomctl.ocx

    If this didn't solve it:

    Run only this line:

    regsvr32 mscomctl.ocx /u

    Reboot

    Run this line:

    regsvr32 mscomctl.ocx

    You may also try to log off/on or reboot after the running the second line

    If it still didn't solve it.

    You'd have to get a hold of the old mscomctl.ocx version Microsoft Update replaced, either via a backup or online, or a friend, somehow get it.

    Place the old ocx in a random folder NOT in the system folder where all the dll's reside (i.e. C:\Windows\System32), for example c:\randomfolder\mscomctl.ocx (old version)

    Then run the following script:

    regsvr32 mscomctl.ocx /u

    regsvr32 mscomctl.ocx

    regsvr32 c:\randomfolder\mscomctl.ocx

    Like the previous solutions you might have to log off/on or reboot between the un-register and register and after the last line

    I believe this covers all remedies you may see different variations but its all over kills, in my honest opinion, and won't do anything more.

    Good luck!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-08-21T13:40:10+00:00

    On our Win7 (x86) Clients we had to delete the following Registrykey:

    HKEY_CLASSES_ROOT\TypeLib{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.0

    as this is the reference to the old mscomctl.ocx. After removing we had to register the new mscomctl.ocx what created the Key HKEY_CLASSES_ROOT\TypeLib{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.1

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-08-21T15:49:19+00:00

    Ok lets come up with a consensus and a summary of the solution to this issue.

    First and foremost, evidently there is no single solution that works for all, I'm assuming it depends on the functionality of the mscomctl.ocx the affected application is using and the version the old ocx was prior to the Microsoft Update.

    Now, it has to be said you always have the option to run a System Restore and turn off Automatic Updates, however if you can't restore or automatic updates is a must, then you have to start dealing with the registering un-registering remedy.

    Before you try anything keep in mind that in Windows 7 (and alike i.e. Vista, Server 2008, etc) you must run the script in elevated rights as administrator.

    Lets start:

    First run this script:

    regsvr32 mscomctl.ocx /u

    regsvr32 mscomctl.ocx

    That alone fixed it for many.

    If this didn't solve it:

    Run only this line:

    regsvr32 mscomctl.ocx /u

    Log off/on

    Run this line:

    regsvr32 mscomctl.ocx

    If this didn't solve it:

    Run only this line:

    regsvr32 mscomctl.ocx /u

    Reboot

    Run this line:

    regsvr32 mscomctl.ocx

    You may also try to log off/on or reboot after the running the second line

    If it still didn't solve it.

    You'd have to get a hold of the old mscomctl.ocx version Microsoft Update replaced, either via a backup or online, or a friend, somehow get it.

    Place the old ocx in a random folder NOT in the system folder where all the dll's reside (i.e. C:\Windows\System32), for example c:\randomfolder\mscomctl.ocx (old version)

    Then run the following script:

    regsvr32 mscomctl.ocx /u

    regsvr32 mscomctl.ocx

    regsvr32 c:\randomfolder\mscomctl.ocx

    Like the previous solutions you might have to log off/on or reboot between the un-register and register and after the last line

    I believe this covers all remedies you may see different variations but its all over kills, in my honest opinion, and won't do anything more.

    Good luck!

    Theses options worked. Problem is number of clients across multiple locations....

    XP: Click Start, Run, Enter "regsvr32 c:\windows\system32\MSCOMCTL.ocx" (without quotes), Click OK 

    WIN7 (32-bit): 

    Must be Admin and disable UAC. 

    Click Start, Run, Enter "regsvr32 c:\windows\system32\MSCOMCTL.ocx" (without quotes), Click OK 

    Alternate method: Click Start, right mouse-click on CMD (Command Prompt), Click on Run As... (Run as Administrator), Enter "regsvr32c:\windows\system32\MSCOMCTL.ocx" (without quotes), Click OK 

    WIN7 or SERVER 2008 (64-bit): 

    Must be Admin and disable UAC. 

    Click Start, Run, Enter "regsvr32 c:\windows\syswow64\MSCOMCTL.ocx" (without quotes), Click OK 

    Don't know what's preventing MS from offering a follow up kb with a comprehensive fix.

    Was this answer helpful?

    0 comments