Component "mscomctl.ocx" or one.....

[dave]

After my last Windows update I have 2 programs which no longer run.
The error message is 'component mscomctl.ocx or one of its dependencies
is not correctly registered: a file is missing or invalid"
The programs are Karen's Replicator and Karen's Directory Printer. I am
using Win7 64 bit.
I think I heard about Karen's software in this group and really liked
the Replicator for simple and fast file and folder backups.
I can't say which update did it because there were 18 at one time.
Can anyone help me fix this?

Dave

 

[Paul]

After my last Windows update I have 2 programs which no longer run.
The error message is 'component mscomctl.ocx or one of its dependencies
is not correctly registered: a file is missing or invalid"
The programs are Karen's Replicator and Karen's Directory Printer. I am
using Win7 64 bit.
I think I heard about Karen's software in this group and really liked
the Replicator for simple and fast file and folder backups.
I can't say which update did it because there were 18 at one time.
Can anyone help me fix this?

Dave

First hit, says to re-register it with regsvr32.

http://www.majorgeeks.com/faqshow.php?id=8

Another example here, for a Windows 7 user.

http://answers.microsoft.com/en-us/...l/f96acaa3-90d7-437a-a9cc-9130eb17fdb4?auth=1

More fun here.

http://answers.microsoft.com/en-us/...ms12-060/6dadedda-7bfa-4569-91d8-a31ebcf6a08a

It seems, on occasion, Microsoft patches that file, which is
perhaps why it got messed up. So it's not likely to be
an accidental victim of an update, but was probably part
of some update.

Paul

 

[dave]

First hit, says to re-register it with regsvr32.

http://www.majorgeeks.com/faqshow.php?id=8

Another example here, for a Windows 7 user.

http://answers.microsoft.com/en-us/windows/forum/windows_7- windows_prog
4
37a-a9cc-9130eb17fdb4?auth=1

More fun here.

http://answers.microsoft.com/en-us/windows/forum/windows_7- windows_upda
456
9-91d8-a31ebcf6a08a

It seems, on occasion, Microsoft patches that file, which is
perhaps why it got messed up. So it's not likely to be
an accidental victim of an update, but was probably part
of some update.

Paul

Thanks Paul. I tried the method in the first link and get the message

The module "mscomctl.ocx" was loaded but the call to DllRegisterServer
failed with error code 0x8002801c.

I'm searching now for the meaning and fix for that.

Dave

 

[Paul]

Thanks Paul. I tried the method in the first link and get the message

The module "mscomctl.ocx" was loaded but the call to DllRegisterServer
failed with error code 0x8002801c.

I'm searching now for the meaning and fix for that.

Dave

Since it is Windows 7, try elevating yourself.

Type "cmd", right click on the returned string on the screen,
then select "Run as Administrator". That starts a Command Prompt
window owned by the administrator (slightly more powerful,
for modifying things like system files).

I get that idea from this:

http://support.microsoft.com/kb/832926

"You may receive failure messages with either the return code value
of 0x80070005 or the return code value of 0x8002801c.

These failure messages occur when you try to unregister a DLL that
you were able to correctly register before. The return code values
that are mentioned previously indicate [some edits by me...]

0x80070005 Access is denied

0x8002801c Error accessing the OLE registry

respectively."

So that's why I'm just guessing, "Mr.Admin" will fix it

Paul

 

[dave]

Since it is Windows 7, try elevating yourself.

Type "cmd", right click on the returned string on the screen,
then select "Run as Administrator". That starts a Command Prompt
window owned by the administrator (slightly more powerful,
for modifying things like system files).

I get that idea from this:

http://support.microsoft.com/kb/832926

"You may receive failure messages with either the return code value
of 0x80070005 or the return code value of 0x8002801c.

These failure messages occur when you try to unregister a DLL that
you were able to correctly register before. The return code values
that are mentioned previously indicate [some edits by me...]

0x80070005 Access is denied

0x8002801c Error accessing the OLE registry

respectively."

So that's why I'm just guessing, "Mr.Admin" will fix it

Paul

Thanks Paul, that did it.
I thought I was the admin 'cause when I checked in "user accounts" there
was my name with "Administrator" beside it!

Dave

 

[Paul]

Since it is Windows 7, try elevating yourself.

Type "cmd", right click on the returned string on the screen,
then select "Run as Administrator". That starts a Command Prompt
window owned by the administrator (slightly more powerful,
for modifying things like system files).

I get that idea from this:

http://support.microsoft.com/kb/832926

"You may receive failure messages with either the return code value
of 0x80070005 or the return code value of 0x8002801c.

These failure messages occur when you try to unregister a DLL that
you were able to correctly register before. The return code values
that are mentioned previously indicate [some edits by me...]

0x80070005 Access is denied

0x8002801c Error accessing the OLE registry

respectively."

So that's why I'm just guessing, "Mr.Admin" will fix it

Paul

Thanks Paul, that did it.
I thought I was the admin 'cause when I checked in "user accounts" there
was my name with "Administrator" beside it!

Dave

Well, if a screwdriver won't work, use a hammer
That's what my shop teacher taught me.

Paul

 

[Gene E. Bloch]

Since it is Windows 7, try elevating yourself.

Type "cmd", right click on the returned string on the screen,
then select "Run as Administrator". That starts a Command Prompt
window owned by the administrator (slightly more powerful,
for modifying things like system files).

I get that idea from this:

http://support.microsoft.com/kb/832926

"You may receive failure messages with either the return code value
of 0x80070005 or the return code value of 0x8002801c.

These failure messages occur when you try to unregister a DLL that
you were able to correctly register before. The return code values
that are mentioned previously indicate [some edits by me...]

0x80070005 Access is denied

0x8002801c Error accessing the OLE registry

respectively."

So that's why I'm just guessing, "Mr.Admin" will fix it

Paul

Thanks Paul, that did it.
I thought I was the admin 'cause when I checked in "user accounts" there
was my name with "Administrator" beside it!

Dave

Microsoft's naming methods can be interesting

*The* Administrator account is the account that can do (almost)
anything. An account of *type* Administrator is an account with many,
but not all, of the privileges of *the* Administrator.