Uninstalling IE10 restores common controls

Karl E. Peterson

unread,

Apr 18, 2013, 1:05:00 PM4/18/13

to

Well, after hearing of no another way to undo the mess, I'll just
report here that uninstalling IE10 - on a Windows 7 x64 system - allows
me to again load both MSCOMCTL.OCX and MSCOMCT2.OCX into the VB6
environment.

--
.NET: It's About Trust!
http://vfred.mvps.org

RW

unread,

Apr 18, 2013, 3:26:07 PM4/18/13

to

On Thu, 18 Apr 2013 10:05:00 -0700, Karl E. Peterson <ka...@exmvps.org>
wrote:

>Well, after hearing of no another way to undo the mess, I'll just
>report here that uninstalling IE10 - on a Windows 7 x64 system - allows
>me to again load both MSCOMCTL.OCX and MSCOMCT2.OCX into the VB6
>environment.

Yep. That's what worked for me (as I reported earlier). As a
precaution I also "hid" the Windows update that installs IE10 to make
sure I don't accidently check it and reinstall the junk.

Karl E. Peterson

unread,

Apr 18, 2013, 3:29:44 PM4/18/13

to

RW formulated on Thursday :

Me too!

ralph

unread,

Apr 18, 2013, 3:48:14 PM4/18/13

to

On Thu, 18 Apr 2013 10:05:00 -0700, Karl E. Peterson <ka...@exmvps.org>
wrote:

>Well, after hearing of no another way to undo the mess, I'll just
>report here that uninstalling IE10 - on a Windows 7 x64 system - allows
>me to again load both MSCOMCTL.OCX and MSCOMCT2.OCX into the VB6
>environment.

To clarify - you also had the problem on Windows 7 x64?

Several posts seemed to suggest that 64-bit O/S did not have the
problem, it was limited to 32-bit O/S only. But that is not true? IE10
is a problem no matter the bit-ness of the O/S?

Did you also attempt to provide a version-free Registry entry?

-ralph

ObiWan

unread,

Apr 18, 2013, 4:12:15 PM4/18/13

to

> Well, after hearing of no another way to undo the mess, I'll just
> report here that uninstalling IE10 - on a Windows 7 x64 system -
> allows me to again load both MSCOMCTL.OCX and MSCOMCT2.OCX into the
> VB6 environment.

Karl... it would be interesting to use something like (e.g.)

http://www.pcmag.com/article2/0,2817,2398835,00.asp

or something like that; it may (and probably will) give you a hint
about what changed and why the setup screws the common controls and
other stuff... and this it turn may help finding a workaround ;-)

Karl E. Peterson

unread,

Apr 18, 2013, 7:43:08 PM4/18/13

to

ralph explained on 4/18/2013 :

> On Thu, 18 Apr 2013 10:05:00 -0700, Karl E. Peterson <ka...@exmvps.org>
> wrote:
>
>> Well, after hearing of no another way to undo the mess, I'll just
>> report here that uninstalling IE10 - on a Windows 7 x64 system - allows
>> me to again load both MSCOMCTL.OCX and MSCOMCT2.OCX into the VB6
>> environment.
>
> To clarify - you also had the problem on Windows 7 x64?
>
> Several posts seemed to suggest that 64-bit O/S did not have the
> problem, it was limited to 32-bit O/S only. But that is not true? IE10
> is a problem no matter the bit-ness of the O/S?

I understood it to only be a problem on x64. I don't have any 32-bit
installs, so haven't tried that.

> Did you also attempt to provide a version-free Registry entry?

No, not even sure I know what you're asking, exactly.

Karl E. Peterson

unread,

Apr 18, 2013, 7:46:39 PM4/18/13

to

ObiWan formulated the question :

That looks like a nice little tool! Since I don't even use IE, though,
I certainly don't need IE10. Which makes me someone disinterested in
spending $8 just to find out how Microsoft is breaking stuff. <g>

Bob Riemersma

unread,

Apr 19, 2013, 2:49:47 AM4/19/13

to

