BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after December Patch Tuesday

  • Thread starter Thread starter Bill Drake
  • Start date Start date
B

Bill Drake

Two days ago, I posted regarding the problem with Internet
Explorer 6 crashing when starting up if the default homepage
was set to "My MSN" and the page was heavily customized.

Other users chimed in to say they were experiencing similar
problems. All the problems resulted in a dialog box saying
that "Internet Explorer has encountered a serious error and
must close". If the user checked the technical info on the
error, the readout confirmed a problem with urlmon.dll.

With the help of several MVPs, other users with the problem,
and Kurt Falde from Microsoft - the problem has now been
localized and a fix has been tested and verified for the last
24 hours.

Those who are experiencing this problem need to make a
Registry Edit after the December Patch Tuesday update
installs the latest Internet Explorer Cumulative Update.
(The technical name for this update is KB942615.)

The problem occurs because the KB942615 update
installs an updated copy of urlmon.dll - but does NOT
install the required Registry Edit that applies the bugfix
so that urlmon.dll works properly in IE6.

The required Registry Entry is as follows:

---------------------begin KB942615FIX.reg--------------------

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Internet Explorer\Main\FeatureControl\
FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB942367]
"*"=dword:00000001

-----------------------end KB942615FIX.reg--------------------

Note: 1. The information within the two square brackets should
all be on ONE line. If your newsgroup reader has split
that information onto two or more lines - remove the
carriage returns so that all the info in between the
square brackets is on the third line in the
KB942615FIX.reg file, and the fourth line starts with "*".

2. There MUST be a blank line at the very bottom of the file.
Do NOT let the last character in the file end at the far
right of the last line. The registry edit will FAIL if there
is not a valid single carriage return as the last item in the
KB942615FIX.reg file.

To make the file and apply the patch:

1. Open Notepad and copy all the information between the
"Begin" and "End" lines above - from the beginning of the
word "Windows" to the beginning of the next line following
"00000001" - into Notepad. Save the notepad file as
KB942615FIX.reg, open Notepad and remove the extra
carriage returns as per Note 1 above. Also confirm the
presence of the final carriage return as per Note 2 above.
Save whatever changes to the KB94615FIX.reg file were
required to bring the file into a workable form.

2. Once you have the working file, close Notepad. Open
Windows Explorer and go to wherever you saved the file.
Double-click the file. Windows will ask you if you want
to merge the data in the Registry file into the Windows
Registry. Click Yes. Windows should respond that it
has successfully merged the KB942615FIX.reg file
info into the Registry.

3. Shut down and reboot your computer. Open Internet
Explorer and navigate to whatever web page was giving
you trouble before. You should now find that Internet
Explorer works properly again, just as it did before the
December version of the Internet Explorer Cumulative
Security Update was installed.


Comment to MVPs:

Kelly, could you please incorporate this info into one of your
Regfix files so the rest of the MVPs can point users at that
entry on your webpage - rather than require that users have
to mess with Notepad and/or Regedit to install this fix?

Thanks for whatever help you can provide.



Best I can do for now. <tm>


Bill
 
"Bill Drake" <bdrake@telus.net> schrieb:

> The problem occurs because the KB942615 update
> installs an updated copy of urlmon.dll - but does NOT
> install the required Registry Edit that applies the bugfix
> so that urlmon.dll works properly in IE6.
>
> The required Registry Entry is as follows:
>
> ---------------------begin KB942615FIX.reg--------------------
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
> Internet Explorer\Main\FeatureControl\
> FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB942367]
> "*"=dword:00000001
>
> -----------------------end KB942615FIX.reg--------------------
>
> Note: 1. The information within the two square brackets should
> all be on ONE line. If your newsgroup reader has split
> that information onto two or more lines - remove the
> carriage returns so that all the info in between the
> square brackets is on the third line in the
> KB942615FIX.reg file, and the fourth line starts with "*".
>
> 2. There MUST be a blank line at the very bottom of the file.
> Do NOT let the last character in the file end at the far
> right of the last line. The registry edit will FAIL if there
> is not a valid single carriage return as the last item in the
> KB942615FIX.reg file.
>
> To make the file and apply the patch:
>
> 1. Open Notepad and copy all the information between the
> "Begin" and "End" lines above - from the beginning of the
> word "Windows" to the beginning of the next line following
> "00000001" - into Notepad. Save the notepad file as
> KB942615FIX.reg, open Notepad and remove the extra
> carriage returns as per Note 1 above. Also confirm the
> presence of the final carriage return as per Note 2 above.
> Save whatever changes to the KB94615FIX.reg file were
> required to bring the file into a workable form.
>
> 2. Once you have the working file, close Notepad. Open
> Windows Explorer and go to wherever you saved the file.
> Double-click the file. Windows will ask you if you want
> to merge the data in the Registry file into the Windows
> Registry. Click Yes. Windows should respond that it
> has successfully merged the KB942615FIX.reg file
> info into the Registry.
>
> 3. Shut down and reboot your computer. Open Internet
> Explorer and navigate to whatever web page was giving
> you trouble before. You should now find that Internet
> Explorer works properly again, just as it did before the
> December version of the Internet Explorer Cumulative
> Security Update was installed.
>
>
> Comment to MVPs:
>
> Kelly, could you please incorporate this info into one of your
> Regfix files so the rest of the MVPs can point users at that
> entry on your webpage - rather than require that users have
> to mess with Notepad and/or Regedit to install this fix?

