@Fernando It works thanks, I will still test with the MS drivers
In some cases with Crystal Disk Mark (Seq among others), the 980 Pro (PCIe 30) is less efficient than the 970 EVO Plus

@Fernando For me, I have the message "Installing this device driver is not recommended because Windows could not verify its compatibility.... "
And indeed, the ID of the 980 Pro is not listed in the driver (.inf)

ID of 980 Pro : PCI\VEN_144D&DEV_A80A&SUBSYS

Yes, Samsung driver works very good
I'll test with MS driver

I integrate the drivers into the ISO, and the Samsung driver will not work with the 980 Pro (without manual installation)

Thanks

Hi

I tested with MS drivers, is it is a little worse than with Samsung drivers in some cases

Otherwise the 970 EVO Plus is a little better (4k write)

Just an FYI for ASMedia SATA and Windows 10:

- you can install old Windows 7 drivers by manually going to Update Driver and pointing to old drivers (don't use installers, they break on W10)

- your generic SATA driver will now become ASMedia 106x and it WILL have Policies tab where you can disable Hot swap / Hot plug / Safely remove, just like it was in W7

* untested drawback might be that I haven't tested if performance drops compared to the generic MS W10 drivers, or system stability
* another drawback is that your W10 might boot into a Blue Screen of Death - just reboot, press F8, boot into Safe Mode, restart, and it should boot into W10 properly

On the other hand, using modern (2.x.x or 3.x.x.x) drivers however DO NOT have the Policies tab.
Also, the installed ASMedia in Device Manager isn't treated as IDE ATA/ATAPI Controller (like for example Intel's SATA driver is) but it's under Storage Controllers.

And if you look in Registy you can notice that this ASMedia driver doesn't have ENUM key, which means it might not even be in use.
Also, since there isn't the Policies tab to make drives not-hot plug, you can still use the old workaround by editing STORAHCI and adding "TreatAsInternalPort" and it will make drives behave as internal - just search on the superuser website with this keyword.

Franky, I don't know whats worse - using W7 ASMedia drivers on W10, but having no idea if you're gimping your system OR using W10 ASmedia drivers, but hiding drives for generic MS SATA driver, which could mean that W10 driver isn't actually used at all. OR actually just not installing ASMedia at all and use default MS SATA driver, and hide problematic drives as described.

If someone can shed some light on this, I'd be grateful.

@Fernando:
Go to Device Manager, open ASMedia SATA 106x Controller, and see if you have Policies tab with 3.x.x.x drivers:

(this is how proper 1.x.x ASMedia drivers on Win7 look like)

Now go to BIOS and try to disable Hot plug/Hot swap/External options for disks connected to ASMedia SATA Controller.
You probably won't even find the option for ASMedia in BIOS, usually only for Intel's SATA Controller!
Even if you do find it for ASMedia, when you reboot to Win 10, you will still have that annoying "Safely remove hardware" in taskbar/systray, and you will still probably have "Quick removal" in disk Policies.

That's the issue with ASMedia 3.x.x.x (and probably 2.x.x) drivers on any operating system.

(this is how wrong 3.x.x.x drivers look on Win10)


I think this thread explains the issue properly:
[Discussion] Firmware for Asmedia Sata 6G Controllers (12)

Please try it and tell me the results!

@Fernando:
I know, however I stumbled upon this issue on a PC with ASmedia SATA when I installed W10 on it, and couldn't figure out what to do.
As I also said, old 1.x.x drivers are probably a bad idea on W10, but 2.x and 3.x drivers don't offer the Policies tab to disable hot plug.

But if you do install ASmedia SATA 2.x or 3.x drivers, the "TreatAsInternalPort" registry trick for generic MS SATA driver on W10 actually hides drivers, now I don't know if that is because that driver is actually being used instead of ASmedia driver, or that registry works regardless if you have 2.x/3.x ASMedia drivers installed.

EDIT by Fernando: Fully quoted post replaced by directly addressing to the author (to save space)

If I check my disks, they all use a totally different .dll and .sys, be it on Intel controller or ASmedia.

How can I check that they are really managed by controller and driver they are attached to?

Blue = Intel, red = ASmedia - I know this because I connected them myself (this is on W7, ignore that for now)