WARNING: KB942615 may require an extra reboot to apply correctly

[Donald Anadell]

Hi Kurt,

I received the KB942367 Hotfix and installed it along with the associated
Registry Tweak. Only some time and some heavy Browsing will tell if this
has fixed the Urlmon.dll crashing problem in IE6, so far so good but I'll
give it a few days to see how it goes.

I am a little bewildered as to the version of Urlmon.dll that remains in the
System32 folder and dllcache folder though after applying the hotfix. The
Article(KB942367) implies that the hotfix will install version 6.0.2900.3213
of urlmon.dll(or am I reading that wrong). However, after applying the
hotfix I'm still left with the version of urlmon.dll that was installed
KB942615 Cumulative Security Update, version 6.0.2900.3231.

Does this sound right to you, the hotfix should only patch the existing
urlmon.dll file as long as it is version 6.0.2900.3213(or higher), or is it
supposed to replace the existing version with a specific version? I
extracted all the files from the hotfix setup file and I don't see a
urlmon.dll file included in the setup, maybe it's just the geek speak in the
KB Article that has me looking for something that isn't supposed to be
there)

At any rate,

1. I applied the hotfix offered as you suggested.
2. Performed the Registry Tweak after installing the hotfix(per the
instructions the KB942367 Article).
3. After performing steps one and two, I'm left with urlmon.dll version
6.0.2900.3231 in both the System32 and dllcache folders.

LOL...I'll be glad when SP3 arrives, fixing Updates with hotfixes it taking
it to the extreme for my 60 year old brain

Thanks again for your assistance,

Donald Anadell

Thanks for the feedback Kurt,

I've submitted for the Hotfix, when I get the link back and get it
downloaded and installed I'll post back the results.

Donald Anadell

Please try http://support.microsoft.com/kb/942367 and let us know if this
resolves your issues.
Use the online request form to get the fix.


--
Kurt Falde [MSFT]

Since this seems to be the Tread most relevant to the Urlmon.dll crashes
in
IE6 after applying KB942615 I'll post my experiences with this Patch
here.

In a home environment with Windows XP Home SP2 and IE6, I'm also
experiencing random crashes of IE6 with urlmon.dll as the faulting
module
since manually installing this Update late Tuesday evening.

The following screenshot depicts the Application errors in the Event
Viewer
that are incurred since installing this Update:
http://users.mikrotec.com/danadell/wwwpages/test/urlmonDllErrors.gif

While they are random in nature, as you can see by the screenshot they
are
beginning to amass.

This problem does not exist on the machines with IE7 and KB942615
installed,
only on the machine with IE6 and KB942615 installed.

My two cents worth.

Donald Anadell


When I installed the Patch Tuesday updates on my WXP Box
with MSIE6 installed. I had the same problems with IE6 startup
as others are mentioning in these newsgroups.

Specifically, about 60% of the time, I would get an "Internet
Explorer has encountered a problem and must close" dialog.
I dutifully reported the failure to Microsoft and then repeatedly
tried reopening IE6 until it would successfully open.

The above occurred when opening my default homepage,
which is "My MSN" - and is heavily customized.

Cleaning my Internet Explorer Tempfolder and moving to a
blank opening page solved the problem. However, this was
not an acceptable solution.

I then rebooted the machine, restored my default homepage
and tried opening IE6 again. Now, the machine is working
correctly, even after multiple open/close cycles.


I suspect the KB942615 update should be coded to force a reboot
and does not. Consequently, some part of the update that requires
a reboot before the update is fully applied does not get done.

As a result, installing this update without the reboot causes IE6
to run in a "half-updated/half-not-updated" mode - which causes
the problem described above to occur.

For those experiencing this problem, please try moving to a blank
opening page - and then reboot your machine again after the
KB942615 update is installed. Once this is done, restore your
default homepage. See if this procedure resolves your problem.


Best I can do for now. <tm>


Bill

 

[Kurt Falde [MSFT]]

From what another engineer told me this is right. the fix in 942367
probably did not need to be installed just the registry key needs to be in
place as this fix is already included in the urlmon.dll thats in the update
just released. Thanks for letting me know.

--
Kurt Falde [MSFT]

Hi Kurt,

