Add software to windows image

Modify a Windows image using DISM

You can make changes to offline mounted or applied Windows images without booting into the operating system you’re going to modify.

Mounted images are WIM, VHD, or FFU files that have their contents mapped to a folder. Changes to mounted images are made from either a Windows 10 technician PC, or from WinPE. You run run DISM commands against a mounted image, as well as run common file operations such as copying, pasting, and renaming on a mounted image. To save changes you make to the image, use the /commit option when you use DISM to unmount the image. To make changes to a mounted image, use DISM /image: .

Applied images are WIM, VHD, or FFU image files that have been applied to a specified partition. Offline changes to an applied image are usually performed from WinPE. To make changes to an applied image, use DISM /image: .

When you apply an image that you’re going to recapture, apply the image to the root folder of a drive. If you recapture an image that wasn’t applied to the root of a drive, the image will inherit the parent folder’s security descriptors and might not be the same as what would be captured if the image was applied to the root of a drive. See Applying an image to learn how to apply an image.

You can mount and modify multiple images on a single computer. For more information, see Deployment Image Servicing and Management (DISM) Best Practices.

Make your image ready for modification

Before you can make changes to your image, you’ll have to mount or apply the image depending on your scenario.

Mount an image

You can mount an image using the /optimize option to reduce initial mount time. However, when using the /optimize option, processes that are ordinarily performed during a mount will instead be completed the first time that you access a directory. This may increase the time that’s required to access a directory the first time after mounting an image using the /optimize option.

Open a command prompt with administrator privileges.

If you are using a version of Windows other than WindowsВ 8 or Windows 10, use the Deployment Tools Command Prompt that gets installed with the ADK.

Use DISM to mount the image

To mount a Windows image from a VHD or FFU file, you must specify /index:1 .

For more information about the options available for the /Mount-Image option in DISM, see DISM Image Management Command-Line Options.

Apply an image

See Apply an image to learn how to an apply an image.

Modify an image

You can use DISM to modify a mounted or applied image. You can add and remove drivers, packages, language packs, enumerate drivers and packages, modify configuration settings, and more.

View and modify an image

You can create, view, and edit files on a mounted image, just as you would any other file on your PC. When you modify the files in a mounted image, those file changes get saved in the image. Note that although you can add application files and folders, you can’t install applications directly into a mounted image in the same way that you would on a running PC. If you must add an application or a device, verify that you included all of the required files.

Add and remove drivers

See Add and remove drivers to an offline Windows image to learn how to work with drivers. Note that the DISM driver commands will only run against an offline image.

Add and remove packages

See Add or remove packages offline using DISM to learn how to work with packages.

Add or remove languages

Upgrade to a higher Windows edition

Any changes you make to a mounted image are also applied to each potential target edition of Windows. Each target edition is staged in the image. The changes will not be lost when you upgrade to a higher edition of Windows.

Reduce the size of an image

You can use DISM to reduce the footprint of a Windows image by cleaning up superseded components and resetting the base of the superseeded components.

At an elevated command prompt, run the following command to reduce the size of the image file:

Commit changes to an image

Mounted image

You can commit changes to an image without unmounting the image.

At the administrator command prompt, type:

Use /CheckIntegrity to detect and track .wim file corruption when you commit changes to the image. When you apply or mount the image, use /CheckIntegrity again to stop the operation if file corruption was detected. /CheckIntegrity cannot be used with virtual hard disk (VHD) files.

Читайте также:  Asus vivobook x540lj драйвера для windows 10

Applied image

Changes to applied images are saved, and you don’t need to take any steps to commit the changes you’ve made.

Unmounting an image

This only applies to mounted images. Applied images don’t need to be unmounted.

After you modify a mounted image, you must unmount it. If you mounted your image with the default read/write permissions, you can commit your changes. This makes your modifications a permanent part of the image.

If you modified an applied image, you don’t have to do anything else. You’ll see any changes you made when you boot the PC.

Open a command prompt or the Deployment and Imaging Tools Environment with administrator privileges.

Unmount the image.

where C:\test\offline is the location of the mount directory. If you do not specify the parameters to unmount, this option lists all of the mounted images but does not perform the unmount action.

You must use either the /commit or /discard argument when you use the /unmount option.

Troubleshooting

If the DISM commands in this topic fail, try the following:

Make sure that you are using the WindowsВ 10 version of DISM that is installed with the WindowsВ ADK.

