The Catch 22 problem

kosmo

Member
Messages
82
Reaction score
27
Started building my "windows_10_iot_enterprise_ltsc_2021_x64" on my Win 7 machine today . (cause that's all I have) I attempted to install 3 updates (that I had manually downloaded) 2 of the 3 failed with "0x80070057 - prarameter is incorrect" errors. Searching the forum I found this thread which suggests that integrating updates (or adding / removing features) on a W10 ISO while using a W7 machine will often result in errors. In the last post in that thread garlin suggests, if I understand correctly, to add updates and add/subtract features to your ISO inside a VM using NTL lite.

So are there any known issues with the build process - besides updates & Add / subtract features - where my W7 host machine is likely to cause me a problem?

( Catch 22 = apparently to upgrade from W7 to W10, using NTL, you need to upgrade to W10 first in order to be able to build your NTL W10 ISO )
 
Last edited:
Install Stock Windows 10 iOT Enterprise ltsc 2021 x64 first. Then build your modded Image.
 
The root of this issue is because NTLite uses Microsoft's built-in DISM command, and it isn't fully compatible with every scenario forward and backward. Like the previous reply stated, users can install the same operating system on the host machine that they are targeting, in order to avoid all problems related to mismatched versions. I think where people tend to get confused on this topic, is due to the other uncertainties surrounding both Microsoft and NTLite licenses, so I'll clarify the bits I see people get stuck on, if nothing more than to help answer some related questions for lurkers.

WINDOWS LICENSE
A Windows license is tied to a unique ID on each motherboard, meaning a person can replace every piece of hardware in their computer and it won't require a new license from Microsoft, as long as the motherboard isn't one of those replacements. Some Windows have special allowances, and one of those is that Windows 10 and 11 licenses are interchangeable, so if a user doesn't like Windows 11 that came preinstalled with a computer, then they can do a clean install of Windows 10 using the same Windows license, as long as the edition matches (Home, Pro, etcetera).

WINDOWS TRIALWARE
Windows defaults into trial mode and doesn't have to be activated for most features to work, meaning if a user just needs a temporary operating system in order to finish a project, such as making a custom image with NTLite, then it's legal, free, and easy to download any of the Microsoft ISO images they make available, and they can be installed as needed for such work.

NTLITE LICENSE
An NTLite license is tied to the computers it is installed on and that had internet access when it attempted to perform an online activation. Once that computer is registered, it uses up one of the limited activations from the license purchase, and then that computer now has one full year of all NTLite features to build as many Windows images as the user wants, before the tool switches back into limited mode after the license expires. Edited Windows images are not tied to the NTLite tool in any way.

NTLITE SUPPORT
NTLite doesn't officially support certain versions of Windows, such as IoT, so keep that in mind when choosing an operating system. In general, there's a ton of hands-on experience that's learned while working through an NTLite image, and the following guides discuss many of those things upfront, which can save users a lot of time and headache in the long run if they read through these before setting out to make their own custom image.

- Guide: NTLite for Beginners (link1)
- Guide: Custom ISO Downloads (link2)
- Guide: Quality Control (link3)
- Guide: Choosing a Preset (link4)
 
Last edited:
Servicing Windows images to install Updates or Feature packages requires proper support from the Servicing Stack platform, which underpins DISM operations. Component removals and other ISO-level tasks don’t involve the Servicing Stack, and are platform independent.

Every Windows packages requires a minimum revision of the SSU in order to be integrated. Since there are specific kernel drivers & DLL’s for the SSU, it can’t be done on older OS releases where it's never been backported.

Bottom line: regardless of which imaging tools you use, W10 updates require the use of W10 or later host.
 
Install Stock Windows 10 iOT Enterprise ltsc 2021 x64 first. Then build your modded Image.

Thank you for suggesting what should have been obvious to me! Except for playing around in a VM for an hour yesterday I have never used W10 before in my entire life. So installing the stock ISO and using it for a week or two before building the modded ISO will put me in a much better position to know what I need to do in the build process.
 
i build a w10 1809 image on an 1809 host, 21h2 on 21h2 etc. i leave 100gb space on my main c drive for these types of occasions. always test run a newer stock os(updated of course) to see whats what, what needs to be done, any annoyances that need to be delt with.

edit
This way you don't use up a license activation.
im on a Business license so i cant comment on activations for Home licenses.
 
Last edited:
Free edition of NTLite will still integrate Updates, but you have to download the files yourself (or transfer them over). Install W10, install NTLite in free mode, integrate updates, and move your updated image back to W7 for finalization. This way you don't use up a license activation.
 
The root of this issue is because NTLite uses Microsoft's built-in DISM command, and it isn't fully compatible with every scenario forward and backward.

Thank you for your clarifications.

I've read all of your guides. If you wrote a translation of the Norwegian Dictionary i'd read that too. IMHO, you have a unique talent for someone with your geek experience level in that you still have the ability and willingness to explain the issues at hand in plain English - without "dumbing the subject down". The forum is a much more useful resource because of your presence.
 
Last edited:
Back
Top