Reinstalling IE and critical updates

Just a question, out of curiosity. I would assume that if someone
reinstalls the same version of IE, all the security updates that were
previously installed would have to be installed again. Added to that:

I assume that when IE is reinstalled over itself, it does NOT care if it
finds a newer and updated DLL (or whatever) file (like from a critical
update), and that it goes ahead and replaces it, even if it was newer. Is
that correct? (just wondering).

(I would assume it does this in order to help avoiding some potential DLL
hells after the reinstallation).

What version are you referring to?

Regards,
Emrys Davies.




"Bill in Co." wrote in message
...
Just a question, out of curiosity. I would assume that if someone
reinstalls the same version of IE, all the security updates that were
previously installed would have to be installed again. Added to
that:

I assume that when IE is reinstalled over itself, it does NOT care if
it
finds a newer and updated DLL (or whatever) file (like from a critical
update), and that it goes ahead and replaces it, even if it was newer.
Is
that correct? (just wondering).

(I would assume it does this in order to help avoiding some potential
DLL
hells after the reinstallation).

I don't think it matters, does it? It should work the same for IE 5,
5.5, or 6 (I would think), and with, or without, the Service Packs. It's
just a programming concept (either it replaces the newer dlls it finds
during reinstall, or it doesn't)

Emrys Davies wrote:
What version are you referring to?

Regards,
Emrys Davies.


"Bill in Co." wrote in message
...
Just a question, out of curiosity. I would assume that if someone
reinstalls the same version of IE, all the security updates that were
previously installed would have to be installed again. Added to that:

I assume that when IE is reinstalled over itself, it does NOT care if it
finds a newer and updated DLL (or whatever) file (like from a critical
update), and that it goes ahead and replaces it, even if it was newer. Is
that correct? (just wondering).

(I would assume it does this in order to help avoiding some potential DLL
hells after the reinstallation).

Bill in Co. wrote:
I don't think it matters, does it? It should work the same for IE
5,
5.5, or 6 (I would think), and with, or without, the Service Packs.
It's
just a programming concept (either it replaces the newer dlls it
finds
during reinstall, or it doesn't)


It doesn't matter as long as it's a recent version, ie 2 and 3 would
not be included for discussion here.

You've no idea what size a pot you are stirring here do you? The short
answer is yes and no.

Most MS inf files are properly written to only replace files if the
current version is the same or lesser than the one in the source
folder. But iesetup creates a special folder and moves some core ie
files to it only to copy them back once iesetup has completed. It's
unlikely one of those files will be retrograded no matter what it's
current version. The fate of other files is not so clear as various
inf files set their own behavior as to the overwrite issue.

From experiance I can tell you that update 313829 shows that it needs
to be reapplied when it actually doesn't after a reinstall of ie. So
one still has to apply it in order to stop WinUP site from nagging you
to apply it. On the other hand, I do see some comments in some inf
files that suggest some ie files are to be replaced no matter what
version they currently are. So yes, and no. It's always best to
assume that you need to visit WinUP after doing a reinstallation of ie.
That would be the only safe assumption.

I'd like it if ie did start over with a clean sweep, but I don't think
it does. I would never assume it either way though, too complicated.

I think you're right.

I noticed a small web page rendering anomaly after installing one of the
latest IE security updates for my older version of IE (5.5 SP2), so I went
back and reinstalled IE 5.5 SP2, but I noticed it wouldn't overwrite some of
the newer stuff, as you mentioned below.

However, I did manage to isolate this particular and rather unique (but
perhaps pretty insignificant) anomaly to MSHTML.DLL, and hence went back to
the slightly older version (and the slightly older cumulative security
update that installed it).

(It's a long story, not really worth getting into, but it was an interesting
"journey". As you say, best advice is not to mess around with it, but I
sometimes like to live on the edge a bit - LOL).

Lee wrote:
Bill in Co. wrote:
I don't think it matters, does it? It should work the same for IE 5,
5.5, or 6 (I would think), and with, or without, the Service Packs. It's
just a programming concept (either it replaces the newer dlls it finds
during reinstall, or it doesn't)


It doesn't matter as long as it's a recent version, ie 2 and 3 would
not be included for discussion here.

You've no idea what size a pot you are stirring here do you? The short
answer is yes and no.

Most MS inf files are properly written to only replace files if the
current version is the same or lesser than the one in the source
folder. But iesetup creates a special folder and moves some core ie
files to it only to copy them back once iesetup has completed. It's
unlikely one of those files will be retrograded no matter what it's
current version. The fate of other files is not so clear as various
inf files set their own behavior as to the overwrite issue.

From experiance I can tell you that update 313829 shows that it needs
to be reapplied when it actually doesn't after a reinstall of ie. So
one still has to apply it in order to stop WinUP site from nagging you
to apply it. On the other hand, I do see some comments in some inf
files that suggest some ie files are to be replaced no matter what
version they currently are. So yes, and no. It's always best to
assume that you need to visit WinUP after doing a reinstallation of ie.
That would be the only safe assumption.

I'd like it if ie did start over with a clean sweep, but I don't think
it does. I would never assume it either way though, too complicated.