“Eclecticism, (from Greek eklektikos, “selective”), in philosophy and theology, the practice of selecting doctrines from different systems of thought without adopting the whole parent system for each doctrine.” – Encyclopaedia Britannica.
Actually I prefer them, I care only about version and not date.
They are also installed by Windows Update if there aren’t already other drivers, it is probably just to avoid overwriting OEM specific drivers.
Put also an additional case, to prefer version, where Intel still support 2 version branches.
Example (not real versions, just an example):
– 10.1.10 (first to release)
– 10.2.1 (second to release)
– 10.1.14 (third to release)
In this example 10.1.14 have the most recent date but it is only a minor fix for the 10.1 branch where 10.2.1 is the most recent albeit with inferior date.
In my opinion there are only rare cases where the date matters, it is when the versioning scheme is changed.
The only case of changed version scheme that I know is “Intel(R) Dynamic Application Loader Host Interface” where:
– The old version scheme is like this: 19220.127.116.119
– The new version scheme is: 1.37.2020.426
I noticed this strange phenomenon some months ago when I built my new PC and had numerous drivers dated 07/18/1968 after a clean installation. I think you’ll find that they are all registers from the System Devices section of Device Manager.
As strange as it may seem, this is the reason given from Intel.
Intel Chipset Device Software uses an unusual date for the devices it is targeting. The date 07/18/1968 is symbolic – Intel was founded that day. The reason this date is used is to lower the rank of Intel Chipset Device Software. This is necessary because it’s a supporting utility that should not overwrite any other drivers. Updating Intel Chipset Device Software is not needed.