Supported Windows customizations
Windows 10 supports the following customizations:
Customization assets are imaging collaterals that partners can add to a base Windows image to generate a model or master image for a model device.
Microsoft-provided Windows desktop images are in Windows image (WIM) containers. Partners can customize the WIM images offline by using DISM as an offline servicing of a Windows image, or by using Windows Setup during the offline phase of Windows deployment. Partners can add customization assets to a desktop image directly in their existing formats. The assets are normally collected from various sources and placed in a repository as a pre-requisite of the offline image customization process.
The following table lists the supported asset types for desktop imaging.
|Asset type||File type||Description||Examples|
The .appx or .appxbundle package along with the dependency packages, license file, and optional custom data file can be provisioned in a desktop image. These assets are configured for each user at first logon.
An individual driver and its payload will be added to the driver store in a desktop image, and boot critical drivers will be reflected.
All driver INFs and their payloads in a specified folder will be added to the driver store in a desktop image. Boot critical drivers will be reflected.
Folder containing multiple driver INFs
In Windows 10, language packs are refactored so the size of packages are much smaller.
fr-fr.cab for French language in France
Features on demand package
Features on demand v2 packages, for example, language component packages or .NET, are optional features that can be added to a desktop image on demand.
Windows update package
KBs downloaded from Windows Update or Windows Server Update Services can be installed in a Windows desktop image to keep images up-to-date and secured.
Reference device data
Reference device data are Windows desktop application files and registry settings captured in a provisioning package by USMT ScanState command from a reference device. Instead of installing a Windows desktop application online on a device, you can install the app to a desktop image offline by importing the provisioning package that contains reference device data.
While desktop imaging starts with hardware-agnostic OS images in WIM containers that can be customized offline, mobile imaging starts with OS packages in .zip files provided by Microsoft and board support packages (BSPs) provided by the silicon vendor. Partners use Microsoft-provided imaging tools to build device platform-specific full flash update (FFU) images that can be flashed through USB tethering to target devices.
FFU images are not offline customizable, and unlike Windows Setup, the sector-based USB flashing deployment does not have an offline phase where customization assets can be injected to the image. Hence, customization assets like drivers, language packs, and applications must be provided as feature packages wrapped in CAB (.spkg for Windows Phone 8.1, and .cab for Windows 10) container. You can add the feature packages to a mobile image at image build time by using feature manifest files and OEMInput files. For more information, see Specifying packages to include in images by using feature manifest files in Building a phone image using ImgGen.cmd.
Other than creating feature packages, customization with apps (.appx or .appxbundle packages) can also be done by using the Applications configuration support in Windows Imaging and Configuration Designer (ICD). For more information, see To add an app in Configure customizations using Windows ICD.
Each Windows OS component can have a set of configuration settings defined in manifest XML files. The manifest XML file defines the hierarchical XML structure of the settings mapping into the registry hive of an OS image. Microsoft uses the XML schema to define policies, customizable values, and the default value of a setting. The XML schema also allows for the definition of asset payloads associated with a setting. The definition is also used to specify the source location of the asset payload, and where to install/configure the asset payloads in an OS image. The asset payloads can be files like maps, retail demos, wallpapers, ringtones, OEM logos, or apps.
Based on the manifest XML definitions, partners can author answer files to customize a Windows image. The customization answer files can be applied to a Windows image through Microsoft provided tools at either Windows imaging time or device provisioning time.
Settings are grouped based on the time the configuration settings are applied to a Windows image. These categories are:
Image time or build time settings – These 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. Examples of these settings include touch
CapButtonssettings or tablet PC platform settings.
Deployment time settings – These settings are applied by Windows Setup during deployment of a Windows image. Since Windows Setup is only used for deploying Windows desktop images, the category is applicable to desktop image configuration settings. The settings can be defined with configuration passes, so that they are processed at the defined Windows Setup pass during Window image deployment. For example,
AutoLogonsettings can be defined with generalize or with oobeSystem configuration pass.
Runtime settings – These settings can be 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. Examples of these settings include
For information about the Windows Provisioning settings that you can configure in Windows ICD, see Windows Provisioning settings reference.
For more information, see Provisioning settings store.