Don’t mount images to protected folders, such as your User\Documents folder.

If DISM processes are interrupted, consider temporarily disconnecting from the network and disabling virus protection.

If DISM processes are interrupted, consider running the commands from the Windows Preinstallation Environment (WinPE) instead.

Add updates to a Windows image

For many customizations, like adding .inf-style drivers, Windows updates or upgrading the edition, you can mount and edit the Windows image. Mounting an image maps the contents of a file to a temporary location where you can edit the files or use DISM to perform common deployment tasks.

Notes

Add languages before major updates. Major updates include hotfixes, general distribution releases, or service packs. If you add a language later, you’ll need to re-add the updates.

Add major updates before apps. These apps include universal Windows apps and desktop applications. If you add an update later, you’ll need to re-add the apps.

For major updates, update the recovery image too: These may include hotfixes, general distribution releases, service packs, or other pre-release updates. We’ll show you how to update these later in Lab 12: Update the recovery image.

If a Servicing Stack Update (SSU) is available, you must install it before applying the most recent General Distribution Release (GDR) or any future GDRs. See Windows 10 update history to see the most recent GDR.

Add a Windows update package to an image

Get a Windows update package. For example, get the latest cumulative update listed in Windows 10 update history from the Microsoft Update catalog. If the update has any prerequisite updates, get those too.

Add the updates to a mounted or online image. For packages with dependencies, either install the packages in order, or add them all at once using a single DISM command.

Example: adding a cumulative update to a mounted image:

Example: adding multiple updates:

Verify that the packages appear correctly:

Review the resulting list of packages and verify that the list contains the package. For example:

Each package will usually be a new KB, and will increase the build revision number of Windows on the device. The revision number of windows a device can be found in the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\UBR .

If you’re done updating your image, you can unmount it, committing changes.

Add languages to Windows images

To add a language to your personal PC, go to Settings > Time & Language > Language, and choose a language to install. Learn more.

You can add languages and regional support to Windows 10 (except for Windows 10 Home Single Language and Windows 10 Home Country Specific editions), and Windows Server.

Windows installations start with at least one language pack and its language components. You can add:

  • Language packs: Localization packages for Windows, delivered as a .cab file, for example, Microsoft-Windows-Client-Language-Pack_x64_es-es.cab. Includes UI elements like text for dialog boxes, menu items, and help files.
  • Language Interface Packs (LIPs): Partially-localized language pack. Requires a base language pack. In Windows 10, version 1809, LIPs are delivered as Local Experience Packs (LXPs) .appx files, for example, LanguageExperiencePack.am-et.neutral.appx. For previous versions of Windows 10, LIPs are delivered as .cab files, for example, C:\Languages\es-ES\lp.cab.
  • Language features: Language features include language basics (like spell checking), fonts, optical character recognition, handwriting, text-to-speech, and speech recognition. You can save disk space by choosing not to include some language components in your image. While this reduction in image size can be helpful when creating images for devices with limited storage, it does lead to an incomplete language experience. Delivered as .cab files, for example, Microsoft-Windows-LanguageFeatures-Basic-fr-fr-Package.cab.
  • Recovery languages: UI text for the Windows Recovery Environment (WinRE). Delivered as .cab files. Example: lp.cab, WinPE-Rejuv_fr-fr.cab, and more.

Get language resources: Language Pack ISO and Feature on Demand ISO

OEMs and System Builders with Microsoft Software License Terms can download the Language Pack ISO and Feature on Demand ISO from the Microsoft OEM site or the Device Partner Center.

  • For Windows 10, version 1809, LIP .appx files and their associated license files are in the LocalExperiencePack folder on the Language Pack ISO.
  • For previous versions of Windows, Language Interface Packs are available as a separate download.
  • WinRE language packs are distributed on the Language Pack ISO. Don’t use the WinPE language packs that ship with the ADK.

IT Professionals can download language packs from the Microsoft Next Generation Volume Licensing Site.

After Windows is installed, users can download and install more languages by selecting Settings > Time & language > Language > Add a language.

  • Language components must match the version of Windows. For example, you can’t add a WindowsВ 10, version 1809 language pack to Windows 10, version 1803.
  • Windows Server: Full language packs are not interchangeable with Windows 10.
Читайте также:  Калибровка монитора windows 10 samsung

Considerations

