/bundles/itninjaweb/img/Breadcrumb_cap_w.png
I am trying to build a new 32bit KBE for Optiplex 3030 AIO (BIOS A06). 

I followed these instructions to determine that our preexisting 32bit KBE was missing a network driver for the 3030 AIO. I was able to fully mount the x86 KBE after mounting the driver locally, and proceeded to image, so I know it's the correct driver. 

I downloaded the WinPE3 driver pack from here and unpacked the 32bit KBE drivers in \\k2000\drivers\kbe_windows_x86.

I also downloaded the (still missing) network driver specifically for Optiplex 3030 AIO 32bit in \\k2000\drivers\kbe_windows_x86 and recached all drivers on K2000.

Then, on a test imaged Optiplex 3030 AIO (imaged once by manually loading the missing network driver), I followed the "building a new KBE" instructions from here -- installed the WAIK on the 3030, downloaded Media Manager and installed it on the 3030, and successfully created (several, at this point...) new KBEs.

The trouble comes in when I try to use the newly created KBE. The KBE never finishes loading and states

Windows failed to start. A recent hardware or software change might be the cause...etc...
File: \windows\system32\DRIVERS\nvme.sys
Status: 0xc000035a
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!

Answer Summary:
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.
0 Comments   [ + ] Show comments

Comments


Answer Chosen by the Author

1

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.

Answered 03/08/2016 by: BHC-Austin
Fourth Degree Black Belt

  • Really!! Wow, I didn't realize I could use WinPE4 -- I somehow thought the drivers within were ONLY for Windows 8.

    Would you recommend that I add the WinPE4 drivers to what's already there, or replace?
    • Yes, I was apprehensive at first, too. Each version of PE typically supports deployment of previous versions of Windows. You could, technically, upgrade to PE10 and still be able to deploy Windows 7 images. I haven't been that brave yet... lol

      As for the drivers, the instructions recommend replacing the contents of the kbe_windows_* folders with the appropriate driver pack.
      • Awesome BHC-Austin! I just followed your instructions and am looking at the main KACE imaging menu on my troublesome 3030 AIO right now! Fantastic!!