Ye I do the same but it fails to work after reboot, not sure why..

@Fernando:
Sorry, looks like this is my fault.
I have Windows 10 2004 with ASUS X HERO (Z370)
Latest driver on my mobo support page is Version 17.5.0.1017 and it works just by driver update in device manager.
For some reason I thought the new one works too. It does but not after second reboot.
I took new driver here and also from new ASUS XII Hero page.
I think Asus is just lazy updating my mobo support page.

So when I use latest 72 (V17881072) or 65 it does not work after second reboot even with RST installation.

So for example:
I have booted with MS driver - update to 72 - it works - reboot - it works - reboot - (!) mark no HDD in My PC and "A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)" message in device manager.
or
If I remove device and delete driver and update it to 72 right away my HDD will be shown in My PC and will be usable, same after reboot, but after second reboot it wont work.

So it's a bug or this driver is not compatible with my Z370 but for some reason it works once and then it does not.

P.S yes I uninstall RST from CP before updates. But it does not matter same behavior with just driver update via DM

OK I solved the issue.
I rolled back to working version then I decided to check my Autoran setup with Autoran organizer and for some mystery reason the driver name for AHCI was disabled from startup despite working in the same time for old version and not new version.

So basically I did an update as I did 999 times above but with this check enabled in Autoran Manager, I didn't disable drivers, only .exes like RST so it was disabled and working for old driver but not for new one.
After enabling it and installing new version works fine for now.

May be interesting, prev.version (17.8.7.1071) popped up on hp ftp:
full package with cmd installer & appx's in sp102418, just drivers attached here:

Hi Dieter,

My system:
MB: MSI Z390 Godlike
CPU: Intel I9 9900K
GPU: nVidia GTX 980 Ti
System drive: 1Tb M2 NVMe Samsung 970 PRO
HDD: 2TB Seagate
OS: Win10 x64 Enterprise 1909

I have been using your Intel AHCI drivers for years without any problems and thank you for that!
Last year I changed my system and I'm not sure which Inter RST AHCI driver to use.
On the MSI website at Z390 MB, at UEFI Bios latest update changelog, he tells me that:
"Description
- Update RST driver to 17.5
- Update Microcode. "

"17.5" tells me I can't use 17.8.1 or newer 17.8.8 ?!
That confuses me a little.
Does it matter if the BIOS has only been updated to 17.5?
I used only driver not driver & software:
last year: 17.5.3.1026
this year: 17.8.1.1066
and for a few days 17.8.8.1072, which seems a bit slower.
I didn't test the speeds with any program, I say that, it seems so at first sight.
On the M2 I have the original Samsung driver.
At Microsoft Storage Spaces Controller I have the driver by default, I don't know why?
Which do you think is the fastest for my system?
What driver do you recommend?
I don't use RAID, I use M2 for OS and HDD for storage work, movies, music.
Thank you for your help!

Are these drivers fully compatible with Windows 8.1?
I'm trying to install it onto an NVMe RAID created with "RST Premium" on Z390 (ASUS). The installer just doesn't see the array.
I updated the RAID ROM to the latest version and tried different versions of drivers: from 16.5 to 17.8. And the array still doesn't appear in the device list.
Win10 installer detects it immediately on the same system

I might have been wrong with terms.
I created the RAID0 in UEFI Setup menu. Some screens from there: 1 2 3

I couldn't install Windows at all since no disks were visible (like this) and nothing appeared after installing the driver. The installation media is Windows 8.1 x64 build 6051499.

It finally worked after I removed all other drives from the system, although it took around 2 minutes to detect the storage.
The other drives are a software RAID of SATA drives and a single NVMe drive, all "non RST controlled".

After I installed this 17.9.0.1007 driver, it knocked out my Samsung SSD controller. Now my 960pro is being controlled by the intel driver and the Samsung NVME controller is no longer listed in my device manager. Is there a way to fix this?