• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Dave-H

Latest IE6 (SP1) Security Update for Win 9x/ME

95 posts in this topic

I didn't replace iecustom.dll because it didn't exist on my system. It's apparently associated with IE 7 from what I've been able to find.

0

Share this post


Link to post
Share on other sites

Ah, my apologies!

I thought I had patched that file, but when I checked it's only on my XP installation. I think I was confusing it with inetcomm.dll!

:blushing:

iecustom.dll seems to be some sort of setup file, related to IE8 in my case, although an IE6 version of it does seem to be included in the MS patch.

It's almost certainly a file used just by the patch installation process as it isn't actually referenced in the inf file for the patch.

Sorry for the confusion!

:)

0

Share this post


Link to post
Share on other sites

Hi,

* Last update for OE6SP1 (17 files) running just fine here also: MS10-030 (KB978542).

* There were an update for IE6SP1 - Windows 2000 SP4: MS10-035 (KB982381) on June 16, 2010 working fine.

Download here.

* and a Cumulative update for ActiveX Killbits - Windows 2000 SP4: MS10-034 (KB980195)

from where I made a reg file with the 204 killbits.

Download here.

Enjoy. :)

0

Share this post


Link to post
Share on other sites

KB982381 and KB980195 are in the updated MDIE6CU3.4

What's new:

uninstall Cumulative Security Update fix

add:

*931125 - Last Windows Roots Update

*980195 - Unofficial ActiveX Kill Bits (AKB) Security Vulnerability Fix

*982381 - Unofficial Internet Explorer Cumulative Security Update

See the MD thread for download details.

0

Share this post


Link to post
Share on other sites

With the release of IE cumulative update KB2183461, which is available for IE6 under Windows XP here, is it likely that its files will work on Windows 98 IE6 SP1?

Is it only for IE6 SP2? It doesn't actually say that.

Now that support for Windows 2000 has ended, I assumed that support for IE6 SP1 had also ended.

:)

0

Share this post


Link to post
Share on other sites

It *is* for IE6SP2 and up only. The reason that that is not spelt up is that MS considers IE6SP2 the only valid IE6, for some time already. When they meant IE6SP1, they've always said it in full. It's over. I'm sorry!

0

Share this post


Link to post
Share on other sites

The MS page says that the update is intended for Windows XP SP3.

That implies that it is meant only for MS IE 6.0 SP3 installed by XP SP3 service pack.

Because all other older SPs have been phased out, MS doesn't make fixes for those XP editions anymore.

And BTW, files included in SP3 fixes are not compatible with MS IE 6.0 SP1 [98/98SE/ME/2000/XP RTM/XP SP1/XP SP1a/2003 RTM] or MS IE 6.0 SP2 [XP SP2].

HTH

0

Share this post


Link to post
Share on other sites

Thanks Den and MD.

I thought that was probably the case.

I'd better closely guard the copy of KB982381 I saved, just in case it's removed in the future.

I assume this contains the very last files for IE6 SP1, and therefore for Windows 98 (and 2000).

