Features on Demand (FOD) in Windows 11 24H2

rawh-ul

New Member
Messages
2
Reaction score
1
Hi! This is my first post. I searched for my question, but didn't find what i am looking for.

I am using NTLite (sometimes with a business licence) since years - thanks for this great piece of software.

Before 24H2, NTLite showed Features on Demand place holders for all possible Features on Demand - FOD-cabs in ...\NTLite\Cache\Updates\[Version]

With Windows 11 24H2, NTLite doesn't show Features on Demand place holders any more - maybe I've done something wrong...
I've placed both folders from the FOD-ISO ("LanguagesAndOptionalFeatures" and "Windows Preinstallation Environment" folder) in ...\NTLite\Cache\Updates\11.24H2.x64.FOD
Will the place holders be back in future versions?
What is the best/easiest way to integrate features into the ISO?

Greetings!
 
Last edited:
I've run into this as well. Was a solution found?

I've followed the WMIC thread and garlin solution by adding the metadata folder (and contents) under 11.24H2.x64.FOD, as well as copying the contents of the whole "LanguagesAndOptionalFeatures" to 11.24H2.x64.FOD, but I guess I'm having a senior moment as its not playing. 10.22H2 and 11.22H2 worked fine, and I know from the same thread 11.24H2 changed things.

The only work-around I've found is to add the FOD .cab's under updates.
 
Add .Cab in Updates page - Add - Package file, is not good ?
 
Hi, that works fine, was just wondering if the more traditional method worked under "features"
 
I've run into this as well. Was a solution found?

I've followed the WMIC thread and garlin solution by adding the metadata folder (and contents) under 11.24H2.x64.FOD, as well as copying the contents of the whole "LanguagesAndOptionalFeatures" to 11.24H2.x64.FOD, but I guess I'm having a senior moment as its not playing. 10.22H2 and 11.22H2 worked fine, and I know from the same thread 11.24H2 changed things.

The only work-around I've found is to add the FOD .cab's under updates.
I'm a new member as well, so is this definitely the answer. To add FOD .cab files to 11.24H2.x64.FOD folder. Do you add the metadata folder as well, and what if you don't have either one of those folders just create them
 
It's now divided and called "Windows Feature Experience Pack".
Can be found in:
Components\ System Apps\ Windows Feature Experience Pack
I was needing to know how to put the features that come on the features on demand ISO into the image I am modifying
 
I understand - why i deleted my first post.
Many of the things of an earlier Windows install FOD package is already avaible in Windows 10/ 11 (22H2/ 23H2/ 24H2) in form of Apps, language install by Settings and .NET which get updated via WU.
.NetFx3 you can install from NTL Updates section.
Use NTL to update 24H2 Images instead of integrating own downloaded updates.
That'll spare time.
Before removal of Components after integrated updates, it's recommended to Apply and remove Components in a second load of NTL.
Then updated components get removed as well.
 
I understand - why i deleted my first post.
Many of the things of an earlier Windows install FOD package is already avaible in Windows 10/ 11 (22H2/ 23H2/ 24H2) in form of Apps, language install by Settings and .NET which get updated via WU.
.NetFx3 you can install from NTL Updates section.
Use NTL to update 24H2 Images instead of integrating own downloaded updates.
That'll spare time.
Before removal of Components after integrated updates, it's recommended to Apply and remove Components in a second load of NTL.
Then updated components get removed as well.
Okay I see thank you very much for your input it is appreciated considering I'm new at this
 
Okay I tried every way possible to make this work and the only other thing I can figure out is do I have to have a live internet connection to make these features on demand updates from the iso work, because I don't have internet that's why I have the features on demand ISO file
 
Add .Cab in Updates page - Add - Package file, is not good ?
in my case I get an error when the program gets to the Cumulative Updates. It finishes the image, but it gives me an error saying it can't integrate. What is the correct order of integration for Language Packs, Updates and Features?
 
The problem shouldn't be the order, NTLite normally integrates in the "correct order"
To see with nuhi

It's been a long time since I tested, but I've never had any errors when integrating different updates (CU, LP, etc...)
 
I just did some testing on my end:

Updates, Language Packs, Features on Demand - Crashes
Language Packs, Features on Demand, THEN Updates - Crashes
Updates, THEN Language Packs, Features on Demand - OK*

So long as you do one of the images at a time, using the Apply changes to another Image also results in a crash about Unable to unload Registry hives.

I'm not sure if its particular to Wireless Display, since its the only Feature I'm integrating. But that is how it happened.
 
To see with nuhi then

One of the advantages of NTLite is that you can "do everything" at once, rather than doing multiple image loading/unloading
The only times I do this is when I have several tests to do, and I integrate the updates into the image first
 
I just did some testing on my end:

Updates, Language Packs, Features on Demand - Crashes
Language Packs, Features on Demand, THEN Updates - Crashes
Updates, THEN Language Packs, Features on Demand - OK*

So long as you do one of the images at a time, using the Apply changes to another Image also results in a crash about Unable to unload Registry hives.

I'm not sure if its particular to Wireless Display, since its the only Feature I'm integrating. But that is how it happened.
Please list one of those crashing combinations, e.g. which lang pack, CU to see the issue myself.
Maybe simplest is to attach or send me the preset used (auto saved XML from that ISO), with explanation what is a crash, some kind of error I assume, not an actual crash?
If it actually crashes, then please attach %temp%\ntlite.log and ntlite.dmp if present at that moment.

Thank you.
 
Please list one of those crashing combinations, e.g. which lang pack, CU to see the issue myself.
Maybe simplest is to attach or send me the preset used (auto saved XML from that ISO), with explanation what is a crash, some kind of error I assume, not an actual crash?
If it actually crashes, then please attach %temp%\ntlite.log and ntlite.dmp if present at that moment.

Thank you.
I found the problem and the issue was that I was being too sleep deprived to think straight. Turns out you can't integrate extra language packs on Windows Home SINGLE LANGUAGE, who would've thought. :rolleyes: Sorry for being a dumbass.
 
I found the problem and the issue was that I was being too sleep deprived to think straight. Turns out you can't integrate extra language packs on Windows Home SINGLE LANGUAGE, who would've thought. :rolleyes: Sorry for being a dumbass.
I must admit I did not know that, checked it now and it's true, seems obvious after the fact.

Will see about adding a warning if detected, thanks for the feedback.
 
I've done a few rounds, so I can share my favorite, always working method now with 24H2:
- download FOD ISO and mount it
- copy contents from ISO to ...\NTLite\Cache\Updates\11.24H2.x64.FOD
- maybe delete all files/contents that you will never need/integrate ( takes long time to check all files, but you do not have to uncheck it later on second round and your base ISO is obviously smaller :) )
- start ntlite and mount a clean 24H2 iso (doesn't matter if it is the standard one, enterprise, or some image build from uupdump scripts)
- integrate 11.24H2.x64.FOD folder as updates > create iso with only your favorite/needed edition(s)
- do not make other changes!!
= you get your personal future use clean base image with FOD integrated that you can use for a second round to change what you want
- on second round, be careful to check Features on Demand page, to uncheck all unneeded FOD, cause all integrated as updates on first round, are now checked by default and will be installed/integrated in your final iso, if not unchecked.

I hate it that we have to create a base ISO with integrated FOD and then go for a second round to make our changes.
I liked the (old) process with placeholders for FOD. It was easy and did't took so much time to build a final iso with favorite FOD (plus time to learn this process).
 
Back
Top