Missing Driver (s) ?

kosmo

New Member
NTLite noob here. Built a W7-64 pro install for my Lenovo X-1 laptop (which has only 3.0 USB ports) using another W7-64 machine. The drivers I used were backed up from the current W7 64 install on the X-1

I added ALL Lenovo drivers and got this error message during build: "Driver Integration Warning:" Error: 0x00000002 "system can't find files" oem23.inf & oem39.inf (which ARE in the respective folders & without any other conflicting inf's) These refer to Bluetooth Server & SM BIOS - neither of which are probably related to my current problem

I "burnt" the 3.0 gb ISO to a USB w/ Rufus and it boots just fine. But right after "starting setup" it complains that it can't find a necessary device driver. Both of these folders were integrated w/ all the other drivers:
Intel(R) 6th Generation Core Processor Family Platform I O SATA AHCI Controller
Intel(R) USB 3.0 eXtensible Host Controller
and the folders have the files I would expect to find in them.

Thinking I might have overlooked something I started w/ a fresh source and did it all over again (using the previous presets) but the 2nd image stops that exactly the same point w/ the same error.

Now what?
 

Attachments

  • Auto-saved session {65CAF905-5E50-4A42-900B-5E14084871E9}.xml
    78.1 KB
  • autounattend.xml
    3.2 KB
  • NTLite.log
    226.1 KB
You need to add the usb3 drivers to the boot.wim - microsoft windows setup aswell as the install.wim. Look at the Apply page to integrate the drivers into both wims though personally i would process the boot.wim seperately because you are only adding the usb3 drivers.
 
Last edited:
@kosmo, in your log I don't see boot.wim being updated, that is the secondary image within the ISO that is actually the one being booted during first stages of Windows setup.
Here is a great guide and forum related to driver integration using NTLite. After absorbing the process in general, there is also a section for USB 3 drivers in particular, here, if it doesn't work from first try.

Yes, you can compound drivers and integrate to boot.wim alone in the second go, no need to re-integrate updates.

Let me know if you see any issues on the processing part. For example when you got that error 2 about missing files, it means your OEM*.inf driver is calling some file that is not there.
Make sure your drivers are not just manually copied INF files, they need to have accompanying driver files/folders as well.
Best is to download fresh ones from the manufacturer's site (or the mentioned forum) and extract to some folder, then integrate that.

To see more details about the missing file the next time, please compress and attach:
[mountdir]\Windows\INF\setupapi.dev.log

Mount dir can be reached by right-clicking the loaded image on the Source page and select Explore Mount Directory.
 
Last edited:
@ nuhi Thanks for your explanations. ( I saved the setupapi.dev.log and will, after I get a successful install, post about that if still necessary)

While I was waiting for inspiration I read a bunch of forum posts and one of kasual's convinced me to do over my updates so I built another ISO - checking off the 2 wim's this time. Now my 3rd attempted install boots to to the partition page where I discovered that I have no cursor. I went back, reloaded the image and verified that I hadn't unchecked Mouse Drivers on the Components page and I did add my Synaptics drivers and integration didn't complain about them. Besides, wouldn't these be generic M$ drivers at this stage of Setup?

What did I do wrong this time?
 

Attachments

  • Auto-saved session {65CAF905-5E50-4A42-900B-5E14084871E9}.xml
    61.5 KB
  • autounattend.xml
    3.2 KB
  • NTLite.log
    300.1 KB
@ Kasual Thanks for replying but you've just spoken Greek to me. (w/ my apologies to any Greek members!) I'm very happy to oblige but I need "See Spot Run" directions i'm afraid...
 
In NTLite\Presets from where you have uploaded the "Auto-saved session {####}.xml" are saved all presets after starting a process.

Open your latest xml files with a text editor and at the line 11 look for something like:
Version mode="offline"Windows (TM) Code Name "Longhorn" Preinstallation Environment SP1 64-bit - WindowsPE 6.1.7601.0
And upload the file containing that string.
 
@ Kasual Thanks for your efforts but i'm not finding what you're describing. You said:
Upload the preset generated by boot.wim editing please.
but I didn't attempt to modify my previous build with the missing USB drivers - I built a complete new image from scratch (to integrate your updates).

So when I open NTL, reload the modified source folder there's only 1 preset showing - the one I uploaded above that covers the whole build process. I tried unloading the main source folder and loading each of the 2 wim's individually but they all refer to the same preset - the one I uploaded earlier. And that doesn't have the string you're looking for.

So am I still misunderstanding your instructions or are you misunderstanding what I did?
 
Last edited:
@kosmo, do you have mouse cursor on full Windows ISO/USB?
If the full ISO works, I would be surprised because I don't see boot.wim removals on your preset.

Then it's the USB controller driver, most probably you need the exact USB3 driver to be integrated into boot.wim (first stage of setup, includes the partition selection) and install.wim.
As to which driver you need, that depends on the motherboard, integrate them all from the forum about USB3 that I linked previously.
Btw when integrating to boot.wim, make sure it's the Setup edition, not the Recovery.
Also you would get better help there in picking your driver.

I also still notice error 2's in your log, please re-read my reply. Don't ignore those errors as you don't have the drivers actually integrated.
Get the full drivers from the manufacturer's site or that forum and integrate those extracted.

Let me know if it gets stuck anywhere, I'll do my best to reply faster this time.

Thanks for your patience.
 
@ nuhi Thanks for your reply.

do you have mouse cursor on full Windows ISO/USB?
If the full ISO works, I would be surprised because I don't see boot.wim removals on your preset.

I'm sorry but I don't understand your question. Any part of it actually.( you should probably assume that I know nothing at all which isn't entirely true but more accurate than assuming that I know as much as most of your forum visitors)

Let me recap: I'm trying to do a a fresh W7-64 Pro install on my Thinkpad X-1 laptop (which has only USB 3 ports). I build a new ISO from scratch (because the last one was missing USB 3 driver integration into setup) This time on the APPLY page > Select Image Paths > Image Process Queue > Integrate Drivers I made sure to check both bootwim 1 & 2. Other than load all the drivers on the Driver page that's all i've done to get the needed drivers into the pre-Windows environment. Unlike my 2nd attempt this ISO boots all the way to the Partition screen in setup leading me to assume that it found the USB drivers and now has a different problem.

When I say I have no cursor I mean that touching the touchpad or the Trackpoint knob has no visible effect. The Synaptics drivers were integrated into the image but wouldn't Setup be using native M$ drivers at this point?

Then it's the USB controller driver, most probably you need the exact USB3 driver to be integrated into boot.wim (first stage of setup, includes the partition selection) and install.wim.

I have the correct USB 3 Lenovo driver integrated and setup now boots past the stage where it complained about a (unspecified) missing driver on my 1st & 2nd install attempts. The problem now is that I have no "mouse action" - I can't select anything on the screen.

I also still notice error 2's in your log, please re-read my reply. Don't ignore those errors as you don't have the drivers actually integrated. Get the full drivers from the manufacturer's site or that forum and integrate those extracted.

When I bought this laptop I downloaded any newer drivers from Lenovo and installed them. Then I backed up all drivers using 4 different driver backup programs into 4 different folders. Then I compared all folders for each item to make sure that I had all the required files. Took me 2 days. So my driver files may have too many files but i'm going to be really surprised if they're missing any needed files.

In both of the errors that NTL is calling out I read the inf's and the all the files called out are there in the folder. I'd like to see, once I get a successful install, whether these drivers actually install or not. If not then i'll have to figure out why but if they do install then i'll let you know that it may have been a "false negative".
 
I hear you, but also there were errors during integration, so why not try the full set of drivers. From the log you're trying to integrate the "oem" infs, which are already deployed drivers.
I believe it's the extra driver necessity or not possible with that driver, to get the cursor during the boot phase in Win7.

So I still suggest to get the full set of drivers and integrate that instead, procedure will pick up only the needed files even if your source location is bloated.
Also ask/search on that forum I linked previously for USB3, maybe they encountered that situation before.

This tool is about the integration, not the driver support per say.
If you see that a driver wasn't integrated properly, that's another story, but since it's using DISM - not likely.
 
Back
Top