I received the KB942367 Hotfix and installed it along with the associated
Registry Tweak. Only some time and some heavy Browsing will tell if this
has fixed the Urlmon.dll crashing problem in IE6, so far so good but I'll
give it a few days to see how it goes.

I am a little bewildered as to the version of Urlmon.dll that remains in
the System32 folder and dllcache folder though after applying the hotfix.
The Article(KB942367) implies that the hotfix will install version
6.0.2900.3213 of urlmon.dll(or am I reading that wrong). However, after
applying the hotfix I'm still left with the version of urlmon.dll that was
installed KB942615 Cumulative Security Update, version 6.0.2900.3231.

Does this sound right to you, the hotfix should only patch the existing
urlmon.dll file as long as it is version 6.0.2900.3213(or higher), or is
it supposed to replace the existing version with a specific version? I
extracted all the files from the hotfix setup file and I don't see a
urlmon.dll file included in the setup, maybe it's just the geek speak in
the KB Article that has me looking for something that isn't supposed to be
there)

At any rate,

1. I applied the hotfix offered as you suggested.
2. Performed the Registry Tweak after installing the hotfix(per the
instructions the KB942367 Article).
3. After performing steps one and two, I'm left with urlmon.dll version
6.0.2900.3231 in both the System32 and dllcache folders.

LOL...I'll be glad when SP3 arrives, fixing Updates with hotfixes it
taking it to the extreme for my 60 year old brain

Thanks again for your assistance,

Donald Anadell

Thanks for the feedback Kurt,

I've submitted for the Hotfix, when I get the link back and get it
downloaded and installed I'll post back the results.

Donald Anadell

Please try http://support.microsoft.com/kb/942367 and let us know if
this resolves your issues.
Use the online request form to get the fix.


--
Kurt Falde [MSFT]




Since this seems to be the Tread most relevant to the Urlmon.dll
crashes in
IE6 after applying KB942615 I'll post my experiences with this Patch
here.

In a home environment with Windows XP Home SP2 and IE6, I'm also
experiencing random crashes of IE6 with urlmon.dll as the faulting
module
since manually installing this Update late Tuesday evening.

The following screenshot depicts the Application errors in the Event
Viewer
that are incurred since installing this Update:
http://users.mikrotec.com/danadell/wwwpages/test/urlmonDllErrors.gif

While they are random in nature, as you can see by the screenshot they
are
beginning to amass.

This problem does not exist on the machines with IE7 and KB942615
installed,
only on the machine with IE6 and KB942615 installed.

My two cents worth.

Donald Anadell


When I installed the Patch Tuesday updates on my WXP Box
with MSIE6 installed. I had the same problems with IE6 startup
as others are mentioning in these newsgroups.

Specifically, about 60% of the time, I would get an "Internet
Explorer has encountered a problem and must close" dialog.
I dutifully reported the failure to Microsoft and then repeatedly
tried reopening IE6 until it would successfully open.

The above occurred when opening my default homepage,
which is "My MSN" - and is heavily customized.

Cleaning my Internet Explorer Tempfolder and moving to a
blank opening page solved the problem. However, this was
not an acceptable solution.

I then rebooted the machine, restored my default homepage
and tried opening IE6 again. Now, the machine is working
correctly, even after multiple open/close cycles.


I suspect the KB942615 update should be coded to force a reboot
and does not. Consequently, some part of the update that requires
a reboot before the update is fully applied does not get done.

As a result, installing this update without the reboot causes IE6
to run in a "half-updated/half-not-updated" mode - which causes
the problem described above to occur.

For those experiencing this problem, please try moving to a blank
opening page - and then reboot your machine again after the
KB942615 update is installed. Once this is done, restore your
default homepage. See if this procedure resolves your problem.


Best I can do for now. <tm>


Bill

 

[Bill Drake]

Hi, Kurt. I have now tested the information found on the KB942367
webpage against the new urlmon.dll found in the KB942615 update.

From the testing I have done so far, the Registry Entry item
detailed on the KB942367 page is all that is required to be added
to the system - to allow the KB942615 update to perform reliably.

MSIE6 does not intermittently crash when starting up on my
default home page (My MSN) with this Registry Edit in place.

