KB Articles: • This package updates two Microsoft Visual Basic 6.0 Common Controls: mscomctl.ocx and comctl32.ocx to address the issues described in the KB articles noted in the Related Resources section on this page. This package will not install these Common Controls if they do not already exist on the target system.

Mscomct2.cab Install. The Mscomct2.cab file is still missing. Office 2013 is validated and everything else seems to be operating fine. You're correct that this is really painful to hand out to others, but if you have to, this is how you do it. Just extract the.ocx file from the.cab file (it is similar to a zip).

This package cannot be uninstalled. This package is provided under the terms of the End User License Agreement and is intended for the following customers: • Customers who are Microsoft Visual Basic 6.0 and/or Microsoft Visual Studio 6.0 licensees. • Customers who are not licensees of Microsoft Visual Basic 6.0 nor Microsoft Visual Studio 6.0 but are using older versions of the two Common Controls. Mainstream Support for Microsoft Visual Basic 6.0 ended on March 31, 2005. However, we are releasing this non-security related package because it contains improvements that were ready for release just prior to the end of Mainstream Support. Microsoft Visual Basic 6.0 has transitioned to Extended Support which runs through March 31, 2008.

Microsoft is not extending the Mainstream Support phase for Microsoft Visual Basic 6.0 in any way.

We use a calendar control as part of several MS Access 2007 databases. This is not a problem in Windows XP, but we are migrating to 64 bit Windows 7 and are having trouble registering this OCX control under this OS. We've tried running as administrator, both from a shortcut and from a command prompt.

We've also tried logging into the machine as a local admin - none of these works. The error when failing is 0x8002801C. I've read that Microsoft is possibly fazing out support for VB6 controls in the 64 bit version of Windows 7 but have heard nothing definite. If there is an alternative to using this control that would still work with Access 2007 and run under Windows 7, I'm willing to give that a try.

Office 2010 is not out yet so there must be something that will work in the interim. Hi OfficeBoy48, We have just had the same problem and have now worked out how to do it. You need to copy the MSCOMCT2.OCX file to c: windows sysWOW64 not c: windows system32. You then can register it by running from the command prompt or run in the start menu regsvr32 c: windows sysWOW64 mscomct2.ocx and it should register although make sure that you run regsvr32 with administrator privileges.

Smadav free key. Please note, if you try to register the ocx from c: windows system32 using regsvr32 you will get the following error: The module “c: windows system32 mscomct2ocx” failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent.DLL files.

The specified module could not be found. We think this is because windows 64 bit is mucking about with what directories it is reporting to the regsvr32 although this is just our educated guess.