Configure customizations using Windows

ICD
You can use Windows Imaging and Configuration Designer (ICD) to configure the Windows
device UI, connectivity settings, and user experience to better reflect your brand, to meet mobile
network requirements, to comply with IT department security requirements, or to fit market
segments or regions where the device will ship.

For more information about what customization assets and configuration settings are supported
depending on the workflow you're using, see Supported Windows customizations.

The following screenshot shows what you might see in the Customizations Page for a particular
Windows edition.

The Customizations Page contains these elements:

Project Information panel - Summarizes the information for the current project
including the selected project workflow and the Windows edition that was selected for
customization.
 Available Customizations panel - Shows the assets and settings that you can customize
for the selected project.
o Deployment assets are configurable customizations that are not settings. These,
and more information on how to configure them, are as follows:
Applications - To add an app
Driver set - To add a driver set
Drivers - To add a driver
Features on demand - To add an individual feature package
Language Packages - To add a language pack
Reference device data - To import reference device data
Windows Updates - To add OS updates

Important For Windows 10, if you build a provisioning package that contains
any asset and then install the package during the first runtime experience or later,
the asset will not be installed on the device. Assets can only be applied during the
deployment process and not at runtime.

o Image time settings are applied to a Windows image while the image is offline,
which can be during offline image customization process or during the image
build process. For more information on how to configure them, see To customize
OS settings.
o Runtime settings are applied to a running OS on a Windows device, or after
Windows image installation is completed and has reached to the desktop on a
device. The settings can be defined with variant targets for supporting
multivariant so that the device can be conditionally configuration based on
selected region/locale. For more information on how to configure them, see To
customize OS settings.
Customizations Editor panel - Displays information about the asset including the asset's
name and path, shows the default OS value and description for a setting (if available),
and lets you set different values for these settings and assets. You will do most of your
customization work in this panel.
Configured Customizations panel - Shows the assets and settings that you have saved or
set in the Customizations Editor panel. The configured customizations is a list of
customizations that will be included in the provisioning package.

If there are any assets or settings that you want to change or remove, see the following
sections for more information on how to do this:

o To remove or change an asset

o To remove or change a setting

To add an app
Select the Applications asset to add a Store or LOB App.
1. Click the Browse... button to launch File Explorer to search and locate the path to a Store
or LOB App .appx or .appxbundle package, dependency package, license file, source
custom data file, or source shared local data file.
2. Select the .appx or .appxbundle, depdency package, license file, source custom data file,
or source shared local data file that you want to add.
3. Specify a friendly name for the app by typing a name in the Name textbox.
4. If you specify dependency packages in the Dependency Package Path textbox, the Store
or LOB App .appx or .appxbundle package name is automatically populated in the Name
textbox and multiple dependency packages are automatically populated in the
Dependency Packages listbox.
5. If you specify an .appxbundle in the Package Path textbox, the bundle already includes
the dependent packages for that app so you can skip specifying any Dependency
Packages.
6. To avoid specifying a license file for the app, check the Skip License checkbox. If you
don't check this box, you must provide a license file for the app. This checkbox is not
checked by default.
7. Click Add to add the app package to the Configured Customizations panel.

A check mark in the Available Customizations pane appears next to the asset that you
added.
To add driver set
Select the Driver Set asset to add a driver set.

1. Click the Browse... button to launch File Explorer to search and locate the path to a
folder that contains your driver files or packages.
2. Select the folder that contains the driver set. The driver set in the specified folder must be
in the INF format.

This populates the Driver Set Path textbox.

3. Specify a friendly name for the driver set by typing a name in the Name textbox.
4. To allow unsigned drivers to be added, check the Force unsigned install checkbox. This
is not enabled by default.
5. Click Add to add the driver set to the Configured Customizations panel.

A check mark appears next to the asset that you added in the Available Customizations
pane.

To add a driver
Select the Drivers asset to add a driver.

Note This asset is only available when you're customizing an image for Windows 10 for desktop
editions (Home, Pro, Enterprise, and Education).

1. Click the Browse... button to launch File Explorer to search and locate the path to a
folder that contains your driver files or packages.
2. Select the folder that contains the driver. The driver(s) in the specified folder must be in
the INF format.

This populates the Driver Folder Path textbox.

3. Specify a friendly name for the driver by typing a name in the Name textbox.
4. To allow unsigned drivers to be added, check the Force unsigned install checkbox. This
is not enabled by default.
5. Click Add to add the driver to the Configured Customizations panel.

A check mark appears next to the asset that you added in the Available Customizations
pane.