:(

0

Share this post


Link to post
Share on other sites

Is anybody feeling adventurous enough to try WildBill's unofficial KB2360131 files on Win9x/ME?

If they work, and I bet they will, it's the way to keep more up-to-date...

I intend to do so myself, but I won't be able to do so right away. :(

0

Share this post


Link to post
Share on other sites

Is anybody feeling adventurous enough to try WildBill's unofficial KB2360131 files on Win9x/ME?

If they work, and I bet they will, it's the way to keep more up-to-date...

I intend to do so myself, but I won't be able to do so right away. :(

Working fine here on 98SE!

:thumbup

There seem to be only four files in this update -

BROWSEUI.DLL

MSHTML.DLL

MSHTMLED.DLL

SHDOCVW.DLL

They are all later versions than those found in KB982381, except for MSHTMLED.DLL.

That file was never included in any of the IE6 SP1 Cumulative Updates that I hacked over to Windows 98 from Windows 2000 before support was ended.

Also, the version I already had is dated 24th March 2005, and is version 6.0.2800.1501.

The "new" version is dated 31st October 2010, but is version 6.0.2800.1107, which appears to be an earlier version of the file!

I am puzzled.......

:wacko:

0

Share this post


Link to post
Share on other sites
Working fine here on 98SE! :thumbup

That's wonderful news! :yes:

Thanks for the lightnig fast reaction to my post! :thumbup You rock!

So we're back it the game, great!

And I'm sure WildBill will be happy, too, since this widens his updates user basis.

I am puzzled....... :wacko:

I'm sure WildBill will be happy to solve this puzzle. I'll invite him over.

0

Share this post


Link to post
Share on other sites

Hey, all:

I tend to base the updates on the files currently installed on my system. I guess for some reason the newest patch to mshtmled wasn't installed on my PC for some odd reason. I'll see about reapplying the patch to the newer one, but I might wait for the next IE release first. I'm so backlogged with patches it isn't funny, to the point that I'm probably going to release my PE tool shortly and ask for help.

0

Share this post


Link to post
Share on other sites

Hey, all:

I tend to base the updates on the files currently installed on my system. I guess for some reason the newest patch to mshtmled wasn't installed on my PC for some odd reason. I'll see about reapplying the patch to the newer one, but I might wait for the next IE release first. I'm so backlogged with patches it isn't funny, to the point that I'm probably going to release my PE tool shortly and ask for help.

Thanks Bill.

I'll probably put my original version of MSHTMLED.DLL back in that case.

It would be interesting to see what version of that file others have.

As I said, mine is 6.0.2800.1501.

Dave.

:)

0

Share this post


Link to post
Share on other sites

@WildBill: The reason you didn't have KB896156 in your system is that it's a Hotfix (so one has to request it to get it), not a Security Update (which would be offered through Win Update and/or MS Update). Changing subjects, I might be able to help you, once you release the Tool, but you'd have to instruct me about your methods: I'm a programmer myself, I understand reasonably the PE exe format and I'm no stranger to creating patched files, but I saw some pretty complex segment reordering and expanding in your patches, the mechanics of which are not totally clear to me. I'm totally at home hexediting and reasonably confortable with IDA, although I sure have lots more to learn. And I'm very short of time, right now, but that's gonna change soon (I hope). Let's talk via PM about it.

@Dave-H: I use MSHTMLED.DLL v. 6.0.2800.1502 (the qfe branch file), from the same KB896156. Like MDGx, I do prefer the qfe branch files, because they include all mainstream fixes (the cumulative updates in the gdr branch) and all the less well tested fixes, too. It's more probable a qfe file will give problems than its gdr counterpart, and when I suspect such is the case, then I fall back to the gdr file and check whether that's the case or not. However, I've never been able to find any confirmed instance of problems due to my using qfe files: in the rare cases where I had problems with the qfe file, the gdr file also gave me the same problems, so I ended falling back to the previous version of the file. One such case was that IE update that gave rise to this thread. And whatever the reason it gave problems, it was fixed some later versions on, as we all know. :)

0

Share this post


Link to post
Share on other sites
I'll probably put my original version of MSHTMLED.DLL back in that case.

It would be interesting to see what version of that file others have.

As I said, mine is 6.0.2800.1501.

Sure. I did that, too, already.

But while you're at it, do also do update mshtml.dll once more. WildBill just correct a bug in it.

KB2360131-v2, which contains it, is in the same place the original one was.

0

Share this post


Link to post
Share on other sites
I'll probably put my original version of MSHTMLED.DLL back in that case.

It would be interesting to see what version of that file others have.

As I said, mine is 6.0.2800.1501.

Sure. I did that, too, already.

But while you're at it, do also do update mshtml.dll once more. WildBill just correct a bug in it.

KB2360131-v2, which contains it, is in the same place the original one was.

Thanks Den, I've now got the new version.