I did not install the KB942367 update - I simply installed the
KB942613 update and added the Registry Edit specified on
the KB942367 webpage.


From everything I can see here, it would seem to me this Registry
Edit should have been applied as part of the install script for
KB942615 - since the version 6.0.2900.3231 urlmon.dll file shipped
with KB942615 has had the requisite code installed in the DLL all
the way back to version 6.0.2900.3213 - which was released on
Sept 12/07.

Regardless, I will be doing more testing over the next 24 hours in
order to ensure that the system is stable with this new Registry
Entry in place. I will report back to the group once I am reasonably
certain this bugfix is stable.


Best I can do for now. <tm>


Bill

 

[Slow Flyer]

Since the recent updates, I've been sending frequent error reports from IE6
as it closes by itself.
A big "thank you" to Kurt and Bill for posting an explanation so that a home
user can understand the problem and decide what to do.

 

[Donald Anadell]

Thanks for the feedback Kurt.

If the hotfix(KB942367) is already coded into the 6.0.2900.3231 version of
urlmon.dll(KB942615), I'm going to uninstall the hotfix and just run with
the Registry Tweak to see how that works out.

Thanks again for your assistance,

Donald Anadell

From what another engineer told me this is right. the fix in 942367
probably did not need to be installed just the registry key needs to be in
place as this fix is already included in the urlmon.dll thats in the
update just released. Thanks for letting me know.

--
Kurt Falde [MSFT]

Hi Kurt,

I received the KB942367 Hotfix and installed it along with the associated
Registry Tweak. Only some time and some heavy Browsing will tell if this
has fixed the Urlmon.dll crashing problem in IE6, so far so good but I'll
give it a few days to see how it goes.

I am a little bewildered as to the version of Urlmon.dll that remains in
the System32 folder and dllcache folder though after applying the hotfix.
The Article(KB942367) implies that the hotfix will install version
6.0.2900.3213 of urlmon.dll(or am I reading that wrong). However, after
applying the hotfix I'm still left with the version of urlmon.dll that
was installed KB942615 Cumulative Security Update, version 6.0.2900.3231.

Does this sound right to you, the hotfix should only patch the existing
urlmon.dll file as long as it is version 6.0.2900.3213(or higher), or is
it supposed to replace the existing version with a specific version? I
extracted all the files from the hotfix setup file and I don't see a
urlmon.dll file included in the setup, maybe it's just the geek speak in
the KB Article that has me looking for something that isn't supposed to
be there)

At any rate,

1. I applied the hotfix offered as you suggested.
2. Performed the Registry Tweak after installing the hotfix(per the
instructions the KB942367 Article).
3. After performing steps one and two, I'm left with urlmon.dll version
6.0.2900.3231 in both the System32 and dllcache folders.

LOL...I'll be glad when SP3 arrives, fixing Updates with hotfixes it
taking it to the extreme for my 60 year old brain

Thanks again for your assistance,

Donald Anadell

Thanks for the feedback Kurt,

I've submitted for the Hotfix, when I get the link back and get it
downloaded and installed I'll post back the results.

Donald Anadell


Please try http://support.microsoft.com/kb/942367 and let us know if
this resolves your issues.
Use the online request form to get the fix.


--
Kurt Falde [MSFT]




Since this seems to be the Tread most relevant to the Urlmon.dll
crashes in
IE6 after applying KB942615 I'll post my experiences with this Patch
here.

In a home environment with Windows XP Home SP2 and IE6, I'm also
experiencing random crashes of IE6 with urlmon.dll as the faulting
module
since manually installing this Update late Tuesday evening.

The following screenshot depicts the Application errors in the Event
Viewer
that are incurred since installing this Update:
http://users.mikrotec.com/danadell/wwwpages/test/urlmonDllErrors.gif

While they are random in nature, as you can see by the screenshot they
are
beginning to amass.

This problem does not exist on the machines with IE7 and KB942615
installed,
only on the machine with IE6 and KB942615 installed.

My two cents worth.

Donald Anadell


When I installed the Patch Tuesday updates on my WXP Box
with MSIE6 installed. I had the same problems with IE6 startup
as others are mentioning in these newsgroups.

