Computer Hope
Software => Computer software => Topic started by: meadows on June 17, 2013, 06:52:07 PM
-
hello and hope someone can help with this been unable to work it out i all ways try first but this is new to me and im getting a bit lost
component COMCTL32.OCX or one of its dependencies not correctly registered a file is missing or invalid (iv downloaded new file placed in 32 folder try register file and get the error (the module comctl32.ocx failed to load make sure the binary is stored at the specified path or debug it to check for problems with the biniry or dependent .dll files)
plus this is on all my pc's iv even reinstalled windows 7 an deleted and re downloaded program to end up with the same prob (alani CODMW3Launcher.exe)
thanks for your time
-
Have you done some research on this?
It seems to be a very common problem.
http://answers.microsoft.com/en-us/windows/forum/windows_7-files/comctl32ocx-error-in-windows-7/051b2862-b4a1-45fc-aad8-140ed32dc682
Here are two steps you may try.
Step 1: Re-register the component.
Verify if comctl32.ocx is in C:\windows\system32 folder. If you, you may try re-registering the file.
1. Go to start and type cmd.
2. Right-Click on cmd and select “Run as Administrator”.
3. Type regsvr32 comctl32.ocx and press Enter.
If successful you should get a popup saying "DllregisterServer in
comscl32.ocx succeeded"
Did you already do that?
-
yes i tryed that when i try reg in cmd i get the module comctl32.ocx failed to load make sure the binary is stored at the specified path or debug it to check for problems with the biniry or dependent .dll files. and remember that i have reinstalled a fresh windows 7 and fresh copy of the program (iv downloaded the .ocx an tryed to register it that is the error the module comctl32.ocx failed to load files. DL the .dll file registered fine
-
What is reg command? I don't know what that means.
The right command is regsvr32.
-
register in command prompt and yes that is what i did to get the comctl32.ocx register error
-
OK. This is a component of Microsoft Office, -Right?
If not, I am on the wrong track. Sorry
On the MS forums users who got the same issue got the run-around from the 'experts' from MS.
You would think that if there was a simple answer, they would give it.
This looks better:
Do you install Windows 7 32bit version or Windows 7 64bit version?
1. Please go to Event Viewer, click Applications and see if any error is logged.
2. It seems that the MSCOMCTL.OCX isn’t correctly registered or that it isn’t compatible with your Windows. Please open a Command Prompt and run as Administrator, then type the following command:
Regsvr32 MSCOMCT2.OCX
If you are using Window7 64bit, try typing:
Regsvr32 c:\windows\SysWOW64\MSCOMCT2.OCX
If the issue still persists, let’s download a new MSCOMCTL.OCX and register it again. You can download the MSCOMCTL.OCX from the following link:
.....
Above copied from:
http://social.technet.microsoft.com/Forums/en-US/w7itproappcompat/thread/19b11adb-4f89-4ced-a049-1f08f2eebcd7/
Scroll down the page and find a link labeled:
Msconctl.zip
I have not tried this.
Please report back if that is the aright answer.
I will assume it is not the right answer.
-
just need to say that the program is alani CODMW3Launcher.exe it is a server launcher and it had been running fine for months and to my memory the trouble started after i ran a reg clean up with jvc power tools
-
Sorry, I was way off. :-[
-
IF you are on a 64-bit system, comctl32.ocx won't be in the C:\Windows\System32 folder; it will be in the C:\Windows\SysWOW64 folder.
Try running regsvr32 C:\Windows\SysWOW64\comctl32.ocx and see how that goes.
Also this is an excellent example of why Register Cleaners suck.
-
yes it is 64bit. so i place comctl32.ocx in C:\Windows\SysWOW64 and use run (regsvr32 C:\Windows\SysWOW64\comctl32.ocx) is that right
i would just like to no how the problem i am having is possible since i have formatted an reinstalled windows (even on a new SSD)
thanks for your time an help guys
-
the module C:\Windows\SysWOW64\comctl.ocx was loaded but the call to dllregisterserver failed with error 0x8002801c
-
You need to run regsvr32 from an elevated command prompt. (Right-click, Run-as Administrator)
-
same error the module C:\Windows\SysWOW64\comctl.ocx was loaded but the call to dllregisterserver failed with error 0x8002801c
-
fresh windows and a fresh DL of CODMW3Launcher.exe how can i have this problem i dont understand
-
same error the module C:\Windows\SysWOW64\comctl.ocx was loaded but the call to dllregisterserver failed with error 0x8002801c
You've said "comctl.ocx" twice now. It's comctl32.ocx, just to be clear.
In an elevated command prompt, the command should be:
C:\windows\syswow64\regsvr32.exe C:\windows\syswow64\comctl32.ocx
yes it is 64bit. so i place comctl32.ocx in C:\Windows\SysWOW64 and use run (regsvr32 C:\Windows\SysWOW64\comctl32.ocx) is that right
Placed? You shouldn't be placing files anywhere. Windows 7 includes both versions of the file.
-
there was not a copy of it in SysWOW64 but yes it works thank you very much sir top marks for this forum now i can get back to it.
-
Just to explain for future readers, on x64 systems there are two system folders. C:\Windows\System32 is where 64-bit components are stored, and C:\Windows\SysWOW64\ is where 32-bit components are stored. 32-bit Applications, however, will get magically redirected to C:\Windows\SysWow64 if they access C:\Windows\System32. This causes a lot of confusion.
There is also redirection in the registry, which is probably relevant here.
regsvr32.exe in C:\Windows\System32 would be the 64-bit program, which registers and unregisters 64-bit components. It acts weird with 32-bit components, and when it does work, it registers it into the main registry.
the regsvr32.exe in the SysWOW64 is the 32-bit version, and will register 32-bit components in a way so that 32-bit applications can see them; (registry access by 32-bit applications in HKEY_CLASSES_ROOT get's redirected to "HKEY_CLASSES_ROOT\WOW6432Node" instead, so 32-bit applications will be looking for the component registration there.
-
32-bit Applications, however, will get magically redirected to C:\Windows\SysWow64 if they access C:\Windows\System32. This causes a lot of confusion.
HUH ???
-
HUH ???
Precisely.
I wrote about this behaviour (http://bc-programming.com/blogs/2009/12/windows-x64-fileregistry-redirection/) some time ago.
Basically, 32-bit applications are often written to access components in C:\Windows\System32. This is why MS couldn't just make a new System64 folder for 64-bit components. In order to be as compatible as possible, Applications running under WoW64 (32-bit apps on 64-bit windows, that is) can still access C:\Windows\System32, but those requests are redirected to C:\Windows\SysWOW64. 32-bit applications that are aware of the redirection can access the actual System32 folder contents by accessing C:\Windows\sysnative.
This can be tested without having to write applications (or something) by using something like Command Prompt. C:\Windows\System32\cmd.exe is the Command Prompt, as we all know; on 64-bit systems, this is a 64-bit executable. However on 64-bit systems the 32-bit version is still available in C:\Windows\SysWOW64.