Save changes to the image - taking forever

[PrinceKufre Akai]

Hi,

I'm trying to make the Windows 7 January 2026 .iso, add a lot of languages and unmount the image, but I've been stuck on 0% for best part of 1 day (save changes to the image) part. I can hear my PC Working hard at it, but the software doesn't seem to move.

I did a Windows 10 iso - it created correctly, but I got stuck on all the minimum requirement checks/TPMs etc so I had to abandon it entirely. Is there a way of pre-configuring that TPM Check/RAM Check etc etc to be disabled by default?

 

[garlin]

When you apply many update packages (like a Language Pack), or larger Monthly Updates (as in W10/11), processing time increases because NTLite has to merge tens of thousands of individual disk files. Disabling Defender or any real-time virus protection will make a dramatic difference in processing time.

Finally, when the WIM is built, the mounted temp folders need to be scanned for duplicate hard links and compression of large multi-edition images is an expensive operation. Typically a faster SSD will help NTLite more than a faster CPU.

If you're going to apply multiple LP's to a multi-edition ISO, expect to wait a long time. While it's a fun thing to do, it's impractical as most of the added languages will never get used in real life. Adding a handful of core languages should be enough for most users. The more LP's you add, the much slower the integration process takes. This is true even if you're not using NTLite to perform integration.

---

You can load your previously created W10 ISO, and re-edit it to add the HW requirement bypasses.

A good rule to follow is always start a new ISO if you're applying more updates. But if the only changes are tweaks (registry edits) or adding Post-Setup tasks, then it's fine to re-edit an existing ISO.