Building a KBE: newly created KBE errors, will state \windows\system32\drivers\nvme.sys missing
Windows failed to start. A recent hardware or software change might be the cause...etc...
Info: Windows failed to load because a critical system driver is missing, or corrupt.
I have located this "nvme.sys" in the \\k2000\drivers folder, so it "should" be available to K2000. I have also tried to put it in the 3030 AIO's own \DRIVERS folder in case *that's* where it's coming from.
I'm not sure what I'm doing wrong. Help!
This *is* the first time I've attempted to build a new KBE so I could definitely believe I'm doing something incorrectly.
Thank you in advance!
BHC-Austin had the answer -- using the WinPE4 driver pack (and adding in my separate network drivers for 3030 AIO also) in \\k2000\drivers\kbe_windows-x86, recache, and rebuild KBE.
Answer Chosen by the Author
What the error is most likely indicating is that you are missing a file that nvme.sys depends on. This driver is specifically for the new NVM Express, a.k.a. M.2, SSDs that connect via a Mini PCI-E slot, versus SATA. Windows 7 SP1 (which PE3 is based on) does not have native support for these drives. There was a hotfix made available to add support (https://support.microsoft.com/en-us/kb/2990941)
You have a couple of options: 1. Manually inject the available hotfix into your KBE (tricky but I can provide some guidance on that if you need it), or 2. Upgrade to WinPE4 or 5. Personally, I would go with option 2. We use PE5 (Win 8.1-based) to deploy Windows 7 and 8.1 images w/o any problems.