I'm not Kelly nor an MVP, but you may find
http://groups.google.com/groups?selm=5shfsmF197blgU1@mid.individual.net
useful in the meantime.

BTW: Rebooting Windows or logging out isn't neccessary to get
the "fix" working. Shutting all IE6 windows after or before
applying the "fix" is sufficent.

Bye,
Freudi
 
RE: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after Decembe

As much as I appreciate the help I do not understand a word of the supposed
Fix.
Can you tell us what to do in laymans language please as I am not and I
suspect a lot of others are not PC Literate.

Thanks

"Bill Drake" wrote:

> Two days ago, I posted regarding the problem with Internet
> Explorer 6 crashing when starting up if the default homepage
> was set to "My MSN" and the page was heavily customized.
>
> Other users chimed in to say they were experiencing similar
> problems. All the problems resulted in a dialog box saying
> that "Internet Explorer has encountered a serious error and
> must close". If the user checked the technical info on the
> error, the readout confirmed a problem with urlmon.dll.
>
> With the help of several MVPs, other users with the problem,
> and Kurt Falde from Microsoft - the problem has now been
> localized and a fix has been tested and verified for the last
> 24 hours.
>
> Those who are experiencing this problem need to make a
> Registry Edit after the December Patch Tuesday update
> installs the latest Internet Explorer Cumulative Update.
> (The technical name for this update is KB942615.)
>
> The problem occurs because the KB942615 update
> installs an updated copy of urlmon.dll - but does NOT
> install the required Registry Edit that applies the bugfix
> so that urlmon.dll works properly in IE6.
>
> The required Registry Entry is as follows:
>
> ---------------------begin KB942615FIX.reg--------------------
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
> Internet Explorer\Main\FeatureControl\
> FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB942367]
> "*"=dword:00000001
>
> -----------------------end KB942615FIX.reg--------------------
>
> Note: 1. The information within the two square brackets should
> all be on ONE line. If your newsgroup reader has split
> that information onto two or more lines - remove the
> carriage returns so that all the info in between the
> square brackets is on the third line in the
> KB942615FIX.reg file, and the fourth line starts with "*".
>
> 2. There MUST be a blank line at the very bottom of the file.
> Do NOT let the last character in the file end at the far
> right of the last line. The registry edit will FAIL if there
> is not a valid single carriage return as the last item in the
> KB942615FIX.reg file.
>
> To make the file and apply the patch:
>
> 1. Open Notepad and copy all the information between the
> "Begin" and "End" lines above - from the beginning of the
> word "Windows" to the beginning of the next line following
> "00000001" - into Notepad. Save the notepad file as
> KB942615FIX.reg, open Notepad and remove the extra
> carriage returns as per Note 1 above. Also confirm the
> presence of the final carriage return as per Note 2 above.
> Save whatever changes to the KB94615FIX.reg file were
> required to bring the file into a workable form.
>
> 2. Once you have the working file, close Notepad. Open
> Windows Explorer and go to wherever you saved the file.
> Double-click the file. Windows will ask you if you want
> to merge the data in the Registry file into the Windows
> Registry. Click Yes. Windows should respond that it
> has successfully merged the KB942615FIX.reg file
> info into the Registry.
>
> 3. Shut down and reboot your computer. Open Internet
> Explorer and navigate to whatever web page was giving
> you trouble before. You should now find that Internet
> Explorer works properly again, just as it did before the
> December version of the Internet Explorer Cumulative
> Security Update was installed.
>
>
> Comment to MVPs:
>
> Kelly, could you please incorporate this info into one of your
> Regfix files so the rest of the MVPs can point users at that
> entry on your webpage - rather than require that users have
> to mess with Notepad and/or Regedit to install this fix?
>
> Thanks for whatever help you can provide.
>
>
>
> Best I can do for now. <tm>
>
>
> Bill
>
>
>
>
>
 
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after Decembe