To add an individual feature package

Select the Features on demand asset to add an individual feature package (.cab).

Important

Windows ICD applies packages based on the order that you provide to the tool. A features on
demand package has internal dependencies so you must follow a specific install order when
using Windows ICD.

When you uninstall features on demand packages, the packages must be removed in the opposite
order of the installation order (or from last to first).

The following table shows the dependent packages you need to install to enable certain features.
For more information, see Features On Demand V2 (Capabilities).

Feature to enable Dependencies (first to last)

Cortana Language pack, basic, text-to-speech, speech
Pen support Basic, handwriting
Optical character recognition Basic, OCR
Handwriting recognition Basic, handwriting
Text-to-speech Basic, text-to-speech
Speech recognition Basic, text-to-speech recognition, speech

1. Click the Browse... button to launch File Explorer to search and locate the path to an
individual .cab.
2. Select the feature package that you want to add. Once you've selected the package, this
populates the Features package path textbox.
3. Specify a friendly name for the feature package by typing a name in the Name textbox.
4. Click Add to add the feature package to the Configured Customizations panel.

A check mark appears next to the asset that you added in the Available Customizations
pane.

To add a language pack

Select the Language Packages asset to add a language pack. Language packs provide a
translated version of most of the UI.

1. Click the Browse... button to launch File Explorer to search and locate the path to a
folder that contains the language pack's .cab file.
2. Select the .cab file for the language pack.

This populates the Cab File textbox.

3. Specify a friendly name for the language pack by typing a name in the Name textbox.
4. Click Add to add the language pack to the Configured Customizations panel.

A check mark pane appears next to the asset that you added in the Available
Customizations pane.

To import reference device data

Select the Reference device data asset to import an ICB (initial configuration blob). This type of
asset inside a provisioning package is used to store third-party Win32 apps and the system
settings from a running OS.

1. Click Browse... to launch File Explorer and specify the path of the provisioning package
that contains the reference device data, or ICB, captured on a reference device.

The information and content of the reference device data in the specified package is
displayed in the Customizations Editor pane as a read-only list.
 2. Click Add to add the reference device data to the tree view in the Configured
Customizations pane.

To customize OS settings
You can customize certain settings by selecting a grouped setting or an individual subsetting, or
property, from the Settings group.

Note Settings can be applied to a running device during the first runtime experience or later, but
some settings can also be applied during deployment time.

1. From the Settings group in Available Customizations panel, select the setting that you
want to configure.

For most settings, a brief description of the setting and its default value is shown in the
Customizations Editor panel.

2. In the Customizations Editor panel, set the value for the setting that you selected and
then click the save setting button (denoted by a floppy disk) next to the textbox.
 A check mark appears next to the setting that you customized and saved in the Available
Customizations pane.

To add OS updates
Select the Windows Updates asset to add Windows Updates. Windows Updates are .MSU files
that you can add to a provisioning package.

1. Click the Browse... button to launch File Explorer to search and locate the path that
contains the individual Windows Updates (.msu), or the folder that contains multiple
Windows Updates.
2. Select the path. This populates the Update package path textbox.
3. Specify a friendly name for the Windows Updates by typing a name in the Name textbox.
4. Click Add to add the Windows Updates to the Configured Customizations panel.

A check mark in the Available Customizations pane appears next to the asset that you
added.

Important

If you selected a folder path that contains multiple update packages, the folder path will
be added to the Configured Customizations tree view as the parent node to the update
package nodes. In this case, you cannot remove individual update packages from the
configured customizations list as only the folder path that contains all the update
packages can be removed. You must remove the update packages from the folder using
File Explorer before you can add the folder path again using the Customizations Page in
Windows ICD to add the rest of the update packages in the folder.

To remove or change an asset

You can remove or change the information for any asset that you add.

1. Select the asset from the Configured Customizations panel to show that asset's
information in the Customizations Editor panel.
2. To remove the asset, click Remove.
3. To change the information about the existing asset including selecting a different path,
specifying a different name, and so on, update the information that you want to change
and then click Save.

To remove or change a setting

You can remove or change the information for any setting that you add.
1. Select the setting from the Configured Customizations pane to show that setting's
information in the Customizations Editor panel.
2. To reset the value to the default OS value or to remove a setting from the Configured
Customizations pane:
1. From the Selected customizations pane, select the setting you want to reset or
remove.
2. Click the X Remove button next to the textbox.
3. To change the configured value for a setting in the Configured Customizations pane:
1. From the Selected customizations pane, select the setting you want to change.
2. In the configuration pane, type or select the new value for the setting.