Guides / Windows Features on Demand (FOD)

Windows Features on Demand (FOD)

What Features on Demand are, where the Windows FOD ISO comes from, and how to integrate optional features and language packs offline or on a running system with NTLite.

Features on Demand (FOD) are the optional Windows parts Microsoft keeps out of the installation ISO: display language packs, N-edition media support, management tools, and the legacy components that used to ship in the box. Windows fetches them from Windows Update on a connected machine, which is exactly what fails on an offline image, a metered network, or a build you want identical on every deployment. This guide covers where the FOD ISO comes from and how to integrate its packages with NTLite, offline or on a running system.

What Features on Demand Are

A Windows installation ISO carries the base operating system. Anything optional is published separately as a FOD package and pulled in on demand, either when you tick a box in Windows Features or when an app asks for it. Typical contents:

  • Display language packs and the smaller Language Interface Packs
  • Media support for N editions of Windows, sold without the media stack in the EU
  • Remote administration and management tooling
  • Speech, handwriting, and optical character recognition components
  • Legacy and compatibility components carried forward from older releases

Each release has its own matching FOD set. A package built for one Windows version will not integrate into another, which is the single most common reason a FOD add fails.

Where to Get the FOD ISO

Microsoft publishes the packages as one ISO per Windows version, named along the lines of Windows 11 Language and Optional Features (LoF). It is not offered on the consumer download page next to the Windows ISO. Sources that carry it:

  • Microsoft Volume Licensing Service Center (VLSC)
  • Visual Studio Subscriptions (formerly MSDN)
  • OEM and partner download portals

For language packs specifically, the community keeps a per-version link list on the forum: Language Packs thread.

Version matching: take the FOD ISO that matches the Windows version and architecture of the image you loaded. A 24H2 image needs 24H2 packages, and x64 packages do not apply to an x86 image.

Point NTLite at the FOD Cache

NTLite reads optional-feature packages from a FOD cache folder, so it can enable features without a network round trip. The first time you enable a feature that needs one, it prompts for that cache location.

  1. Load your Windows image in NTLite
  2. Open File Settings and note the Update Cache path
  3. Find the version-matched FOD subdirectory under it, for example 11.21H2.x64.FOD for that Windows 11 build
  4. Mount the FOD ISO and copy the content of its LanguagesAndOptionalFeatures directory into that cache folder

The cache is reusable. Populate it once per Windows version and every later image of that version picks the packages up without the ISO being present.

Enable Features on an Image

With the cache populated, optional features integrate like any other change to the image:

  1. Go to the Features page
  2. Enable the features you want present in the deployed system
  3. Go to Apply Process

Because the state lives in the image, every machine installed from it comes up with those features already on, with no per-machine step and no download at first boot. Save it as a preset and the same set applies to next month's rebuild.

Add Features to a Running Windows

The same flow works against a system that is already installed. On the Image page, load the live install (C:\Windows) instead of an image file, then enable features and process as above. This is the answer when one machine is missing a component and reinstalling it is not worth the disruption.

Changes to a live install apply to the operating system you are running. Read the popup warnings before processing, and have a restore point or backup for anything you cannot rebuild.

Editing a live install carries the same licensing as working on image files, so this is not a paid-tier path. See the Image page for the full loading reference.

Language Packs From the Same ISO

Display languages ship inside the FOD ISO as individual CAB files, and they take the update path rather than the Features page:

  1. Take the CAB matching your language and architecture, for example Microsoft-Windows-Client-Language-Pack_x64_de-de.cab for 64-bit German
  2. Go to the Updates page
  3. Click Add File and select the CAB
  4. Go to Apply Process

The Language Packs guide covers multi-language images, setting the default display language, and the language-code list in full.

Troubleshooting

A Feature Will Not Enable

The package for it is missing from the cache. Confirm the cache subdirectory matches the loaded image's version and architecture, and that the ISO content was copied from LanguagesAndOptionalFeatures rather than the ISO root.

Integration Fails on a Serviced Image

Add optional features and language packs before the image is finished rather than after a heavy component removal, and integrate cumulative updates in the same pass so the servicing stack sees a consistent set.

The ISO Is a Different Build

A near-miss build usually fails at integration rather than silently working. Get the FOD ISO for the exact version you are servicing; there is no supported way to retarget packages from another release.