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-17T22:51:45+00:00

    I'm just reverting my 100+ users to the previous version of the OCX. They still have to reboot after unregistering. Here's my command script in case anyone is interested.

    [code]

    @echo off

    echo.

    echo Reverting to original MSCOMCTL.OCX file (thank you Bill Gates!). Please wait...

    if exist %systemroot%\sysWOW64\mscomctl.ocx goto x64

    if exist c:\temp\unreg.txt goto reg

    %systemroot%\system32\regsvr32 /u %systemroot%\system32\mscomctl.ocx /s

    if errorlevel 1 goto err

    echo Unregistered! >c:\temp\unreg.txt

    goto restart

    :reg

    ren %systemroot%\system32\mscomctl.ocx mscomctl.ocx.bad

    if errorlevel 1 goto err

    xcopy c:\temp\mscomctl.ocx %systemroot%\system32

    if errorlevel 1 goto err

    %systemroot%\system32\regsvr32 %systemroot%\system32\mscomctl.ocx /s

    if errorlevel 1 goto err

    goto Done

    :x64

    if exist c:\temp\unreg.txt goto reg64

    %systemroot%\sysWOW64\regsvr32 /u %systemroot%\sysWOW64\mscomctl.ocx /s

    if errorlevel 1 goto err

    echo Unregistered! >c:\temp\unreg.txt

    goto restart

    :reg64

    ren %systemroot%\sysWOW64\mscomctl.ocx mscomctl.ocx.bad

    if errorlevel 1 goto err

    xcopy c:\temp\mscomctl.ocx %systemroot%\sysWOW64

    if errorlevel 1 goto err

    %systemroot%\sysWOW64\regsvr32 %systemroot%\sysWOW64\mscomctl.ocx /s

    if errorlevel 1 goto err

    goto Done

    :restart

    echo.

    echo Restart your system and re-run this script.

    goto quit

    :err

    echo.

    echo Error running script! Please contact support!

    goto quit

    :Done

    echo.

    echo Done! Please restart your system. The app should function normally now.

    :quit

    echo.

    pause

    exit

    [/code]

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-08-17T20:41:07+00:00

    We fixed it by doing the following in our DOT file that had the reference:

    1. Removed the reference to MSCOMCTL.OCX
    2. Saved DOT file.
    3. Added new reference to MSCOMCTL.OCX
    4. Saved DOT file.

    Did not even have to Compile. Just changing the reference seems to have made it compatible with the newest OCX build.

    BIZARRE!

    In a Microsoft Access 2003 application, this same fix (sort of) worked for us to resolve issues with the TreeView control.

    I removed the reference to MSCOMCTL.OCX, closed the References dialog, re-added the reference to MSCOMCTL.OCX and recompiled.  Everything worked on the development machine (WinXP) but when I copied the file to another PC with Win7, the problems persisted.  Interestingly, the copy of the OCX in WinXP had version number 6.1.98.34 (same as Win7) but the file date was 5/2/2012 in WinXP and 6/6/2012 in Win7....  I'm wondering if this makes any difference....

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-08-17T19:38:49+00:00

    I'm having an issue with the TreeView control being broken after the update as well.

    have u tried the remedies suggested so far?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-08-17T19:31:28+00:00

    Hmm... I didn't have to log off or reboot in my situation.

    Was this answer helpful?

    0 comments