[BUG] Editing Winre.wim causes NTLite to save/unload install.wim

[intelfx]

When opening Winre.wim (nested inside of an install.wim) in a session and instructing NTLite to "Save the image" on the Apply page, both the Winre.wim being edited and containing install.wim are saved and unloaded.

Reproduction steps:

1. Load an image (e.g., "Windows 10 Pro") from install.wim
2. Click "New session" (such that the image remains "Mounted")
3. Load the "Microsoft Windows Recovery Environment" image from the nested Winre.wim
4. Make some changes
5. Go to the Apply page, select "Save the image" (or "Save the image and trim editions") as the "Saving mode"
6. Click "Process"
7. Observe that both the Winre.wim and the containing install.wim are being saved and unloaded.

Arguably, when editing a specific WIM, only that WIM should be affected (i.e., when editing a WinRE image, I'm not expecting NTLite to unload the OS image because I will likely edit that next).

A demo screenshot is attached (compare/contrast the name of the image being edited and the path to the image being saved in the status bar).

 

[nuhi]

Thank you, confirmed, will fix and reply here when done.

 

[nuhi]

Done, let me know if newer versions have any issues with this.

Thanks.