This security update doesn't replace any previously released update.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:ģ139567 Error messages or Access crashes after you install security update MS16-004įor deployment information about this update, see Microsoft Knowledge Base Article KB3124585. Developer Microsoft Corporation Product MSCOMCTL Description Windows Common Controls ActiveX Control DLL Filename Mscomctl32. Specifically, these problems occur if you use the controls that are associated with the MSCOMCTL.OCX file that's updated in the security update. Download and install Mscomctl32.ocx to fix missing or corrupted ocx errors. Follow the installation instructions on the download page to install the update.ĭownload the security update KB2920727 for 32-bit version of Office 2016 More Information Known issues in this security updateĪfter you install this security update, you have problems that affect your Access database if you use certain Windows common controls. You can obtain the stand-alone update package through the Microsoft Download Center.
For more information about how to turn on automatic updating, see Get security updates automatically. When you turn on automatic updating, this update will be downloaded and installed automatically. This update is available from Microsoft Update. How to obtain and install the update Method 1: Microsoft Update Note To apply this security update, you must have the release version of Office 2016 installed on the computer.įor a complete list of affected versions of Microsoft Office software, see KB3124585. To learn more about these vulnerabilities, see Microsoft Security Bulletin MS16-004.
This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user opens a specially crafted Office file. When all three common control components have been registered, re-open your project in Visual Basic 6.MS16-004: Description of the security update for Office 2016: JanuSummary To register the controls on a 64-bit Windows system, enter the following commands at the command prompt:Ĭ:\windows\syswow64\regsvr32.exe c:\windows\syswow64\mscomctl.ocxĬ:\windows\syswow64\regsvr32.exe c:\windows\syswow64\mscomct2.ocxĬ:\windows\syswow64\regsvr32.exe c:\windows\syswow64\comct332.ocxĪfter each command is entered, a confirmation message box should be displayed indicating that the control has been registered successfully. To register the controls on a 32-bit Windows system, enter the following commands at the command prompt:Ĭ:\windows\system32\regsvr32.exe c:\windows\system32\mscomctl.ocxĬ:\windows\system32\regsvr32.exe c:\windows\system32\mscomct2.ocxĬ:\windows\system32\regsvr32.exe c:\windows\system32\comct332.ocx Change your current working directory to that directory before registering the components. This is where 32-bit ActiveX components and DLLs are stored on 64-bit systems. If the system is running a 64-bit version of Windows, the components listed above will be in the C:\Windows\SysWOW64 folder. With UAC enabled, this will cause a confirmation dialog to be shown. From the context menu, select Run as Administrator. To do this, you should open a command prompt by selecting Start > All Programs > Accessories and then right-click on Command Prompt.
If the system is running Windows Vista or later versions of Windows, the control registration must be performed with administrative privileges. If the IDE prompts you to save any changes, do not save them to prevent the references to the common controls from being removed from the project. Prior to registering these components, make sure that you have closed all running instances of the VB6 IDE. To fix this problem, it is recommended that you re-register each of these components using the regsvr32.exe utility. Most of the SocketTools examples for Visual Basic 6 use the first common controls component (mscomctl.ocx), but there are several that may use the others as well. There are three common controls components available for Visual Basic 6: mscomctl.ocx This error occurs when one or more of the Microsoft Windows Common Controls are not registered, or the registry information has been corrupted. Visual Basic will generate a logfile that lists the control or controls that could not be loaded, along with various invalid property names. The actual name of the common control class will vary depending on what control the project references, such as ProgressBar, StatusBar or TreeView however the error always indicates a Windows Common Control name. ClassName of control ControlName was not a loaded control class" is displayed. When attempting to open a SocketTools example project for Visual Basic 6.0, the error "Class MSComctlLib.