Hi, Peter. If you don't understand this, then you wait for the
bugfix regfile that I asked Kelly (one of the MS MVPs) to create.

Note: This work is NOT something that should be attempted by
those who are unable to read, comprehend and follow
instructions. If you aren't willing or able to deal with this
in a competent technical manner, DON'T do the work.

Bill


Peter wrote:
> As much as I appreciate the help I do not understand a word of the
> supposed Fix.
> Can you tell us what to do in laymans language please as I am not
> and I suspect a lot of others are not PC Literate.
>
> Thanks
>
> "Bill Drake" wrote:
>
>> Two days ago, I posted regarding the problem with Internet
>> Explorer 6 crashing when starting up if the default homepage
>> was set to "My MSN" and the page was heavily customized.
>>
>> Other users chimed in to say they were experiencing similar
>> problems. All the problems resulted in a dialog box saying
>> that "Internet Explorer has encountered a serious error and
>> must close". If the user checked the technical info on the
>> error, the readout confirmed a problem with urlmon.dll.
>>
>> With the help of several MVPs, other users with the problem,
>> and Kurt Falde from Microsoft - the problem has now been
>> localized and a fix has been tested and verified for the last
>> 24 hours.
>>
>> Those who are experiencing this problem need to make a
>> Registry Edit after the December Patch Tuesday update
>> installs the latest Internet Explorer Cumulative Update.
>> (The technical name for this update is KB942615.)
>>
>> The problem occurs because the KB942615 update
>> installs an updated copy of urlmon.dll - but does NOT
>> install the required Registry Edit that applies the bugfix
>> so that urlmon.dll works properly in IE6.
>>
>> The required Registry Entry is as follows:
>>
>> ---------------------begin KB942615FIX.reg--------------------
>>
>> Windows Registry Editor Version 5.00
>>
>> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
>> Internet Explorer\Main\FeatureControl\
>> FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB942367]
>> "*"=dword:00000001
>>
>> -----------------------end KB942615FIX.reg--------------------
>>
>> Note: 1. The information within the two square brackets should
>> all be on ONE line. If your newsgroup reader has split
>> that information onto two or more lines - remove the
>> carriage returns so that all the info in between the
>> square brackets is on the third line in the
>> KB942615FIX.reg file, and the fourth line starts with
>> "*".
>>
>> 2. There MUST be a blank line at the very bottom of the
>> file. Do NOT let the last character in the file end
>> at the far right of the last line. The registry edit
>> will FAIL if there is not a valid single carriage
>> return as the last item in the KB942615FIX.reg file.
>>
>> To make the file and apply the patch:
>>
>> 1. Open Notepad and copy all the information between the
>> "Begin" and "End" lines above - from the beginning of the
>> word "Windows" to the beginning of the next line following
>> "00000001" - into Notepad. Save the notepad file as
>> KB942615FIX.reg, open Notepad and remove the extra
>> carriage returns as per Note 1 above. Also confirm the
>> presence of the final carriage return as per Note 2 above.
>> Save whatever changes to the KB94615FIX.reg file were
>> required to bring the file into a workable form.
>>
>> 2. Once you have the working file, close Notepad. Open
>> Windows Explorer and go to wherever you saved the file.
>> Double-click the file. Windows will ask you if you want
>> to merge the data in the Registry file into the Windows
>> Registry. Click Yes. Windows should respond that it
>> has successfully merged the KB942615FIX.reg file
>> info into the Registry.
>>
>> 3. Shut down and reboot your computer. Open Internet
>> Explorer and navigate to whatever web page was giving
>> you trouble before. You should now find that Internet
>> Explorer works properly again, just as it did before the
>> December version of the Internet Explorer Cumulative
>> Security Update was installed.
>>
>>
>> Comment to MVPs:
>>
>> Kelly, could you please incorporate this info into one of your
>> Regfix files so the rest of the MVPs can point users at that
>> entry on your webpage - rather than require that users have
>> to mess with Notepad and/or Regedit to install this fix?
>>
>> Thanks for whatever help you can provide.
>>
>>
>>
>> Best I can do for now. <tm>
>>
>>
>> Bill
 
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after Dec

Thanks Bill.

"Bill Drake" wrote:

> Hi, Peter. If you don't understand this, then you wait for the
> bugfix regfile that I asked Kelly (one of the MS MVPs) to create.
>
> Note: This work is NOT something that should be attempted by
> those who are unable to read, comprehend and follow
> instructions. If you aren't willing or able to deal with this
> in a competent technical manner, DON'T do the work.
>
> Bill
>
>
> Peter wrote:
> > As much as I appreciate the help I do not understand a word of the
> > supposed Fix.
> > Can you tell us what to do in laymans language please as I am not
> > and I suspect a lot of others are not PC Literate.
> >
> > Thanks
> >
> > "Bill Drake" wrote:
> >
> >> Two days ago, I posted regarding the problem with Internet
> >> Explorer 6 crashing when starting up if the default homepage
> >> was set to "My MSN" and the page was heavily customized.
> >>
> >> Other users chimed in to say they were experiencing similar
> >> problems. All the problems resulted in a dialog box saying
> >> that "Internet Explorer has encountered a serious error and
> >> must close". If the user checked the technical info on the
> >> error, the readout confirmed a problem with urlmon.dll.
> >>
> >> With the help of several MVPs, other users with the problem,
> >> and Kurt Falde from Microsoft - the problem has now been
> >> localized and a fix has been tested and verified for the last
> >> 24 hours.
> >>
> >> Those who are experiencing this problem need to make a
> >> Registry Edit after the December Patch Tuesday update
> >> installs the latest Internet Explorer Cumulative Update.
> >> (The technical name for this update is KB942615.)
> >>
> >> The problem occurs because the KB942615 update
> >> installs an updated copy of urlmon.dll - but does NOT
> >> install the required Registry Edit that applies the bugfix
> >> so that urlmon.dll works properly in IE6.
> >>
> >> The required Registry Entry is as follows:
> >>
> >> ---------------------begin KB942615FIX.reg--------------------
> >>
> >> Windows Registry Editor Version 5.00
> >>
> >> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
> >> Internet Explorer\Main\FeatureControl\
> >> FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB942367]
> >> "*"=dword:00000001
> >>
> >> -----------------------end KB942615FIX.reg--------------------
> >>
> >> Note: 1. The information within the two square brackets should
> >> all be on ONE line. If your newsgroup reader has split
> >> that information onto two or more lines - remove the
> >> carriage returns so that all the info in between the
> >> square brackets is on the third line in the
> >> KB942615FIX.reg file, and the fourth line starts with
> >> "*".
> >>
> >> 2. There MUST be a blank line at the very bottom of the
> >> file. Do NOT let the last character in the file end
> >> at the far right of the last line. The registry edit
> >> will FAIL if there is not a valid single carriage
> >> return as the last item in the KB942615FIX.reg file.
> >>
> >> To make the file and apply the patch:
> >>
> >> 1. Open Notepad and copy all the information between the
> >> "Begin" and "End" lines above - from the beginning of the
> >> word "Windows" to the beginning of the next line following
> >> "00000001" - into Notepad. Save the notepad file as
> >> KB942615FIX.reg, open Notepad and remove the extra
> >> carriage returns as per Note 1 above. Also confirm the
> >> presence of the final carriage return as per Note 2 above.
> >> Save whatever changes to the KB94615FIX.reg file were
> >> required to bring the file into a workable form.
> >>
> >> 2. Once you have the working file, close Notepad. Open
> >> Windows Explorer and go to wherever you saved the file.
> >> Double-click the file. Windows will ask you if you want
> >> to merge the data in the Registry file into the Windows
> >> Registry. Click Yes. Windows should respond that it
> >> has successfully merged the KB942615FIX.reg file
> >> info into the Registry.
> >>
> >> 3. Shut down and reboot your computer. Open Internet
> >> Explorer and navigate to whatever web page was giving
> >> you trouble before. You should now find that Internet
> >> Explorer works properly again, just as it did before the
> >> December version of the Internet Explorer Cumulative
> >> Security Update was installed.
> >>
> >>
> >> Comment to MVPs:
> >>
> >> Kelly, could you please incorporate this info into one of your
> >> Regfix files so the rest of the MVPs can point users at that
> >> entry on your webpage - rather than require that users have
> >> to mess with Notepad and/or Regedit to install this fix?
> >>
> >> Thanks for whatever help you can provide.
> >>
> >>
> >>
> >> Best I can do for now. <tm>
> >>
> >>
> >> Bill
>
>
>
>
 
