MSCOMCTL - Object library not registered? It did work, but not anymore! Help :(

Hi guys, My project has been using Microsoft Windows Common Controls 6.0 (SP6) as it used listview controls on my forms,

Last night, my computer rebooted unexpectedly, since then I am now getting the error when opening my project as well as adding the component.

I get the error : Object library not registered


Does anybody know how I can fix this?

Regards
Jamie

I had the same problem this morning after Windows Update installed some updates (I'm using Windows 7 Professional 32-bit).

It looks as if the update installed a new version of the common controls OCX, but didn't register it.

I used regsvr32 to register comctl32.ocx and comct332.ocx which seems to have solved the problem.

We have the same problem and found that de \windows\system32\mscomctl.ocx was reniewed and not registered.
After registration the problem was solved.

There was a recent Office 2003 update that replaced this library with a new version, but in a way that breaks its registration. For all I know other versions of Office might trigger the same update.

They went from version 2.0 of the COM binary interface to version 2.1, see:

MS12-060: Description of the security update for Office 2003 and Office 2003 Web Components: August 14, 2012

This isn't the "file version" a.k.a. "build version" which is now 6.01.9834 and shows up in the file's Properties pages.


If you always run VB6.EXE elevated this is no problem. Open an old Project and it runs and compiles just fine, and the new compiled EXE runs fine.

The real headache might be applications already deployed to other systems. I can't verify that yet one way or the other.

It is also generally better to use the older 5.0.x (file version) of this library when you can anyway. Most of it is a thin wrapper on the Windows Common Controls libraries and so you can apply the system UxTheme by using a manifest.

The 6.0.x versions "got clever" and added new functionality by embedding modified, custom versions of the Common Controls. This also makes the 6.0 library bigger as well as ruling out simple themeing - something they didn't realize back in 1998 was going to happen down the road.

In Windows 7 x64, and Office2010 32bits We too had the same problem with Mscomctl.ocx and "object library not registered".
The update causing this issue is: http://support.microsoft.com/kb/2597986
The solution was to use regsvr32 to register \windows\sysWOW64\mscomctl.ocx and it seems to work OK.

I know this is an old thread but I have the same problem and un-registering and re-registering does not work for me. Files are in Syswow32. Any other ideas? Thanks guys. This all started somewhere between Aug 2013 and now. It effects the windows common controls for Mscomctl.ocx (version 6.1.98.33) and Mscomct2.ocx (version 6.1.98.16).
What I really need is to add back the DTPicker control. And if I can't, is there a 3rd party control that is similar?

Forgot to mention that this is happening with my Windows 7 Pro, 64bit PC. My XP Pro, 32bit is working fine.

See this thread (post #15):
http://www.vbforums.com/showthread.p...=1#post4546015

Thanks @Arnoutdv
I tried that yesterday with no luck. I found that I need to use Regtlibv12.exe. I found it in C:\Windows\Microsoft.NET\Framework64\v4.0.30319 and copied it to my Syswow32 folder. Then I used C:\Windows\Syswow64\Regtlibv12 Msdatsrc.tlb and it worked great. I'm happy now

Great and thanks for sharing!

I faced this problem on Windows 7 64 bit. I re-installed Windows 7 and Office 2003. Then manually registered \windows\sysWOW64\mscomctl.ocx as a system adminstrator. Now it is working fine.

object library not registered vb6 on windows 11. How do I find out which module has the problem.

Windows 10 has no problem. Compiles succesful in both systems. IDE runs successful in win 10; fails in Win 11. .exe works in win 10 but not in win 11.

dependency check reveals nothing.

bkandler

Windows 11 does not support manifests.:mad:

It likely has external ones off by default... do you mean the option to turn them on no longer exists?

Or do you mean internal manifests too?

A recent update MS pushed may be making Windows ignore certain parts of manifests for VB6 apps.


----
More on topic, I've had some luck resolving these kinds registration error issues for new Windows 10+ installs in the IDE with the following,

-Open the project, ignore errors and continue loading.

-Don't open anything, just goto to Project->Components

-Check the component it says it couldn't load, then click ok

-Exit, and when you get the prompt to save, save only the vbp. If more files are listed, deselect them.

Now when you open the project again, everything should load normally with all controls still in place.

Quote:

---

Originally Posted by fafalone

A recent update MS pushed may be making Windows ignore certain parts of manifests for VB6 apps.

---

Could you expand?

Quote:

---

Originally Posted by Argus19

Windows 11 does not support manifests.:mad:

---

Is that true?

Quote:

---

Originally Posted by yereverluvinuncleber

Is that true?

---

The manifest for MSCOMCTL.ocx, in one of my programs, stopped working on Win 11.

Quote:

---

Originally Posted by Argus19

The manifest for MSCOMCTL.ocx, in one of my programs, stopped working on Win 11.

---

How do you know it is the manifest what is causing the problem (stop working)?
What error are you experiencing?

Quote:

---

Originally Posted by argen

How do you know it is the manifest what is causing the problem (stop working)?
What error are you experiencing?

---

"Component 'MSCOMM32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid".

Quote:

---

Originally Posted by argen

Could you expand?

---

https://www.vbforums.com/showthread....ted&highlight=

Quote:

---

Originally Posted by fafalone

https://www.vbforums.com/showthread....ted&highlight=

---

It does not seem that they ignore manifest files, that seems more like a bug.
BTW: I don't have that update (KB5013941), it seems to be just for some very specific Windows versions (Windows Server 2019 and Windows 10 LTSB).