Manually adding DISM packages to a mounted image

PhsMu

Active Member
Basically what it says on the tin. Much like the right click options on the image list to remove/convert an image on the iso, but on the updates list, in case we want to manually add features Microsoft removed 'for our own good' (Read to keep us from using version X for Y purposes, when they're just plain better).

As NTLite is now, I can basically do the same by pointing it to a folder to use as tempmount and do it by script, but I have to mount the image manually, OR open NTLite, mouint image, close it, manually integrate pesky cab files, reopen tool, do NTLite things to image then save it.

I feel like an option to "Apply esd/cab/msu to image now" in updates opening an 'add file menu' and then running

dism /image:[tempfolder]NLTmpMnt01 /Add-Package /PackagePath:[path to cab/esd file]

shouldn't be too much of a hastle to implement and would allow us to troubleshoot issues with the order of integration without having to fully run the tool multiple times if updates need to be integrated in a particular order to unlock certain features and capabilities. *cough*WirelessDisplay on LTSC*cough*
 

garlin

Moderator
Staff member
Requiring multiple, manual integration passes isn't a new problem. abbodi's install order for W7 RDP comes to mind.
I would agree NTLite needs a "dry run" mode, where it previews the order of execution and writes it to file.
 

nuhi

NTLite developer
Staff member
PhsMu,
this is how NTLite is to be used for such a task of inserting an update fast in a pre-session:
  • load edition (it will mount and open pages)
  • make sure nothing else is done, under the Source page - Presets tab - click New to reset.
    Saying this because an autoloaded preset from earlier session might confuse.
  • go to the Updates page
    Add your package
  • go to the Apply page
    change Save mode to Stop before saving image
  • Process
Then the mount folder will contain the package and nothing else was done.
You can reload it to continue in another session, it's already mounted etc.

Also can automate all that via ntlite.exe switches inside your scripts, see ntlite.exe /?, and a preset made from steps above.

Is that it or I misunderstood the point?

garlin, this isn't about the sorting of update integration, if you see any issues with the order, let me know, it's easy to adapt, user should not bother about it.
 

PhsMu

Active Member
this is how NTLite is to be used for such a task of inserting an update fast in a pre-session:
  • load edition (it will mount and open pages)
  • make sure nothing else is done, under the Source page - Presets tab - click New to reset.
    Saying this because an autoloaded preset from earlier session might confuse.
  • go to the Updates page
    Add your package
  • go to the Apply page
    change Save mode to Stop before saving image
  • Process
Then the mount folder will contain the package and nothing else was done.
You can reload it to continue in another session, it's already mounted etc.
I didn't know you could stop before saving the image, that helps!

A way to 'force integrate' packages though would still be awesome.

this isn't about the sorting of update integration, if you see any issues with the order, let me know, it's easy to adapt, user should not bother about it.
it kind of is, depending on how you look, not for the official updates, mind you, that I 100% agree with you should be automatic, but for bits and pieces of features microsoft have been taking down over time.
 
Top