But instead Windows loaded the driver normally and applied it to the Intel NVMe controller automatically! WTF?! I know it did this, because in my list of drives available to install Windows to, my NVMe drive plugged into the Intel system disappeared, just like what was happening on the AMD system. Now, anyone that has done this before knows that normally if you try to load a driver this way that isn't compatible with any hardware in your system, Windows installer won't let you.
I selected the option to load more drivers and loaded the AMD NVMe drivers, and to my surprise it took them.
So I fired up my Windows 10 install media on my Intel system. I force removed the device and it's drivers through Device Manager, rebooted Windows and BAM I can see the VNMe Drive now!īut this got me wondering. I just happened to be running through Device Manager and saw something under Storage Controllers called AMD RAID something something(I don't remember exactly what it said, I was just happy to find it and quicly right clicked on it and uninstalled it). As far as Windows was concerned, everhthing was perfectly normal. The odd part is there wasn't any error in device manager. But the controller wasn't functional with that driver. So, you guessed it, the AMD RAID driver was still loading for the NVMe controller. Well guess what, AMD in their infinite wisdom, deciced to not change the device ID of the NVMe controller when you change it from RAID to nromal NVMe mode and vise versa. That's why when I changed the SATA controller form RAID to AHCI, the standard AHCI driver just loaded automatically the next time I booted Windows. ALSO, normally when you change a controller from RAID back to AHCI/NVMe, the device ID changes so the OS identifies it as a different device entirely. So, AMD is stupid(are we surprised?) Even though I uninstalled all the drivers(I thought), the NVMe Controller driver is separate and doesn't get uninstalled when you uninstall all the other drivers. If you install this package, your device will be properly recognized by compatible systems, and might even benefit from new features or various bug fixes.ĭell Express Flash NVMe PM1725 1.6TB PCIe SSD Adapter by Samsungĭell Express Flash NVMe PM1725 1.6TB PCIe SSD Controllerĭell Express Flash NVMe PM1725 12.8TB PCIe SSD Adapter by Samsungĭell Express Flash NVMe PM1725 3.2TB PCIe SSD Adapter by Samsungĭell Express Flash NVMe PM1725 3.2TB PCIe SSD Controllerĭell Express Flash NVMe PM1725 6.4TB PCIe SSD Adapter by Samsungĭell Express Flash NVMe PM1725 800GB PCIe SSD Controllerĭell Express Flash NVMe SM1713 3.8TB PCIe SSD Adapter by Samsungĭell Express Flash NVMe SM1713 3.8TB PCIe SSD Controllerĭell Express Flash NVMe SM1715 1.6TB PCIe SSD Adapter by Samsungĭell Express Flash NVMe SM1715 1.6TB PCIe SSD Controllerĭell Express Flash NVMe SM1715 3.2TB PCIe SSD Adapter by Samsungĭell Express Flash NVMe SM1715 800GB PCIe SSD Controllerĭell Express Flash NVMe SM1715a 3.2TB PCIe SSD Controllerĭell Express Flash NVMe XS1715 1.So this finally got me in the right direction and I figured it out! Moreover, constantly scan driver updates by Driver Genius or enable the Scheduled Scan function in Options- Schedule to make sure that will not miss a new release. Driver Genius will install the driver automatically, smoothly and silently.
If you consider updating this driver package by Driver Genius, all you need to do is clicking the Update button beside this driver update. The driver package provides the installation files for Samsung NVMe Controller Driver 1.4.8.3 for Server 2008 R2 system. Samsung NVMe Controller Driver 1.4.8.3 for Server 2008 R2