Is your feature request related to a problem?
When I customize a WIM in DISMTools, the project does not save a reusable list of the changes after the image is unmounted.
If I use a clean WIM or a newer Windows image, I have to manually repeat the same changes.
A similar idea was also mentioned in Discussion #139.
Describe the solution you'd like
I would like a reusable preset system similar to the preset system in NTLite.
The preset could save supported changes such as:
- AppX packages selected for removal
- Packages added or removed
- Features and capabilities enabled or disabled
- Drivers added
- Other settings changed through DISMTools
The preset could then be loaded into another project or applied to a fresh WIM.
Before applying it, DISMTools should show the saved changes so the user can review or edit them. It should also show if an item is unavailable or incompatible with the new image.
Describe alternatives you've considered
The alternatives are keeping a manual checklist, using separate scripts, copying an already modified WIM, or repeating every change manually.
Additional context
The idea is similar to NTLite presets, where image-customization selections can be saved and reused on another Windows image.
The preset would not need to copy the mounted image or the whole project folder. It could be a small configuration file containing the saved operations.
Is your feature request related to a problem?
When I customize a WIM in DISMTools, the project does not save a reusable list of the changes after the image is unmounted.
If I use a clean WIM or a newer Windows image, I have to manually repeat the same changes.
A similar idea was also mentioned in Discussion #139.
Describe the solution you'd like
I would like a reusable preset system similar to the preset system in NTLite.
The preset could save supported changes such as:
The preset could then be loaded into another project or applied to a fresh WIM.
Before applying it, DISMTools should show the saved changes so the user can review or edit them. It should also show if an item is unavailable or incompatible with the new image.
Describe alternatives you've considered
The alternatives are keeping a manual checklist, using separate scripts, copying an already modified WIM, or repeating every change manually.
Additional context
The idea is similar to NTLite presets, where image-customization selections can be saved and reused on another Windows image.
The preset would not need to copy the mounted image or the whole project folder. It could be a small configuration file containing the saved operations.