Guides / Language Packs

Language Packs

Add Windows display language packs with NTLite: tick the language, and the pack is downloaded and integrated into an image or an already running Windows.

Language packs enable multilingual Windows installations. NTLite offers every display language Microsoft publishes for the loaded image as a tick on the Features page, downloads the pack and integrates it - into an image, or into a Windows that is already installed and running. There is no language pack ISO to find first.

Integrate Language Packs

  1. Load your Windows image in NTLite (Windows 10 or newer)
  2. Go to the Features page, Features on Demand tab
  3. Type the language into the search box and tick its language pack, the first row of the language's group
  4. Optionally tick the language's other rows: basic typing, handwriting, OCR, speech and text-to-speech
  5. Queue the latest cumulative update on the Updates page. On Windows 11 24H2 and later the pack queues it for you, along with the checkpoint update it needs
  6. Go to Apply → Process

The tick queues the pack on the Updates page, where it is downloaded at Apply and integrated ahead of the cumulative update. Users can switch display language via Windows Settings after installation. The language's other rows can be fetched before the run with Download on the Features toolbar Premium; the pack itself always downloads at Apply.

Why the cumulative update: a language pack comes at its release build and stays out of date until a cumulative update is applied after it. The Apply page warns when none is queued.

The pack goes further than the install image. Windows Setup (boot.wim) and the recovery environment get the matching WinPE language, so setup and recovery speak the language too; the row's hover card names the loaded images it goes to.

Already have the pack as a CAB? Add it on the Updates page with Add → File; its row on the Features on Demand tab then shows ticked and locked, and the tab leaves your file alone.

Add a Language Pack to a Running Windows

The steps above prepare media for machines you have not deployed yet. When Windows is already installed and someone needs another display language on it, you do not have to rebuild anything - NTLite services the installed Windows the same way it services an image file:

  1. On the Image page, load the live install (C:\Windows) instead of an image file
  2. On the Features page, tick the language pack on the Features on Demand tab
  3. Go to Apply → Process

The new language then appears under Windows Settings → Time & language, ready to select. The Image page covers the loading reference in full. For a fleet, or for anything you will rebuild next month, put the language in the image instead so this is never a per-machine step.

Read the warnings: changes to a live install apply to the operating system you are running. Have a restore point for anything you cannot rebuild.

Multi-Edition and Multi-Language Images

Adding several languages to a multi-edition ISO does not multiply the wait. NTLite services each edition in parallel, in its own DISM process, so all editions finish in roughly the time one would take. The scaling is automatic - it adapts to the CPU and leaves a little headroom so the machine stays usable, for example servicing three editions at once on a 4-thread CPU.

Give it room to work: every edition is mounted separately, so free disk space is usually the limit you hit first. Queue order inside a single apply is handled for you - language packages are integrated ahead of the updates that service them.

Keep a Language Baseline for Monthly Rebuilds

Language packs change rarely, cumulative updates change every month. Redoing the language work on every refresh wastes the slowest part of the build, so integrate the languages once and keep that result as a reusable baseline:

  1. Integrate the language packages, apply, and name the result clearly
  2. Right-click the image on the Image page and choose New edit - the language-pack image becomes your read-only reference, and the new edit is the working copy you build in
  3. Each month, right-click the edit and choose Revert to drop back to language-packs-only, then apply your preset with the latest updates

Because Revert only mirrors the differences from the reference, getting back to a clean language baseline is quick - and rebuilding this way is faster than assembling a fresh multi-language image from UUP each month. The edit and reference mechanics are covered in the Image Management guide.

Set Default Language

To set a non-English default language for unattended installation:

  1. Go to the Unattended page
  2. Find the Regional Settings section
  3. Set UI Language to your desired language code
  4. Optionally configure keyboard layout and locale settings to match

Troubleshooting

  • A language group with no language pack row: Microsoft publishes no display language pack for it (Windows delivers that one through the Store), so only its typing and speech parts are offered
  • A blocked download asks to retry, and the report after the run names the ISO to get and the folder to extract it into; see Features on Demand, Offline or Blocked Downloads
  • If a CAB you added yourself fails, verify its version, build and architecture match the image
  • Setup language is automatically included when integrating a language pack
.NET 3.5 FrameworkFeatures on Demand (FOD)