1.7.2.6680 to v2.0.0.7618 - no drives detected, not integrating drivers

[skyracer]

Hello,

I just updated to 2.0.0.7618. NTLite is not integrating my drivers. I did a file comparison of the preset and here's what I found:

Under 1.7.2.6680:
<ImageTasks>
<Task>imageSaveRebuild</Task>
<Task>imageFormatWim</Task>
<Task>drivers_01_9_64</Task>
<Task>drivers_02_2_64</Task>
<Task>imageOptionsDontBackupPresetLog</Task>
<Task>imageOptionsCreateIso</Task>
</ImageTasks>

Under 2.0.0.7618
<ImageTasks>
<Task>imageSaveRebuild</Task>
<Task>imageFormatWim</Task>
<Task>imageOptionsDontBackupPresetLog</Task>
<Task>imageOptionsCreateIso</Task>
</ImageTasks>

Note, under 'Apply', on the right-most pane, it shows, "Integrate Drivers (11)", and they are listed in the preset, just not under <ImageTasks>. 1.7.2.6680 has no issues.

 

[skyracer]

Whoops, looks like integrate drivers was unchecked for the setup WIM. Is it normal for NTLite to change these values when updating to a newer version?

 

[nuhi]

<Task>drivers_01_9_64</Task>
<Task>drivers_02_2_64</Task>
drivers is a page, 01/02 is an image index, 9/2 is an image flags, 64 is bits. If any of it changed then it would not load it from the same preset, otherwise it should be loaded.

 

[skyracer]

I went from Windows 10 1806 to 2004, that would be why it changed?

 

[nuhi]

It shouldn't, boot.wim is still of the same naming as tool is concerned.
If you have the original preset, I am interested in loading it on my side.
Make sure the drivers are actually on the same location, sometimes I move the drivers and then loading an old preset will prompt missing files and skip those.

 

[skyracer]

There was an extra image: winre, that wasn't on my other media. I simply re-selected the images for the driver integration. Worked!