Update Win7x86 for USB3/nvme? Redux

Thanks, I didn't know the structure of boot.wim/install.wim. Does this coding also exist in 7UPv64I? If it does, then I must have used it wrongly.

This just in --
Using the very simple .cmd's from the NVME SOP_20170419 folder obtained from Lenovo(?), I built two separate usb3 sticks, x86 and x64, and successfully booted both to a Crucial P5P NVME. The result was a working dual boot Windows 7.
What is interesting is that the Device Manager, in both cases, tells me the driver for the P5P is a Microsoft 6.1.7600.16385 dated 6/21/2006.
If I try to update driver with the Micron (Crucial mfg) driver, I get the response that the current driver is the latest.
Has anyone actually installed a manufacturers driver over the MS driver?
What am I missing?

Had the same exact issue. I have a P3.

- - - Updated - - -

But get this! I actually wrote a post in post #5 because I have the experience....

The bottom line--
I decided to install a triple boot system:
1. WIN7x86 on the Crucial P5P M.2 NVME,
2. WIN8.1x86 also on the P5P,
3. WIN7x86 on the Gloway WAR PRO T300 2.5" SSD.
The P5P WIN7 was already installed, as I have been using it all along after spending so much time getting it onto an NVME drive with, finally, only the KB2990941 hotfix mixed into the boot USB3 drive.
The WIN8.1x86 went on the NVME drive easily, as did the Win7x86 on the 2.5" SSD drive.

I ran a benchmark on each.

NO. OPERATING SYSTEM RESULT

1 WIN7x86 NVME 2091.8
2 WIN8.1x86 NVME 2043.1
3 WIN7x86 SSD 2063.9

They all used the same driver, as per the Device Manager: Microsoft 6.1.760x.xxxxx. Trying to get the Device Manager to "Update Device" was useless. In my opinion, without a specific NVME driver, the NVME is just another SSD.

i AM DONE.
JOE.