@Ricks:
Welcome at Win-RAID Forum!
I am sorry for my delayed reply, I obviously missed your post during my holidays.
Now to you question:
You are right: Microsoft misleadingly dates many of their Win10 in-box drivers 06/21/2006, but this does not mean, that these drivers were compiled in 2006. The driver version is exactly the same as the OS version, which verifies, that the related driver is as up-to-date as the OS itself.
By the way: You can find the related date and version of the Intel USB port devices with the DeviceIDs DEV_8C26 and DEV_8C2D within the file named "usbport.inf", which is stored within the D:\Windows\INF folder.
The currently latest official Win10 version is v10.0.16299.15 and has been released by Microsoft in September 2017. Here are the first lines of the usbport.inf:

As you can see, this file is much newer and has a much higher version number than the usbport.inf file of your Win10 version.

Regards
Dieter (alias Fernando)

@Dromadus:
You can find the Intel AHCI driver versions, which I recommend to use with Intel 8-Series Chipset systems, within the start post of >this< thread. Look into the related table, which is near the bottom of that post.
On the other hand the generic Win10 v1709 in-box MS AHCI driver is very good as well. You will probably not realize any performance gain after the replacement by any Intel AHCI driver.

@Dromadus:
Within the related table you can find the Intel RST driver versions, which I recommend to use with Intel 8-Series Chipset systems running in AHCI mode.
JFYI: The CPU model doesn't matter regarding the choice of the best AHCI driver.

@Dromadus:
What about testing them both yourself? This way you can find out, which one is definitively the best for your specific system.
I bet, that you will not realize any noticeable performance difference.

Zitat von onemoar im Beitrag #10

---

exactly what device is (Intel(R) 8 Series/C220 Series USB EHCI #1 - 8C26)

---

Zitat

---

I installed your modded driver for it just wondering what that device is for and why it wasn't covered in your driver inf

---

No wonder (see above).