>Two days ago, I posted regarding the problem with Internet
>Explorer 6 crashing when starting up if the default homepage
>was set to "My MSN" and the page was heavily customized.
>
>Other users chimed in to say they were experiencing similar
>problems. All the problems resulted in a dialog box saying
>that "Internet Explorer has encountered a serious error and
>must close". If the user checked the technical info on the
>error, the readout confirmed a problem with urlmon.dll.
>
>With the help of several MVPs, other users with the problem,
>and Kurt Falde from Microsoft - the problem has now been
>localized and a fix has been tested and verified for the last
>24 hours.
>
>Those who are experiencing this problem need to make a
>Registry Edit after the December Patch Tuesday update
>installs the latest Internet Explorer Cumulative Update.
>(The technical name for this update is KB942615.)
>
>The problem occurs because the KB942615 update
>installs an updated copy of urlmon.dll - but does NOT
>install the required Registry Edit that applies the bugfix
>so that urlmon.dll works properly in IE6.
>
>The required Registry Entry is as follows:

I have seen this crashing occur at my installation as well and
hopefully it will be address very soon.

- Thee Chicago Wolf
 
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after Decembe

>As much as I appreciate the help I do not understand a word of the supposed
>Fix.
>Can you tell us what to do in laymans language please as I am not and I
>suspect a lot of others are not PC Literate.

Here's what you do:

1. Start > Run > type in notepad.exe and press enter.
2. Copy and paste into the notepad body the following

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet
Explorer\Main\FeatureControl\FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB942367]
"*"=dword:00000001

3. File > Save As

A: FIle Name = IE6-crash-fix.reg
B: Save As Type: All Files
C: ANSI

4. This will save it to your desktop and should have a green cube-ish
icon. Double click it and it will ask you to "Add the information..."
so just click OK.

DOne.

- Thee Chicago Wolf
 
the fix as attachement


"Bill Drake" <bdrake@telus.net> wrote in message
news:OD5or4rPIHA.5400@TK2MSFTNGP04.phx.gbl...
> Two days ago, I posted regarding the problem with Internet
> Explorer 6 crashing when starting up if the default homepage
> was set to "My MSN" and the page was heavily customized.
>
> Other users chimed in to say they were experiencing similar
> problems. All the problems resulted in a dialog box saying
> that "Internet Explorer has encountered a serious error and
> must close". If the user checked the technical info on the
> error, the readout confirmed a problem with urlmon.dll.
>
> With the help of several MVPs, other users with the problem,
> and Kurt Falde from Microsoft - the problem has now been
> localized and a fix has been tested and verified for the last
> 24 hours.
>
> Those who are experiencing this problem need to make a
> Registry Edit after the December Patch Tuesday update
> installs the latest Internet Explorer Cumulative Update.
> (The technical name for this update is KB942615.)
>
> The problem occurs because the KB942615 update
> installs an updated copy of urlmon.dll - but does NOT
> install the required Registry Edit that applies the bugfix
> so that urlmon.dll works properly in IE6.
>
> The required Registry Entry is as follows:
>
> ---------------------begin KB942615FIX.reg--------------------
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
> Internet Explorer\Main\FeatureControl\
> FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB942367]
> "*"=dword:00000001
>
> -----------------------end KB942615FIX.reg--------------------
>
> Note: 1. The information within the two square brackets should
> all be on ONE line. If your newsgroup reader has split
> that information onto two or more lines - remove the
> carriage returns so that all the info in between the
> square brackets is on the third line in the
> KB942615FIX.reg file, and the fourth line starts with "*".
>
> 2. There MUST be a blank line at the very bottom of the file.
> Do NOT let the last character in the file end at the far
> right of the last line. The registry edit will FAIL if
> there
> is not a valid single carriage return as the last item in
> the
> KB942615FIX.reg file.
>
> To make the file and apply the patch:
>
> 1. Open Notepad and copy all the information between the
> "Begin" and "End" lines above - from the beginning of the
> word "Windows" to the beginning of the next line following
> "00000001" - into Notepad. Save the notepad file as
> KB942615FIX.reg, open Notepad and remove the extra
> carriage returns as per Note 1 above. Also confirm the
> presence of the final carriage return as per Note 2 above.
> Save whatever changes to the KB94615FIX.reg file were
> required to bring the file into a workable form.
>
> 2. Once you have the working file, close Notepad. Open
> Windows Explorer and go to wherever you saved the file.
> Double-click the file. Windows will ask you if you want
> to merge the data in the Registry file into the Windows
> Registry. Click Yes. Windows should respond that it
> has successfully merged the KB942615FIX.reg file
> info into the Registry.
>
> 3. Shut down and reboot your computer. Open Internet
> Explorer and navigate to whatever web page was giving
> you trouble before. You should now find that Internet
> Explorer works properly again, just as it did before the
> December version of the Internet Explorer Cumulative
> Security Update was installed.
>
>
> Comment to MVPs:
>
> Kelly, could you please incorporate this info into one of your
> Regfix files so the rest of the MVPs can point users at that
> entry on your webpage - rather than require that users have
> to mess with Notepad and/or Regedit to install this fix?
>
> Thanks for whatever help you can provide.
>
>
>
> Best I can do for now. <tm>
>
>
> Bill
>
>
>
>
 
