How exactly nVME drivers can be appropriately integrated into the Windows 7's boot.wim? Because there is a problem when KB2864202, KB2990941-v3, and KB3087873-v2 are integrated into both indexes of the boot.wim image, Index #1 Pe Index #2 Setup in the setup screen there no standard HHD, SSD or even virtual HDD in VMWare that can be found. Simply as integration of the above updates that contain nvme drivers breaks the old sata drivers... that is very strange. What is more strange is that, even the nvme drivers are chosen to be integrated via simplix's UpdatePack7R2 (probably in both the install.wim and the boot.wim) the result is the same.
It's enough we know this Windows 7 NVMe driver works fine on real HW. On VM simply emulate something else.
Are you sure it's not the setup.exe mismatch issue? https://forums.mydigitallife.net/th...win7-distribution.45005/page-233#post-1802763
Windows 7 NVMe driver doesn't work in most on VMs, thats that issue. W8 backported works. I just don't understand why to emulate NVMe on VM when my system is already installed on NVMe? What should be real usecase?
That depends, newer drivers 6.3 have newer storport and most of structures were changed. Even it could be mirror change, I would go with ported one (XP2ESD use same ported W81 NVMe driver in WinPE 7) Btw, for Windows 7 we have NVMe hotfix Windows 8.1 handle NVMe natively Is there any Windows 8.0 NVMe hotfix?
You are right. However it looks that on VMs it doesn't work even with setup.exe updated. Doubtful. But vendor specific drivers still can be used.
Yes, there are many solution. I'm just looking for MS NVMe compiled with Windows 8.0 DDK as there is big chance to run it with extender. 8.1 storport based drivers we changed a lot.
For VMware copying only the "sources\setup.exe" from index #2 of boot.wim to "DVD\sources\" fix the problem.
Another interesting NVME driver for W7 is the Generic Phison driver. It is built using the Win7 DDK and contains a valid SHA1 and 256 certificate (no need to import/install any kind of certificate) and can be used on W7 builds even without any of the SHA2 related patches. Readme : Spoiler All these Phison NVMe drivers are dated 02/23/2018 and WHQL certified. Since their *INF file doesn’t contain any specific VendorID or DeviceID, they may support the NVMe Controllers of all currently available NVMe SSDs. Due to the fact, that theses drivers are WHQL certified by Microsoft, they can be integrated into the OS Image or being loaded at the beginning of the OS installation. Thanks to our Forum member Black6spdZ for the hint to these extremely hidden Phison NVMe drivers. Tip: To avoid any problems while (re-)starting or shutting-down the computer, it is a good idea to disable the "Fast Boot" and "Secure Boot" options within the BIOS. Furthermore I recommend to set a “Restore Point” before updating to these drivers. You can find it on the WinRaid forum / NVME Driver Megathread but I also uploaded it here for convenience :