Updating registry with ocx files
Enter the font's name in the “Registration Name” text field.This will be the name under which the font will be registered.Creating and saving a NEW project did show the 2.1 but it sure doesn't seem critical here. Well maybe it's because of the ' DTPicker'(to access certain Database/Recordsets ) from MSCOMCT2 that is somehow linked to MSCOMCTL.The problem: Microsoft Office 2010 products (or later) install updates that break compatibility of and COMCTL32Unfortunately this affects many other programs such Visual Basic 6 SP6 and even Oracle Virtual Box v5. You can find detailed background information about this problem here.Here is another working solution: The solution assumes you have not damaged your registry by deleting, replacing and re-registering and COMCTL32without unregistering the Office patch files.The oldest (legacy) version is that shipped with Visual Basic 6 on 1998 18.104.22.168 (v2.0), or the one shipped with an early service pack 22.214.171.124 on April 2005.
Displayed error message is "'[project_vbp_path]/MSCOMCTL. OCX' could not be loaded--Continue Loading Project? Note that the path in the messeage is the vbp file folder path instead of the control's registered path.Updating to the "2.1" version will resolve this, and is the recommended solution.In critical cases, where you run a program "now", or you don't have access to source code, or the control is used 400 times in a large modular project, you can use a "big hammer" method and update the registry to re-enable the control: ** : Editing the Windows Registry in the wrong way can mess up your computer big time. Problem still unresolved with solutions like "reg/unreg mscomctl.ocx" Used the Info above of Rumi.Create a batch file called and place the following commands in it: regsvr32 /s /u %windir%\Sys WOW64\comctl32regsvr32 /s /u %windir%\Sys WOW64\del /y %windir%\Sys WOW64\comctl32del /y %windir%\Sys WOW64\msiexec /passive /norestart /i KB2708437msiexec /passive /a KB2708437regtlib %windir%\Sys WOW64\Download from Security update for Visual Basic 6.0 Service Pack 6: August 14, 2012 the msi file and rename it to KB2708437
Note: A direct link to the Service Pack 6 download is located HERE. What does is to properly unregister and then delete the current and COMCTL32files, and then apply the latest Visual Basic 6 SP6 rollup patch. ====================================================================== Advanced Solution: If however you have accidentally damaged your registry, you need to get as many versions of and COMCTL32you can find.
The following file types can be registered: Check the Auto register file (DLL, OCX,etc) box to mark the file for registration. The self registration method of registering components has many drawbacks (like not being able to roll back the changes if something fails later in the install) and it is against Microsoft guidelines.