W7 x64 EOL, Long processing time NTLite 2.3.4.8643

[Clanger]

NTLite_2.3.4.8643_x64 - w7 pro x64 eol captured image, not dism cleaned before capture. MT_ w7 preset, processing time 75m 10s.

Report on winsxs leftovers to follow, same tool build number.

 

[garlin]

Help me with my maths.

24/03/2022 10:51:28 Load tool settings

24/03/2022 12:09:50 #

 

[Clanger]

Huh? . That is the time reported in the progress bar bottom left.

 

[garlin]

I can't see your desktop, looking at NTLite.log

 

[Clanger]

Its the log for that build in the image folder. I didnt clock watch, its what the tool reported. I can redo it that test and post.

 

[Clanger]

2nd run, 76m 18s. Its them damn printer drivers, tool always bogged down with them .

 

[garlin]

Maybe worth a shot. Removing the targeted drivers using a DISM loop.
Then use NTLite.

Dism /Mount-Image /ImageFile:C:\w7dvd\Sources\install.wim /Index:1 /MountDir:C:\Offline
for /F "delims=| tokens=2" %%a in ('findstr "Removing" NTLite.log ^| findstr /rc:"inf$"') do echo %%a >> INF_list.txt
for /F "delims= " %%a in ('sort INF_list.txt') do Dism /Image:C:\Offline /Remove-Driver /Driver:%%a
Dism /Unmount-Image /MountDir:C:\Offline /Commit

EDIT - Corrected -> /Index:1

 

[Clanger]

Right, i get ya, some of that is beyond my pay grade. Wouldnt i need a makedir for \Offline? before running dism?
ie - MAKEDIR "C:\Offline"

where would i put INF_list.txt?

 

[Clanger]

dism just zips through it throwing errors .

 

[Clanger]

I am going to write today off.

 

[Clanger]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\PowerRun-1.6>Dism /Mount-Image /ImageFile:C:\w7dvd\Sources\install.wim /Image
Index:1 /MountDir:C:\Offline

Deployment Image Servicing and Management tool
Version: 6.1.7601.24499

Error: 87

The mount-image option is unknown.
For more information, refer to the help by running DISM.exe /?.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\PowerRun-1.6>

 

[garlin]

Sorry, thought you were running DISM on a W10 or 11 host. W7 DISM is too primitive.

 

[Clanger]

, yeah, w7 host. Thanks for your help anyway .
Ive used makedir and dism before on setupcomplete.cmds, i'll have to dig them out and check the commands.

 

[Clanger]

Can i use dism from w10(and its commands) on w7?

 

[garlin]

Basic commands do work (but integration is unsupported).
W10 ADK installed on my W7 system:

> cd "\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools"
> DandISetEnv.bat

> mkdir G:\src\MOUNT
> Dism /mount-image /imageFile:"F:\Win7_Ult_SP1_English_x64\sources\install.wim" /index:1 /mountdir:G:\src\MOUNT

> Dism /image:G:\src\MOUNT /get-drivers
Published Name : oem0.inf
Original File Name : prnms001.inf
Inbox : No
Class Name : Printer
Provider Name : Microsoft
Date : 6/21/2006
Version : 6.1.7600.16385

Published Name : oem1.inf
Original File Name : prnms001.inf
Inbox : No
Class Name : Printer
Provider Name : Microsoft
Date : 6/21/2006
Version : 6.1.7601.17514

> Dism /image:G:\src\MOUNT /remove-driver /driver:oem1.inf
Found 1 driver package(s) to remove.
Removing 1 of 1 - oem1.inf: The driver package was successfully removed.

> Dism /unmount-image /mountdir:G:\src\mount /commit
The operation completed successfully.

 

[Clanger]

I got 1809 ADK.

 

[garlin]

W10 DISM supports /Remove-Driver.

 

[Clanger]

I'll give it a go but i gotta spend a couple of days where i do stuff that actually gets results, yesterday really busted my hump.
I hate wasted days where nothing goes right, grrrrr