- MSCOMCTL OCX DLLREGISTERSERVER FAILED INSTALL
- MSCOMCTL OCX DLLREGISTERSERVER FAILED CODE
- MSCOMCTL OCX DLLREGISTERSERVER FAILED WINDOWS
I think you meant "RIGHT CLICK" on command prompt > "RUN AS ADMINISTRATOR", *Edit:* FYI This was done on a Windows7 圆4 Ult machine > LEFT CLICK ON "Command Prompt" and choose "RUN AS ADMINISTRATOR"
) And instead of doing the "Start > Run" go to Start > Programs > Accessories Get the afrementioned zip, extract to said directory ( C:\WINDOWS\SYSTEM directory. ! If you have any feedback, please tell us.Įveryone always forgets to mention the "Administrator role" or, like here, people overlook it. Or please register this control under Administrator role. Once it is there click START-> RUN and type "REGSVR32 MSCOMCTL.OCX" (No quotes) in the box to register this control. The file should be placed in your C:\WINDOWS\SYSTEM directory. This requires a little more understanding of proper component registration, however the standard merge modules take care of this for VB6 components.To correct the error, first search your drive for MSCOMCTL.OCX to see if you have it.
MSCOMCTL OCX DLLREGISTERSERVER FAILED WINDOWS
Ideally you would give up on legacy scripted installers and use Windows Installer packages instead. If you can't get this right, using a product with sharp knives on the dashboard facing the front seat occupants (like Inno) isn't going to help you. Take a step back and try to create and deploy a setup package created using the PDW. With a proper installer you should not even need to be aware of the filesystem redirection done for 32-bit processes. This screwing around trying to manually dump things into SysWOW64 and register them doesn't bode well. Instead people seem to copy/paste script snippets they find lying around on the Internet and use them blindly, leading to all sorts of DLL Hell for users gulled into running the resulting installers. I consider tools like Inno Setup fairly hazardous, since they do little to help you get things right. If you "don't know" your program uses it this suggests a possible malware infection - though that seems like a stretch. If you get the error at runtime, then clearly your program is trying to use this control. RE: Package and Deployment error HughLerwill (Programmer) 21 Aug 11 03:54
MSCOMCTL OCX DLLREGISTERSERVER FAILED CODE
However, an attempt to register this gave the same error code 0x8002801c message.Īny thoughts? Thanks in advance for your expert help.
MSCOMCTL OCX DLLREGISTERSERVER FAILED INSTALL
I install this in C:\Windows\SysWOW64 on my Windows 7 machine.
More googling finds answers.mi m/en-us/wi ndows/foru m/windows_ 7-windows_ install/wi ndows-7-pr o-error-co de-0x80028 01c/518c72 cd-2a89-47 fa-bf01-cb 88470b1f0c, which tells me to obtain an up to date version of mscomct2.ocx (from http ://activex. RegSvr32: The module "c:\windows\syswow64\MSWINSCK.OCX" was loaded but the call to DllRegisterServer failed with the error code 0x8002801c. Unfortunately, an attempt to register this file on my Windows 7 machine gave me the following error: This had me install MSWINSCK.OCX in the Windows\SysWOW64 directory (as opposed to the Windows\System32 directory) on my Windows 7 machine. (It is in the WINDOWS\system32 directory on my XP machine).Īfter some sleuthing, I found http: //angrybyt e.com/wind ows-hacks/ mswinsck-o cx-for-64- bit-window s-7-vista/. However, in both cases, when I try to run the app I get the following error:Ĭomponent 'MSWINSCK.OCX' or one of its dependencies not correctly registered: a file is missing or invalidĪs far as I know, I do not use this. I use the resulting setup.exe to successfully install the app on my two Windows 7 machines. I have used the Inno Setup Compiler to create an installer for my VB6 application, which I've developed on an XP machine.