"Karl E. Peterson" <ka...@exmvps.org> wrote in message
news:kkp8uf$7n4$1...@dont-email.me...

> Well, after hearing of no another way to undo the mess, I'll just report
> here that uninstalling IE10 - on a Windows 7 x64 system - allows me to
> again load both MSCOMCTL.OCX and MSCOMCT2.OCX into the VB6 environment.

There is a rumor that an expired code-signing certificate may be involved.
If true that might suggest why the problem appears as of April 1st and why
setting the system date prior to that fixes it for some people.

ObiWan

unread,

Apr 19, 2013, 10:22:25 AM4/19/13

to

> > Karl... it would be interesting to use something like (e.g.)
> >
> > http://www.pcmag.com/article2/0,2817,2398835,00.asp
> >
> > or something like that; it may (and probably will) give you a hint
> > about what changed and why the setup screws the common controls and
> > other stuff... and this it turn may help finding a workaround ;-)

> That looks like a nice little tool! Since I don't even use IE,
> though, I certainly don't need IE10. Which makes me someone
> disinterested in spending $8 just to find out how Microsoft is
> breaking stuff. <g>

Well... there's really NO need to pay $8; I wrote "something like"
which doesn't mean "that one" but something "like it" and, luckily,
there ARE some choices

http://lists.thedatalist.com/pages/Install_and_Uninstall_Tools.htm

and some of them are free too :) all in all, the "List of Lists", set
aside the name (resounding from DOS memories ;D) carries quite a bunch
of good links and if you never saw it http://lists.thedatalist.com is
the correct starting point :)

ObiWan

unread,

Apr 19, 2013, 10:31:41 AM4/19/13

to

> Well... there's really NO need to pay $8; I wrote "something like"
> which doesn't mean "that one" but something "like it" and, luckily,

Oh ... and since we're at it; I think that it shouldn't be so
difficult (at least from the need to use APIs standpoint) to create
some app in VB (yeah !) to help with installations; basically the idea
is to have an app which you'll use to run the setup, the app will
then put hooks on the filesystem/registry (and some other process
stuff if needed), and create a copy of whatever file or entry created
or changed by the setup and then, when the setup completes, the app may
present a detailed report; not just that, saving the log (use whatever
custom format) and reloading it at a later time would then allow to
rollback all the changes or either, to flush the backup :)

Karl E. Peterson

unread,

Apr 22, 2013, 12:16:07 PM4/22/13

to

ObiWan pretended :

>>> Karl... it would be interesting to use something like (e.g.)
>>>
>>> http://www.pcmag.com/article2/0,2817,2398835,00.asp
>>>
>>> or something like that; it may (and probably will) give you a hint
>>> about what changed and why the setup screws the common controls and
>>> other stuff... and this it turn may help finding a workaround ;-)
>
>> That looks like a nice little tool! Since I don't even use IE,
>> though, I certainly don't need IE10. Which makes me someone
>> disinterested in spending $8 just to find out how Microsoft is
>> breaking stuff. <g>
>
> Well... there's really NO need to pay $8; I wrote "something like"
> which doesn't mean "that one" but something "like it" and, luckily,
> there ARE some choices

Sure, I've seen similar. This is the first I recall that "promised" to
also monitor what happened during shutdown and startup, following the
install. That sounded like it might do a better job of capturing the
corruption during Windows Updates. :-)

Karl E. Peterson

unread,

Apr 22, 2013, 12:16:58 PM4/22/13

to

Bob Riemersma explained :
> "Karl E. Peterson" <ka...@exmvps.org> wrote...

>> Well, after hearing of no another way to undo the mess, I'll just report
>> here that uninstalling IE10 - on a Windows 7 x64 system - allows me to
>> again load both MSCOMCTL.OCX and MSCOMCT2.OCX into the VB6 environment.
>
> There is a rumor that an expired code-signing certificate may be involved. If
> true that might suggest why the problem appears as of April 1st and why
> setting the system date prior to that fixes it for some people.

That's intriguing. Sounds pretty fixable, too, if "someone" cared
enough to do so.