How to Install a Feature On Demand (FOD) Package Offline

Feature On Demand (FOD) packages let you add extra Windows features like language packs, .NET Framework, or graphics tools. Sometimes your PC isn't connected to the internet, or you want to avoid downloading large packages repeatedly. In these cases, installing FODs offline is the way to go. This guide explains how to do it step by step, covering all the details you need to get it right.

Understanding Feature On Demand (FOD) Packages

FODs are Windows features that aren't installed by default but can be added later as needed. Examples include Internet Explorer, Windows Hello Face, or language handwriting support. Microsoft provides these as separate CAB files, which you can obtain from official ISO images or through Windows Update when online. If a PC is on a restricted network or has no internet access, you need to provide these files manually.

Offline installation becomes essential in enterprise environments, air-gapped machines, or when bandwidth is limited. Microsoft maintains FOD ISOs for Windows 10 and Windows 11, often named something like 'Microsoft-Windows-Features-on-Demand-Package'. These ISOs contain dozens or hundreds of FOD CAB files, organized by feature and architecture. Knowing which CAB you need is the first step.

Getting the Correct FOD Source Files

To install a FOD offline, you'll need the correct source files. Start by downloading the 'Features on Demand' ISO that matches your version and edition of Windows. You can get these from the Microsoft Volume Licensing Service Center (VLSC) or your organization's software library. Make sure the language and architecture (x64 or ARM64) match your target system.

After downloading, mount the ISO by right-clicking and selecting 'Mount'. Browse to the folder structure - typically the CAB files are inside directories like 'FeatureCab' or 'Microsoft-Windows-LanguageFeatures-...'. Identify the CAB file for your desired feature. For example, the 'Microsoft-Windows-Notepad-FOD-Package' CAB installs Notepad. If you're unsure which CAB to use, Microsoft's FOD documentation lists each feature with its corresponding file name.

Preparing Your Environment for Offline Installation

Before installing, check your Windows version and ensure you have administrative rights. To verify your Windows build, open Command Prompt and run winver. Mismatched versions can cause installation errors. It's also good practice to copy the required FOD CAB files to a folder on your local drive, such as C:\FODs, rather than accessing them directly from a mounted ISO, especially if you're deploying to multiple machines.

If you plan to install FODs on several computers, keep all the necessary CABs in a shared folder or on a USB drive. This makes repeated installations faster and more reliable. Also, make sure the target system does not have pending updates or reboots, as these can block feature installation.

Using DISM to Add FOD Packages Offline

The Deployment Image Servicing and Management (DISM) tool is the standard way to install FOD CABs offline. Open an elevated Command Prompt (right-click, 'Run as administrator'). Use the following command, replacing the paths and filenames as needed:

DISM /Online /Add-Capability /CapabilityName:FeatureName~~~~0.0.1.0 /Source:C:\FODs /LimitAccess

For some features, you may need to use /Add-Package instead, pointing directly to the CAB file:

DISM /Online /Add-Package /PackagePath:C:\FODs\Microsoft-Windows-Notepad-FOD-Package~31bf3856ad364e35~amd64~en-US~.cab

The /Online switch tells DISM to work on your running system. The /LimitAccess flag ensures Windows only uses your provided source, not Windows Update. If you see a success message, the feature is now installed.

Verifying the FOD Installation

After installation, it's important to confirm the feature was added correctly. You can check this with DISM:

DISM /Online /Get-Capabilities

This lists all optional features and their status. Look for your installed feature - it should show as 'State : Installed'. For some features, you may want to check in the Windows Features dialog or control panel, or simply launch the feature to test it, such as opening Notepad or changing input language options.

If the feature isn't showing as installed, review your command syntax and make sure you used the correct architecture and language CAB. Sometimes, a reboot is required before a feature becomes active, especially for major components.

Common Errors and How to Fix Them

Errors during FOD installation are common, but most have straightforward solutions. Error 0x800f0954 usually means Windows tried to fetch the feature from Windows Update but couldn't. Make sure to use the /LimitAccess flag and verify your source path. If you see 'The specified package is not applicable', double-check your Windows version, architecture, and language against the CAB file you're using.

Other issues can stem from corrupted source files, pending updates, or lack of disk space. Try running sfc /scannow to repair system files, and ensure you have enough free storage. If DISM still fails, consult the C:\Windows\Logs\DISM\dism.log file for detailed diagnostics. The log will often point to the exact line or file that's causing trouble, which can save time hunting for the root cause.

Automating FOD Deployment Across Multiple PCs

If you're managing several computers, scripting the FOD installation can save hours. Batch scripts or PowerShell can loop through a list of features and run DISM automatically. For example, a batch file can iterate CAB files in a folder and install each in turn. Store your FOD source files on a network share accessible to all deployment targets, and run the script remotely or via tools like Group Policy or System Center Configuration Manager (SCCM).

Document each step and test your script on a non-critical machine first. Automating FOD installation reduces manual errors and ensures consistency across your fleet. Remember to update your FOD source repository when updating Windows builds, as new features or updated CABs may be needed after a major upgrade.

Frequently asked questions