Specifically, about 60% of the time, I would get an "Internet
Explorer has encountered a problem and must close" dialog.
I dutifully reported the failure to Microsoft and then repeatedly
tried reopening IE6 until it would successfully open.

The above occurred when opening my default homepage,
which is "My MSN" - and is heavily customized.

Cleaning my Internet Explorer Tempfolder and moving to a
blank opening page solved the problem. However, this was
not an acceptable solution.

I then rebooted the machine, restored my default homepage
and tried opening IE6 again. Now, the machine is working
correctly, even after multiple open/close cycles.


I suspect the KB942615 update should be coded to force a reboot
and does not. Consequently, some part of the update that requires
a reboot before the update is fully applied does not get done.

As a result, installing this update without the reboot causes IE6
to run in a "half-updated/half-not-updated" mode - which causes
the problem described above to occur.

For those experiencing this problem, please try moving to a blank
opening page - and then reboot your machine again after the
KB942615 update is installed. Once this is done, restore your
default homepage. See if this procedure resolves your problem.


Best I can do for now. <tm>


Bill

 

[Embalmed]

I applied just the registry change for KB942367 and it fixed the
problem I did not install the hot fix. A few more hours of testing to
go and then to push the reg hack out to all the clients.

 

[Ottmar Freudenberger]

From what another engineer told me this is right. the fix in 942367
probably did not need to be installed just the registry key needs to be in
place as this fix is already included in the urlmon.dll thats in the update
just released. Thanks for letting me know.

Thanks jumping in, Kurt!

Now, since the "registry hack" seems to solve the problems with urlmon.dll
running IE6 under Windows XP SP2, wouldn't it be a good idea to revise the
Security Bulletin MS07-069 and the "Known Issues" section there which still
states, that there are no known problems?

Further more, what will the next steps be from MS to really fix the issue
for the average user? The release of a KB942615v2 for IE6 on Windows XP SP2
*inculding* the registry fix or even better, releasing the update package
with a fixed urlmon.dll? Me thinks it's somewhat unacceptable to force
users hacking in the heart and brain of Windows aka the registry themself
and leaving those users in the dark, which will most likely never find the
way into the newsgroups to get aware of the -well- "fix".

In the meantime I've uploaded the registry fix on my little web site the
other day: http://patch-info.de/IE/Downloads/IE6SP2_urlmon_dll-Crash.zip
The zip file contains "IE6SP2_Hotfix_KB942367_aktivieren.reg" which will
import the neccessary "registry hack" into the registry after double
clicking on it and letting it merge into the registry.
"IE6SP2_Hotfix_KB942367_deaktivieren.reg" is included in the zip file too
which will remove the registry keys again in case someone needs too.
Note that the registry fix only works for these IE6 instances, that have
been started *after* applying the registry hack/fix. So it's a good idea
to close *all* opened IE6 windows *before* applying the registry fix.

Bye,
Freudi

 

[georgieb]

Thanks jumping in, Kurt!

Now, since the "registry hack" seems to solve the problems with urlmon.dll
running IE6 under Windows XP SP2, wouldn't it be a good idea to revise the
Security Bulletin MS07-069 and the "Known Issues" section there which still
states, that there are no known problems?

Further more, what will the next steps be from MS to really fix the issue
for the average user? The release of a KB942615v2 for IE6 on Windows XP SP2
*inculding* the registry fix or even better, releasing the update package
with a fixed urlmon.dll? Me thinks it's somewhat unacceptable to force
users hacking in the heart and brain of Windows aka the registry themself
and leaving those users in the dark, which will most likely never find the
way into the newsgroups to get aware of the -well- "fix".

In the meantime I've uploaded the registry fix on my little web site the
other day:http://patch-info.de/IE/Downloads/IE6SP2_urlmon_dll-Crash.zip
The zip file contains "IE6SP2_Hotfix_KB942367_aktivieren.reg" which will
import the neccessary "registry hack" into the registry after double
clicking on it and letting it merge into the registry.
"IE6SP2_Hotfix_KB942367_deaktivieren.reg" is included in the zip file too
which will remove the registry keys again in case someone needs too.
Note that the registry fix only works for these IE6 instances, that have
been started *after* applying the registry hack/fix. So it's a good idea
to close *all* opened IE6 windows *before* applying the registry fix.