Install languages, then updates and apps. If you’re adding languages to an image that already contains apps or updates (for example, servicing stack updates (SSU) or cumulative updates (CU), reinstall the apps and updates.

After you install a language pack, you have to reinstall the latest cumulative update (LCU). If you do not reinstall the LCU, you may encounter errors. If the LCU is already installed, Windows Update does not offer it again. You have to manually install the LCU.

Care is required when installing languages to an image that includes FODs with satellite packages. When FODs have satellite packages, the localized text for the feature may be carried in a satellite package rather than the language pack or primary FOD package. Specific steps must be followed when adding languages to an image that includes these FODs.

  • Starting with Windows 10, version 2004, the default Windows 10 image includes several FODs with language resources in satellite packages. Before adding languages, you must first build a custom FOD and language repository to ensure that the appropriate satellite packages are pulled in when the language is added.
  • For versions of Windows 10 earlier than 2004, this is typically only a concern when you have added a FOD with satellite packages. A best practice here is to add languages first, then FODs.

Size and performance

  • You can install multiple languages and components onto the same Windows image. Having too many affects disk space, and can affect performance, especially while updating and servicing Windows.
  • LXP-backed language packs are smaller than their Lp.cab-backed counterparts.
  • When creating Windows images, you can remove English language components when deploying to non-English regions to save space. You’ll need to uninstall them in the reverse order from how you add them.
  • After the Out-Of-Box-Experience (OOBE) is complete, the default language cannot be removed. The default UI language is selected either during the Out-Of-Box-Experience (OOBE), or can be preselected in the image using DISM or an unattended answer file.
  • Some time after OOBE, any pre-installed languages that haven’t been used are removed automatically. The language-pack removal task does not remove LIPs.

Cross-language upgrades are not supported. This means that during upgrades or migrations, if you upgrade or migrate an operating system that has multiple language packs installed, you can upgrade or migrate to the system default UI language only. For example, if English is the default language, you can upgrade or migrate only to English.

Add language packs, LIPs, and Features on Demand

We’ll check to see if the image includes FODs with language resources in satellite packages, build a custom and local FOD repository, add languages, and verify all language resources were pulled in for each FOD. Then we’ll add a LIP language and the language Feature on Demand packages.

To save space, you can remove English language components when deploying to non-English regions by uninstalling the language components in the reverse order from how you add them.

Mount an image (install.wim) that you plan to deploy using Windows PE or Windows Setup

Mount the Windows image:

Check to see if the image includes FODs with language resources in satellite packages

First, check to see if the image includes FODs with language resources in satellite packages:

Look for Feature on Demand packages, other than the Language Features, that include a language code in their name. For example, MSPaint:

The two packages here with the en-us language code embedded in the name are satellite packages with language specific resources. If any such package is present in your image, you must build a custom FOD and language pack repository to add languages from. This custom repository needs to include all FODs with satellite packages in your image and all language packs you wish to add. This enables DISM to automatically pull in the right FOD satellite packages when a language is added.

Build a custom FOD and language pack repository

If your image contains FODs with language resources in satellite packages you must build a custom FOD and language pack repository before adding language packs to ensure the language resources for each FOD are pulled in. If you fail to do this correctly, these features will not be localized. Starting with Windows 10, version 2004, this includes features such as Notepad, WordPad, MsPaint, and PowerShell ISE included in the image by default. If your image doesn’t include any FODs with language resources in satellite packages you can skip this section and add the FODs and language packs directly from the respective ISOs.

The following methods are recommended for building a custom FOD and language pack repository:

  • If the size of the repository is not a concern, simply copy the contents of the FOD ISO and all language packs into the same directory.
  • For a minimally sized repository, use the /export-source switch with DISM to export just the FODs included in your image that have satellite packages and any other FODs you’d like to add. Copy all language packs of interest into the same directory.

In the following example, we’ll build a minimally sized FOD and language pack repository. First, mount the Language Pack ISO and the Features on Demand ISO with File Explorer. This will assign them drive letters.

Next, export all FODs included in your image that have satellite packages, from the FOD ISO. If you know which languages you intend to add, you can include the associated language features too:

Читайте также:  Wallpapers windows 10 20h2

Where D:\ is the mount location for the Feature on Demand ISO

Next, copy the language packs of interest into the local repository. In this example, all language packs are copied.

Where E:\ is the mount location for the Language Pack ISO

Add language packs, LIPs (LXPs), and language features

Pre-install languages by adding the language packs and their corresponding Feature on Demand packages, including the base languages if you’re adding a LIP language.

Add a language pack:

Add the language pack(s) of interest. Note how the language pack is sourced from the custom repository:

Check to see that both the language pack(s) and FOD satellite packages containing language resources were added:

You should see something like this in the output:

In addition to the fr-fr language pack now appearing in the image, note how the MSPaint Feature on Demand has satellite packages containing both the en-us and fr-fr language codes present. Make sure this is the case for every FOD with language specific satellite packages, for each language you added.

Satellite FOD packages cannot be added manually, you must allow DISM to automatically pull them in.

If satellite FOD packages are not correctly included during image customization, they won’t be automatically pulled in immediately after the image boots.

Add LIP languages. In this example, we add Luxembourgish, which requires the fr-FR base language:

For Windows 10, version 1809 and later, LIP languages are delivered as LXPs:

Where E:\ is the Language Pack ISO

Verify that it’s in the image:

For earlier versions of Windows 10, LIP languages are delivered as .cab files:

Add language and region Features on Demand to support your language packs and LIPs. We recommend including the Basic, Fonts, OCR, Text-to-speech, and Speech recognition FODs if they’re available for the languages you’re pre-installing. Additionally, include the handwriting language component FOD if you’re shipping a device with a pen.

Not all LIP languages have all language components. Luxembourgish (lb-LU), for example, only has basic and handwriting FODs. You can learn which FODs are available for languages in the LP to FOD mapping spreadsheet

Example: adding Basic, OCR, Text-to-Speech, and Speech Recognition to fr-fr:

Example: adding Basic and Handwriting to lb-LU:

Verify that these packages are in the image:

Remove languages, LIPs, LXPs, and Features on Demand.

You cannot remove a language pack from an offline Windows image if there are pending online actions. The Windows image should be a recently installed and captured image. This will guarantee that the Windows image does not have any pending online actions that require a reboot.

Get a list of packages and features installed in your image:

Remove languages, .cab-based LIPs, and Features On Demand:

Remove LIPs added through LXPs:

Verify that they’re no longer in your image:

Change your default language, locale, and other international settings:

As of Windows 10, version 2004, if a .appx-based Language Experience Pack (LXP) backed language is passed as an argument then the language will be set as the System Preferred UI language and its parent language will be set as the Default System UI language. In prior versions only .cab based language packs were supported.

See which language settings are available:

For online images, use Control Panel, or the International Settings PowerShell cmdlets: Get-WinSystemLocale and Set-WinSystemLocale . This works with languages delivered as LXPs.

For more options, see

Add languages to the recovery environment (Windows RE)

For any language you add to Windows, add the language to the Windows Recovery Environment (WinRE), whenever possible.

Not all languages or LIPs have localized recovery images.

Use languages from the Language Pack ISO, not from the Windows 10 ADK, to localize WinRE.

Known issue: Windows RE included with Windows 10 October 2018 Update Thai language image (en-US base language + th-th language pack) shipped with an issue in which an end user will only see UI components (or English) without Thai language text in the Windows Recovery Environment, the text displayed during recovery (Push-button reset), and/or certain screens during the reboot process of feature updates. To fix this issue pre-install the 2018.11D Quality Update.

Mount the recovery image.

Offline: the recovery image is inside the Windows image:

Online:

Note, Windows RE is inside the Windows image until the Out of Box Experience, after which it is moved to a separate recovery partition.

Where D:\ is the Language Pack ISO.

Verify that they’re in the image:

Example output from /Get-Packages:

Commit changes to the recovery image:

For online images, also remove the mount folder:

Capture the changes

Offline: For Windows images (install.wim)

Commit changes to the Windows image:

Online: Modify a running Windows installation

Generalize and capture the image:

To learn more, see generalize.

Next steps

Localize more of Windows:

  • Out of Box Experience (OOBE): Create localized end user license agreements (EULA), registration pages, and instructions for pairing keyboards and mice.
  • Retail demo experience: Showcase your new devices on the retail sales floor with localized content.

Localize the installation process:

Add languages to Windows Setup: Now that you’ve added languages to your Windows image, make sure they appear in Windows Setup. You can also create Windows installation media that works in the user’s preferred language.

Add languages to WinPE to help your technicians install Windows in their preferred language.

Add languages to a Windows distribution share to help users on a corporate network select Windows in their preferred language

Оцените статью