Plato wrote:
> Bill Drake wrote:
>>
>> Two days ago, I posted regarding the problem with Internet
>> Explorer 6 crashing when starting up if the default homepage
>
> Use Firefox.

Can't. Firefox causes the cat to develop warts.
 
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after Dec

"realcestmoi" wrote:

> the fix as attachement
>
>
> "Bill Drake" <bdrake@telus.net> wrote in message
> news:OD5or4rPIHA.5400@TK2MSFTNGP04.phx.gbl...
> > Two days ago, I posted regarding the problem with Internet
> > Explorer 6 crashing when starting up if the default homepage
> > was set to "My MSN" and the page was heavily customized.
> >
> > Other users chimed in to say they were experiencing similar
> > problems. All the problems resulted in a dialog box saying
> > that "Internet Explorer has encountered a serious error and
> > must close". If the user checked the technical info on the
> > error, the readout confirmed a problem with urlmon.dll.
> >
> > With the help of several MVPs, other users with the problem,
> > and Kurt Falde from Microsoft - the problem has now been
> > localized and a fix has been tested and verified for the last
> > 24 hours.
> >
> > Those who are experiencing this problem need to make a
> > Registry Edit after the December Patch Tuesday update
> > installs the latest Internet Explorer Cumulative Update.
> > (The technical name for this update is KB942615.)
> >
> > The problem occurs because the KB942615 update
> > installs an updated copy of urlmon.dll - but does NOT
> > install the required Registry Edit that applies the bugfix
> > so that urlmon.dll works properly in IE6.
> >
> > The required Registry Entry is as follows:
> >
> > ---------------------begin KB942615FIX.reg--------------------
> >
> > Windows Registry Editor Version 5.00
> >
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
> > Internet Explorer\Main\FeatureControl\
> > FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB942367]
> > "*"=dword:00000001
> >
> > -----------------------end KB942615FIX.reg--------------------
> >
> > Note: 1. The information within the two square brackets should
> > all be on ONE line. If your newsgroup reader has split
> > that information onto two or more lines - remove the
> > carriage returns so that all the info in between the
> > square brackets is on the third line in the
> > KB942615FIX.reg file, and the fourth line starts with "*".
> >
> > 2. There MUST be a blank line at the very bottom of the file.
> > Do NOT let the last character in the file end at the far
> > right of the last line. The registry edit will FAIL if
> > there
> > is not a valid single carriage return as the last item in
> > the
> > KB942615FIX.reg file.
> >
> > To make the file and apply the patch:
> >
> > 1. Open Notepad and copy all the information between the
> > "Begin" and "End" lines above - from the beginning of the
> > word "Windows" to the beginning of the next line following
> > "00000001" - into Notepad. Save the notepad file as
> > KB942615FIX.reg, open Notepad and remove the extra
> > carriage returns as per Note 1 above. Also confirm the
> > presence of the final carriage return as per Note 2 above.
> > Save whatever changes to the KB94615FIX.reg file were
> > required to bring the file into a workable form.
> >
> > 2. Once you have the working file, close Notepad. Open
> > Windows Explorer and go to wherever you saved the file.
> > Double-click the file. Windows will ask you if you want
> > to merge the data in the Registry file into the Windows
> > Registry. Click Yes. Windows should respond that it
> > has successfully merged the KB942615FIX.reg file
> > info into the Registry.
> >
> > 3. Shut down and reboot your computer. Open Internet
> > Explorer and navigate to whatever web page was giving
> > you trouble before. You should now find that Internet
> > Explorer works properly again, just as it did before the
> > December version of the Internet Explorer Cumulative
> > Security Update was installed.
> >
> >
> > Comment to MVPs:
> >
> > Kelly, could you please incorporate this info into one of your
> > Regfix files so the rest of the MVPs can point users at that
> > entry on your webpage - rather than require that users have
> > to mess with Notepad and/or Regedit to install this fix?
> >
> > Thanks for whatever help you can provide.
> >
> >
> >
> > Best I can do for now. <tm>
> >
> >
> > Bill
> >
> >
> >
> >
> Looks like MS found a way to shove IE7 down our throats.I had the same problem after that update.I uninstalled the update,installed IE7 wich reinstall the update again,but with IE7 the problem went away.
>
>
 