Bye,
Freudi

A huge thanks for all your efforts. On the techno radar I have nothing
but a logical mind and an ability to read "plain english" & this post
truly made sense of all the noise (& reassured me that merging
Freudi's file into the Registry would resolve the issue, which it
did). Wish, somehow, that all & sundry struggling with this problem,
fearful of regedit, still posting to various blogs, etc, etc, could
get to this post, download, open, doubleclick & get on with it, if MS
is truly not going to address this (except on a case by case
basis..monstrous & inconceivable from a Customer Service point of view
but???) until maybe the next update in January. In any case, you folks
ROCK ! Glad I found you. Thanks again & until next (I'm sure there
will be one)

 

[~Carol]

Thanks jumping in, Kurt!

Now, since the "registry hack" seems to solve the problems with urlmon.dll
running IE6 under Windows XP SP2, wouldn't it be a good idea to revise the
Security Bulletin MS07-069 and the "Known Issues" section there which still
states, that there are no known problems?

Further more, what will the next steps be from MS to really fix the issue
for the average user? The release of a KB942615v2 for IE6 on Windows XP SP2
*inculding* the registry fix or even better, releasing the update package
with a fixed urlmon.dll? Me thinks it's somewhat unacceptable to force
users hacking in the heart and brain of Windows aka the registry themself
and leaving those users in the dark, which will most likely never find the
way into the newsgroups to get aware of the -well- "fix".

In the meantime I've uploaded the registry fix on my little web site the
other day: http://patch-info.de/IE/Downloads/IE6SP2_urlmon_dll-Crash.zip
The zip file contains "IE6SP2_Hotfix_KB942367_aktivieren.reg" which will
import the neccessary "registry hack" into the registry after double
clicking on it and letting it merge into the registry.
"IE6SP2_Hotfix_KB942367_deaktivieren.reg" is included in the zip file too
which will remove the registry keys again in case someone needs too.
Note that the registry fix only works for these IE6 instances, that have
been started *after* applying the registry hack/fix. So it's a good idea
to close *all* opened IE6 windows *before* applying the registry fix.

Bye,
Freudi

THANK YOU, Freudi! Worked like a charm!
~Carol

 

[Sharkman]

I'm sooo confused... All I want to do is dl the KB. Has it been corrected or
do I have to wait. I dont want to work on the registry at all..

thanks
sharkman

 

[Vince]

I have not updated my machine yet as I am too busy to be on it anyway. I do
however have 85 computers at work that I am getting ready to install the
updates on. But first at my other job one person did install the updates
with the same urlmon issues.

Now I could have easily followed the instructions in the article telling how
to modify the registry but since Freudi took the time to post the reg file
so we could all simply download and run it was great. Saved me time and will
save others that are afraid to go into the registry the fear of doing so.

That said. Freudi you did include a reg file to make it easy to remove the
new key in the future if one wants to. Do you think it necessary to remove
this key when the next cumulative updated comes out or at some time in the
future?

Thanks

 

[Ottmar Freudenberger]

That said. Freudi you did include a reg file to make it easy to remove the
new key in the future if one wants to. Do you think it necessary to remove
this key when the next cumulative updated comes out or at some time in the
future?

I doubt it will be neccessary, but you never know. I'll post in this
very thread *if* MS fixes the issue themself by releasing a "repaired/
repairing" update and in case it's needed to remove the registry key.

You're welcome,
Freudi

 

[Ottmar Freudenberger]

I'm sooo confused... All I want to do is dl the KB.

In case you are using IE6 on Windows XP SP2:

Let KB942615 download and install. Afterwards download
http://patch-info.de/artikel/2007/12/11/435 open it, double click
on the contained IE6SP2_Hotfix_KB942367_aktivieren.reg and approve
to let it merge into the registry.

Has it been corrected

Not yet.

Bye,
Freudi

 

[gem1201]

When I installed the Patch Tuesday updates on my WXP Box
with MSIE6 installed. I had the same problems with IE6 startup
as others are mentioning in these newsgroups.