As you rightly surmised, I had also installed KB896156 at some point, hence my later version of mshtmled.dll.

I'll probably stick with the version I've got rather than the 1502 version, as I've never had any problems with it.

:)

0

Share this post


Link to post
Share on other sites

I wanted to chime in and confirm that the KB2360131 updated system files seem to be working fine in Win98 SE, at least so far. Thank you WildBill for your excellent hard work in creating these Win2000 updates! And thanks dencorso for informing us about them and Dave-H for being the first guinea pig. :)

BTW, I also have the 6.00.2800.1501 version of MSHTMLED.DLL even though I don't remember installing the referenced Hotfix.

0

Share this post


Link to post
Share on other sites
BTW, I also have the 6.00.2800.1501 version of MSHTMLED.DLL even though I don't remember installing the referenced Hotfix.

It's part of MDIE6CU 3.4... that's probably how you and Dave got it.

Me, too. But I updated manually to the qfe branch afterwards, due to my preferring the qfe branch.

0

Share this post


Link to post
Share on other sites

Yeah that's it... from MDIE6CU34E or earlier. Thanks again for letting us know about WildBill's work. I'm thinking about trying to implement some of the other updates too. And I admit I don't really understand the QFE/GDR branch issue you mentioned. I'll have to do some research and reading up on it b/c I've seen those terms around before.

0

Share this post


Link to post
Share on other sites

Sorry for the indigestibly long explanation I pointed to. Here's what matters for our purposes:

GDR packages contain only security and critical stability issue fixes.

LDR packages contain "other" fixes that have not undergone as extensive testing, and resolve issues that only a fraction of the millions of Windows users might ever encounter.

What is not said above is that both those types are cumulative, so that a GDR file contains some new and all previous GDR fixes, while a QFE (= LDR) contains all that the GDR does, plus some new and all previous QFE fixes, being thus more completely fixed, but perhaps more prone to give problems, because less well tested.

Moreover, once a QFE file gets installed, all the future updates to it will always be taken from the QFE branch, too, automagically, from that point onwards (until the next official service pack, which, for 9x/ME, 2k and NT4 or older, will never be issued).

Hope this digests better. :D

0

Share this post


Link to post
Share on other sites

Sorry for the indigestibly long explanation I pointed to. Here's what matters for our purposes:

GDR packages contain only security and critical stability issue fixes.

LDR packages contain "other" fixes that have not undergone as extensive testing, and resolve issues that only a fraction of the millions of Windows users might ever encounter.

What is not said above is that both those types are cumulative, so that a GDR file contains some new and all previous GDR fixes, while a QFE (= LDR) contains all that the GDR does, plus some new and all previous QFE fixes, being thus more completely fixed, but perhaps more prone to give problems, because less well tested.

Moreover, once a QFE file gets installed, all the future updates to it will always be taken from the QFE branch, too, automagically, from that point onwards (until the next official service pack, which, for 9x/ME, 2k and NT4 or older, will never be issued).

Hope this digests better. :D

So the QFE/LDR versions of files contain further fixes, which are not completely tested and now never will be completely tested, or officially issued for systems where support has ended?

That implies that MS have abandoned fixes in mid implementation because the systems they were intended for went out of support.

Seems a strange thing to do, but that's MS for you!

:)

0

Share this post


Link to post
Share on other sites

Well, mostly, the QFE fixes work OK, but they were not deemed serious enough to undergo "full regression testing", whatever that may mean.

The QFE files for 98SE are the core of Gape's pack, for instance and the unofficial update packs for other versions of 9x/ME are based on them, as well, so I think they are very well tested by now and safe to use.

0

Share this post


Link to post
Share on other sites

Well, mostly, the QFE fixes work OK, but they were not deemed serious enough to undergo "full regression testing", whatever that may mean

I believe that means re-validating functionality that was previously validated in an earlier release. In other words, if a software provides functionality A, B, C, D, and a fix is required for functionality B, full regression testing would mean re-validating functionality A, C and D also.

Joe.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.