Just curious about why something happened!

I was one of users who experienced problems with IE6.
Uninstalled it - everything OK for few days.

Still following the threads I picked up your attached regfix file, then
reinstalled KB942615 along with the other two KB which I had removed because
during initial removal of 942615 a dialog box indicated that two other KB's
(can't remember what they were) might not function.

After reinstall, rebooted and applied your regfix file. After merging, I
ran regedit, navigated to location where new key should have been. Wasn't
there???

So I manually added key and dword. Why could I not see the new key when I
first checked. Should I have rebooted after appling your regfix file?

For the record - everything seems to be functioning alright with IE now.

Running XO Pro V 2002 SP2

<clipped>
 
Are you running an Antivirus/Antispyware/Firewall application which
blocks Regedit merges from Windows Explorer? If so, the merge
will fail.

When you got the merge-request confirmation-dialog, did you
click Yes? Clicking No will abort the merge.

Did you get the merge-acknowledgement dialog telling you
the merge occurred? If you got a merge-rejected dialog
instead, then the merge was aborted.


And finally, there is also a change that can be made to Regedit's
handling of items double-clicked from Explorer. Regedit can be
set so it does NOT default to merging the Regfile when clicked.

If you have this change on your system (recommended by Aumha),
then you must right-click on the Regfile and select the "Merge"
function from the context-menu to get the Regfile to merge with the
Registry.

Doing the Regedit manually is certainly OK, it's just more
error-prone as far as mistyping is concerned.

Hope this helps your understanding.


Bill


skeet3 wrote:
> Just curious about why something happened!
>
> I was one of users who experienced problems with IE6.
> Uninstalled it - everything OK for few days.
>
> Still following the threads I picked up your attached regfix file,
> then reinstalled KB942615 along with the other two KB which I had
> removed because during initial removal of 942615 a dialog box
> indicated that two other KB's (can't remember what they were) might
> not function.
> After reinstall, rebooted and applied your regfix file. After
> merging, I ran regedit, navigated to location where new key should
> have been. Wasn't there???
>
> So I manually added key and dword. Why could I not see the new key
> when I first checked. Should I have rebooted after appling your
> regfix file?
> For the record - everything seems to be functioning alright with IE
> now.
> Running XO Pro V 2002 SP2
>
> <clipped>
 
Hi there,

The registry is being processed during boot: so yes you willl have to reboot
after applying the regfix file;)

Best regards,
Michel Denie

"skeet3" <adssuck@adssuck.net> wrote in message
news:%23LF0$u0PIHA.2376@TK2MSFTNGP02.phx.gbl...
> Just curious about why something happened!
>
> I was one of users who experienced problems with IE6.
> Uninstalled it - everything OK for few days.
>
> Still following the threads I picked up your attached regfix file, then
> reinstalled KB942615 along with the other two KB which I had removed
> because during initial removal of 942615 a dialog box indicated that two
> other KB's (can't remember what they were) might not function.
>
> After reinstall, rebooted and applied your regfix file. After merging, I
> ran regedit, navigated to location where new key should have been. Wasn't
> there???
>
> So I manually added key and dword. Why could I not see the new key when I
> first checked. Should I have rebooted after appling your regfix file?
>
> For the record - everything seems to be functioning alright with IE now.
>
> Running XO Pro V 2002 SP2
>
> <clipped>
>
 
HeyBub wrote:
>
> >> Two days ago, I posted regarding the problem with Internet
> >> Explorer 6 crashing when starting up if the default homepage
> >
> > Use Firefox.
>
> Can't. Firefox causes the cat to develop warts.

Cats are disposable :)














--
http://www.bootdisk.com/
 
A reboot is NOT necessary, but you must close all running instances of IE
before IE will use the new setting.

Here is the link to the Microsoft KB article that explains how to add the
fix manually using REGEDIT

http://support.microsoft.com/default.aspx/kb/942367

KB942615 updates "Urlmon.dll" to version 6.0.2900.3231, dated 11-Oct-07
12:57:40, and has the same filesize. I guess they didn't fix the problem in
this version of the DLL, or they made other changes that expose this problem
to a wider audience.