Specifically, about 60% of the time, I would get an "Internet
Explorer has encountered a problem and must close" dialog.
I dutifully reported the failure to Microsoft and then repeatedly
tried reopening IE6 until it would successfully open.

The above occurred when opening my default homepage,
which is "My MSN" - and is heavily customized.

Cleaning my Internet Explorer Tempfolder and moving to a
blank opening page solved the problem. However, this was
not an acceptable solution.

I then rebooted the machine, restored my default homepage
and tried opening IE6 again. Now, the machine is working
correctly, even after multiple open/close cycles.


I suspect the KB942615 update should be coded to force a reboot
and does not. Consequently, some part of the update that requires
a reboot before the update is fully applied does not get done.

As a result, installing this update without the reboot causes IE6
to run in a "half-updated/half-not-updated" mode - which causes
the problem described above to occur.

For those experiencing this problem, please try moving to a blank
opening page - and then reboot your machine again after the
KB942615 update is installed. Once this is done, restore your
default homepage. See if this procedure resolves your problem.


Best I can do for now. <tm>


Bill

 

[jwillisbarrie]

When I installed the Patch Tuesday updates on my WXP Box
with MSIE6 installed. I had the same problems with IE6 startup
as others are mentioning in these newsgroups.

Specifically, about 60% of the time, I would get an "Internet
Explorer has encountered a problem and must close" dialog.
I dutifully reported the failure to Microsoft and then repeatedly
tried reopening IE6 until it would successfully open.

The above occurred when opening my default homepage,
which is "My MSN" - and is heavily customized.

Cleaning my Internet Explorer Tempfolder and moving to a
blank opening page solved the problem. However, this was
not an acceptable solution.

I then rebooted the machine, restored my default homepage
and tried opening IE6 again. Now, the machine is working
correctly, even after multiple open/close cycles.


I suspect the KB942615 update should be coded to force a reboot
and does not. Consequently, some part of the update that requires
a reboot before the update is fully applied does not get done.

As a result, installing this update without the reboot causes IE6
to run in a "half-updated/half-not-updated" mode - which causes
the problem described above to occur.

For those experiencing this problem, please try moving to a blank
opening page - and then reboot your machine again after the
KB942615 update is installed. Once this is done, restore your
default homepage. See if this procedure resolves your problem.


Best I can do for now. <tm>


Bill

 

[jwillisbarrie]

May be a bit off topic here but if you use Quickbooks. The patch Tuesday
messes up the help system and you will get an error from the web browswer. QB
has an update for that it is in the Answerworks 4.0 do the QB update and make
sure the Answerworks version number is increased to .101 or more.

More see: http://knowledgebase.quickbooks.ca/detail.php?&qbid=QB2202

The Help function doesn't work because of a recent security update from
Microsoft. Their update, released on Dec. 11 via automatic download for
Internet Explorer users, protects your computer from a potential security
vulnerability, but may also affect the Help function in QuickBooks.
Downloading and installing Intuit's update will fully restore the Help
function.

Jim

 

[PA Bear]

It's totally OT. Please begin a new thread.

 

[damkedar]

Thanks for the feedback Kurt.

If the hotfix(KB942367) is already coded into the 6.0.2900.3231 version of
urlmon.dll(KB942615), I'm going to uninstall the hotfix and just run with
the Registry Tweak to see how that works out.

Thanks again for your assistance,

Donald Anadell

From what another engineer told me this is right. the fix in 942367
probably did not need to be installed just the registry key needs to be in
place as this fix is already included in the urlmon.dll thats in the
update just released. Thanks for letting me know.

