Trying to slipstream (via DISM) the Samsung NVMe drivers labelled as pure" 64bit Samsung NVMe Driver v3.3.0.2003 WHQL for Win7 x64 fails signature verification on Windows 7 x64 SP1. RAR file downloaded has MD5 checksum 18D6162EF38650F1FB6A4FA19FD132DC:

Installing 1 of 1 - D:\storage\Samsung NVMe\Drivers\secnvme.inf: Error - The driver package contains x64 boot-critical drivers, but the drivers are not properly signed.
Use the /forceunsigned option to install the drivers.

The exact command being used for integration (which worked just fine for official 3.2 drivers): dism /image:mount /add-driver:"Samsung NVMe\Drivers" /recurse

I really don't want to use /forceunsigned here to bypass this situation because it smells like there was a mistake made somewhere during driver packaging (either by Samsung or Fernando, not sure).

Manually checking Digital Signatures of both .sys files and .cat file show no anomalies that I can determine, but I did notice the .cat file is missing Samsung's SHA1 signature (the .sys have this, the .cat doesn't). Not sure if that's the problem or not. Either way, something is amiss here.

Any help is appreciated, but bare minimum, retaining a link to the old 3.2 drivers (RAR file) would be awesome. Thanks!

Edit: Poked around the driver extraction bits in the official Samsung .exe installer, got the cat/inf/sys files from there. They're the same. So this seems to be an error on the part of Samsung, but I don't know where the problem actually lies. I strongly suspect incorrect SHA1/SHA256 hashes in the .cat file. Someone should really report this to Samsung.

Zitat von koitsu im Beitrag #1759

---

Edit: Poked around the driver extraction bits in the official Samsung .exe installer, got the cat/inf/sys files from there. They're the same. So this seems to be an error on the part of Samsung, but I don't know where the problem actually lies. I strongly suspect incorrect SHA1/SHA256 hashes in the .cat file. Someone should really report this to Samsung.

---

@koitsu What about the two official NVMe-support updates for Windows 7?
Or you can read this driver during installation, right befor partitioning, from antoher usb drive, for example.
In my experience I do not slipstream any NVMe drivers into the installer because it seems, at least to me, more reliable to work with just the NVMe updates and install any manufacturer's driver inside the fnishes installation.
I use the force option on my ISOs all the time.

@PatrickK The "two official NVMe support updates for Windows 7" have no bearing on this problem. The problem pertains to to an incorrect certificate chain in Samsung's 3.3 NVMe drivers. The 3.2 drivers have a proper certificate chain.

Samsung responded in Email today, stating they have forwarded the issue on to their software engineering team for review and will reply further soon.

Now, unrelated to the above matter:

As for the two non-publicly-distributed KBs you're talking about -- KB2990941 and KB3087873 (hotfix/bugfix for KB2990941) -- these are Microsoft's NVMe drivers. You can't slipstream those two KBs and Samsung's drivers at the same time -- DISM will fail. You have to pick either Microsoft's or Samsung's when using DISM (nobody online seems to state this anywhere; I found hints about it deep within some weird Intel RST PDF somewhere online). I use Samsung's because while the performance is slightly worse (by a miniscule amount), my NVMe drive (970 EVO 1TB) runs several degrees cooler (temperature-wise) using Samsung's drivers. I live in northern California in an apartment that lacks air conditioning: during the summer, indoor room temperatures can exceed 97F/36C.

The reason I slipstream these drivers is because I have two disks in my workstation: a SATA SSD for C: (OS drive) and an NVMe drive for D: (extra storage). I keep all my drivers, applications, slipstreaming scripts, etc. on my NVMe drive (I do not want to involve a USB drive). Thus, after an OS reinstall, the OS does not see the NVMe drive at all due to lack of drivers, leading to a chicken-and-egg problem. Slipstreaming the drivers relieves this problem (I can see the NVMe drive even during Windows Setup).

Updating the Samsung drivers when using slipstreamed Samsung driver integration is very easy too: Device Manager, Disk Drives, find the NVMe disk, right-click on it and pick Update Driver Software, then pick the folder containing the newer driver (INF/CAT/SYS files). Reboot and you're done.

I hope this answers your question.

hi to all i have this controller https://www.raidsonic.de/en/index.php?we_objectID=5456 with samsung 500 evo oplus
my pc is dell optiplex 3070 i5-9500 with windows 10
witch nvme drivers is best ?
thanks

Zitat von Fernando im Beitrag #1528

---

Update of the start post
Changelog:

• OCZ NVMe drivers:
  • Customized:
    • "pure" 32/64bit OCZ NVMe drivers v1.2.126.843 mod+signed by me at 07/28/2019 (now with support of "XG6" NVMe Controllers with the DeviceID DEV_011A)

---

I can confirm that FINALLY the ASMedia 3.3.3.0 solved my locking problem (PC freeze, or disks controller freeze) when launching the HWiNFO64 with ide/sata drive scan enabled, and especially launching AIDA64 after it!
Was broken in WIN10 for years... :)