"realcestmoi" <mdenie@dutchweb.nl> wrote in message
news:e3$v923PIHA.2208@TK2MSFTNGP06.phx.gbl...
> Hi there,
>
> The registry is being processed during boot: so yes you willl have to
> reboot after applying the regfix file;)
>
> Best regards,
> Michel Denie
>
> "skeet3" <adssuck@adssuck.net> wrote in message
> news:%23LF0$u0PIHA.2376@TK2MSFTNGP02.phx.gbl...
>> Just curious about why something happened!
>>
>> I was one of users who experienced problems with IE6.
>> Uninstalled it - everything OK for few days.
>>
>> Still following the threads I picked up your attached regfix file, then
>> reinstalled KB942615 along with the other two KB which I had removed
>> because during initial removal of 942615 a dialog box indicated that two
>> other KB's (can't remember what they were) might not function.
>>
>> After reinstall, rebooted and applied your regfix file. After merging, I
>> ran regedit, navigated to location where new key should have been.
>> Wasn't there???
>>
>> So I manually added key and dword. Why could I not see the new key when
>> I first checked. Should I have rebooted after appling your regfix file?
>>
>> For the record - everything seems to be functioning alright with IE now.
>>
>> Running XO Pro V 2002 SP2
>>
>> <clipped>
>>
>
>
 
"realcestmoi" <mdenie@dutchweb.nl> schrieb:

> The registry is being processed during boot: so yes you willl have to reboot
> after applying the regfix file;)

Nope, that's simply *not* true for the *IE6 on Windows XP SP2* registry
"hack" originating from MSKB article KB942367. You'll have to simply
shut down all opened IE6 windows and that's all. Don't believe me? Okay,
test it yourself. I did.

Bye,
Freudi
 
"Thrill5" <nospam@somewhere.com> schrieb:

>A reboot is NOT necessary, but you must close all running instances of IE
> before IE will use the new setting.

Correct :-)

Bye,
Freudi
 
Appreciate your comments. See answers below. I know for sure I didn't
reboot and based on other resonses - I'm not sure whether or not I should
have. In any event, the fix is in the registry, and all's well. Now I
just wait for next month's fiasco.

Thanks again.

"Bill Drake" <bdrake@telus.net> wrote in message
news:O%23LAM42PIHA.1208@TK2MSFTNGP05.phx.gbl...
> Are you running an Antivirus/Antispyware/Firewall application which
> blocks Regedit merges from Windows Explorer? If so, the merge
> will fail. ------- Yes, but I have that function disabled.
>
> When you got the merge-request confirmation-dialog, did you
> click Yes? Clicking No will abort the merge. ----- Got the dialog box,
> but I clicked Yes!
>
> Did you get the merge-acknowledgement dialog telling you
> the merge occurred? If you got a merge-rejected dialog
> instead, then the merge was aborted. ---- I would swear that the final
> dialog box I got was the confirmation box, unless I didn't read it
> carefully!
>
>
> And finally, there is also a change that can be made to Regedit's
> handling of items double-clicked from Explorer. Regedit can be
> set so it does NOT default to merging the Regfile when clicked.
>
> If you have this change on your system (recommended by Aumha),
> then you must right-click on the Regfile and select the "Merge"
> function from the context-menu to get the Regfile to merge with the
> Registry. ------ I know for sure sure that I used the context-menu merge
> method -- not the double click. In fact, I did an edit on the file just to
> file what was there. Can't be to careful nowdays. :):)
>
> Doing the Regedit manually is certainly OK, it's just more
> error-prone as far as mistyping is concerned.
>
> Hope this helps your understanding.
>
>
> Bill
>
>
> skeet3 wrote:
>> Just curious about why something happened!
>>
>> I was one of users who experienced problems with IE6.
>> Uninstalled it - everything OK for few days.
>>
>> Still following the threads I picked up your attached regfix file,
>> then reinstalled KB942615 along with the other two KB which I had
>> removed because during initial removal of 942615 a dialog box
>> indicated that two other KB's (can't remember what they were) might
>> not function.
>> After reinstall, rebooted and applied your regfix file. After
>> merging, I ran regedit, navigated to location where new key should
>> have been. Wasn't there???
>>
>> So I manually added key and dword. Why could I not see the new key
>> when I first checked. Should I have rebooted after appling your
>> regfix file?
>> For the record - everything seems to be functioning alright with IE
>> now.
>> Running XO Pro V 2002 SP2
>>
>> <clipped>
>
>
>
 
Back
Top