- #Mscomctl ocx dllregisterserver failed install
- #Mscomctl ocx dllregisterserver failed update
- #Mscomctl ocx dllregisterserver failed code
#Mscomctl ocx dllregisterserver failed install
Presumably Microsoft will eventually ship a non-breaking version of these security updates that you can install later. The last step is to simply block the security updates from being applied by searching for updates, then right-clicking on these and choosing hide. Removing all the ones that do let you remove them, followed by a reboot, seems to allow you to remove the remaining ones. Note: Some of the updates don’t have a remove option however apparently due to a dependency of some sort.
#Mscomctl ocx dllregisterserver failed update
System Restore failed to replace the file _ with its original copy from the restore point.įor those customers we’ve then resorted to removing “Every” security update that is Microsoft Office related, regardless of version of Office, by going to the control panel add/remove programs / programs and features. So this solution sounds great and simple, only problem is that for my customers it hasn’t actually been working.Ī system restore, followed by blocking the update does work, but for many of my customers, the system restores have been failing with an error:
#Mscomctl ocx dllregisterserver failed code
as Administrator or you’ll get a failure type of message such as: The module "mscomctl.ocx" was loaded but the call to DllRegisterServer failed with error code 0x8002801c). bat file, don’t forget that you have to run it with elevated privileges (i.e. %systemroot%\sysWOW64\regsvr32 mscomctl.ocx /s %systemroot%\sysWOW64\regsvr32 /u mscomctl.ocx /s %systemroot%\system32\regsvr32 mscomctl.ocx /s %systemroot%\system32\regsvr32 /u mscomctl.ocx /s If "%PROCESSOR_ARCHITECTURE%" = "AMD64" goto 圆4 bat file containing something like the following (below is my version of it that uses a better method to detect the bit-ness of the OffĮcho Re-Registering the MSCOMCTL.OCX file Rolling back the update / doing a system restore seems to solve the problem, but according to this Microsoft person’s blog entry, the problem is supposed to be fixable by just re-registering the.
If this update is installed on a development computer, a new application created using it will exhibit the same error when delivered to a computer that DOES NOT contain the update. The issue is this KB if you’re running Office 2003: The issue is this KB if you’re running Office 2007: The issue is this KB if you’re running Office 2010: The cause is an update to the MSCOMCTL.OCX file (located in \Windows\System32\ on 32-bit machines or \Windows\SysWow64\ on 64-bit machines) has been made by the Microsoft Security update described in this bulletin: After the Windows Security Update, customers who open my app get errors such as: “Error: TheOpenForm action was cancelled.” + If MSCOMCTL.OCX is no longer present on your system, let me know and I'll send you a replacement.My app uses MSComCtl.ocx to display a tree control.
If the file is present, then direct Windows to register it: DXKeeper needs version 6.1.97.85 of this file, or later. + Otherwise, check to see if the file MSCOMCTL.OCX is present on your system. + If you just now installed or uninstalled another application and suspect that process may have un-registered MSCOMCTL.OCX, and if you directed Windows to create a "restore point" before taking action, then direct Windows to recover from that Restore Point. + No DXLab application has the ability to un-register any component. + that means some event occurred on your system that caused the above component, on which DXKeeper depends, to be un-registered from Windows. “Component ‘mscomctl.oxc’ or one of its dependencies is not correctly registered: a file is missing or invalid”