Hi Kurt,
I received the KB942367 Hotfix and installed it along with the associated
Registry Tweak. Only some time and some heavy Browsing will tell if this
has fixed the Urlmon.dll crashing problem in IE6, so far so good but I'll
give it a few days to see how it goes.
I am a little bewildered as to the version of Urlmon.dll that remains in
the System32 folder and dllcache folder though after applying the hotfix.
The Article(KB942367) implies that the hotfix will install version
6.0.2900.3213 of urlmon.dll(or am I reading that wrong). However, after
applying the hotfix I'm still left with the version of urlmon.dll that
was installed KB942615 Cumulative Security Update, version 6.0.2900.3231.
Does this sound right to you, the hotfix should only patch the existing
urlmon.dll file as long as it is version 6.0.2900.3213(or higher), or is
it supposed to replace the existing version with a specific version? I
extracted all the files from the hotfix setup file and I don't see a
urlmon.dll file included in the setup, maybe it's just the geek speak in
the KB Article that has me looking for something that isn't supposed to
be there)
At any rate,
1. I applied the hotfix offered as you suggested.
2. Performed the Registry Tweak after installing the hotfix(per the
instructions the KB942367 Article).
3. After performing steps one and two, I'm left with urlmon.dll version
6.0.2900.3231 in both the System32 and dllcache folders.
LOL...I'll be glad when SP3 arrives, fixing Updates with hotfixes it
taking it to the extreme for my 60 year old brain
Thanks again for your assistance,
Donald Anadell
Thanks for the feedback Kurt,
I've submitted for the Hotfix, when I get the link back and get it
downloaded and installed I'll post back the results.
Donald Anadell
Please tryhttp://support.microsoft.com/kb/942367and let us know if
this resolves your issues.
Use the online request form to get the fix.
--
Kurt Falde [MSFT]
Since this seems to be the Tread most relevant to the Urlmon.dll
crashes in
IE6 after applying KB942615 I'll post my experiences with this Patch
here.
In a home environment with Windows XP Home SP2 and IE6, I'm also
experiencing random crashes of IE6 with urlmon.dll as the faulting
module
since manually installing this Update late Tuesday evening.
The following screenshot depicts the Application errors in the Event
Viewer
that are incurred since installing this Update:
http://users.mikrotec.com/danadell/wwwpages/test/urlmonDllErrors.gif
While they are random in nature, as you can see by the screenshot they
are
beginning to amass.
This problem does not exist on the machines with IE7 and KB942615
installed,
only on the machine with IE6 and KB942615 installed.
My two cents worth.
Donald Anadell
When I installed the Patch Tuesday updates on my WXP Box
with MSIE6 installed. I had the same problems with IE6 startup
as others are mentioning in these newsgroups.
Specifically, about 60% of the time, I would get an "Internet
Explorer has encountered a problem and must close" dialog.
I dutifully reported the failure to Microsoft and then repeatedly
tried reopening IE6 until it would successfully open.
The above occurred when opening my default homepage,
which is "My MSN" - and is heavily customized.
Cleaning my Internet Explorer Tempfolder and moving to a
blank opening page solved the problem. However, this was
not an acceptable solution.
I then rebooted the machine, restored my default homepage
and tried opening IE6 again. Now, the machine is working
correctly, even after multiple open/close cycles.
I suspect the KB942615 update should be coded to force a reboot
and does not. Consequently, some part of the update that requires
a reboot before the update is fully applied does not get done.
As a result, installing this update without the reboot causes IE6
to run in a "half-updated/half-not-updated" mode - which causes
the problem described above to occur.
For those experiencing this problem, please try moving to a blank
opening page - and then reboot your machine again after the
KB942615 update is installed. Once this is done, restore your
default homepage. See if this procedure resolves your problem.
Best I can do for now. <tm>
Bill- Hide quoted text -

- Show quoted text -

IT IS ALWAYS ADVISABLE TO RESTART WINDOWS AFTER INSTALLING /
UNINSTALLING ANY NEW PROGRAMS / DRIVERS ETC.
I always follow this GOLDEN RULE and have not got any problem due to
such issues.
Kedar

 

[Timothy Daniels]

Damkedar, if everyone else is top-posting in a thread, it is very
annoying to have to bounce down to the bottom to read a
bottom-posting. Here in the Microsoft.* NGs, it's customary
to top-post, or at least to follow the lead of the 1st respondent.
Could you manage to do the same, please?

*TimDaniels*

 

[Vince]

Hi Freudi:

I've been very busy the past couple of weeks and had hidden the original
update to KB942615 on all of the office computers.

I noticed Microsoft came up with a patch to fix the issues with that patch.

Do you know if that patch works ok? Also for the one computer that had the
KB942615 installed I did use your fix. Should I undo your fix before getting
the patch for that update or does it do the samething your patch did?

Thanks
Vince