How to Convert Install.ESD to Install.WIM on Windows

8.2K

The Media Creation Tool writes the Windows 11 installation image to a USB flash drive in the compressed install.esd file format instead of the usual install.wim file. An install.esd file is a compressed, read-only Windows installation image that cannot be mounted or modified directly without conversion. This guide explains the differences between the ESD and WIM installation image formats and shows how to convert an install.esd file to an install.wim file.

What are the ESD and WIM Image Formats?

ESD (Electronic Software Download) is a highly compressed Windows image distribution format used for deploying the Windows operating system instead of the classical WIM (Windows Imaging Format) image. Due to the use of LZMS compression, the size of the install.esd file is typically 10–30% smaller than the install.wim file.

Unlike WIM images, ESD files use stronger solid compression algorithms (LZMS), which significantly reduce image size but also make image servicing slower and more resource-intensive.

The install.esd format is primarily optimized for Windows distribution and delivery, while install.wim is designed for deployment customization and offline servicing.

Key differences between ESD and WIM images:

Feature	ESD	WIM
Compression ratio	Higher	Lower
File size	Smaller	Larger
Compression type	LZMS (solid compression)	LZX/Xpress
Mountable	Limited	Yes
Writable/serviceable	No (read-only)	Yes
Driver injection	Not supported directly	Supported
Offline servicing	Limited	Fully supported
Deployment customization	Limited	Optimized
Processing speed	Slower	Faster

Generally, ESD is optimized for compact OS distribution, while WIM is optimized for image customization, servicing, and enterprise deployment cases.

Because of these limitations, admins usually convert install.esd to install.wim before integrating drivers, updates, language packs, or customizing Windows deployment images.

Due to its smaller size, the ESD image format provides the following benefits:

• The size of the 64-bit install.esd file is less than 4 GB, so it can be written to FAT32-formatted media for installation on UEFI computers.
• The ESD file downloads faster.
• It takes up less disk space.

One drawback of the install.esd format is that it is read-only and is not intended for normal offline image customization. If you need to inject drivers, packages, or updates into the installation image, convert the required ESD image to WIM first and then service the WIM with DISM. For enterprise deployments, the resulting WIM can be used with supported image-based deployment workflows such as Configuration Manager OSD.

How to Extract Install.ESD from Windows ISO

First, extract the install.esd file from the Windows installation ISO image. Right-click the Windows ISO image file in File Explorer and select Mount

Open the new virtual DVD drive that appears in File Explorer. Navigate to the E:\Sources\ folder, find the install.esd file, and copy it to your local drive to the C:\ESD folder.

Verifying ISO Integrity Before Extracting Install.ESD

Before extracting install.esd, it is a good practice to verify the integrity of the downloaded Windows ISO image.

You can calculate the SHA256 hash of the ISO file using PowerShell command:

Get-FileHash .\Windows11.iso -Algorithm SHA256

You need to compare the resulting hash with the checksum published by Microsoft/your internal software distribution repository.

Verifying image integrity before deployment helps you to prevent issues caused by corrupted downloads, incomplete file transfers, or modified installation media.

Note. In enterprise environments, ISO images are often validated automatically as part of software packaging and deployment workflows before being imported into SCCM, Configuration Manager, or other deployment platforms.

Hint. You can use the archiver tools to view the contents of the install.esd image. For example, open the ESD file with 7-Zip archiver and you will be able to browse the image.

How to Convert an ESD File to WIM on Windows

There are several tools available for converting ESD files to the WIM image format, including both built-in and third-party.

• Native DISM command (Deployment Image Servicing and Management);
• Export-WindowsImage PowerShell cmdlet
• DISM++ graphical tool
• NTLite

Converting Install.ESD to Install.WIM Using DISM

The built-in DISM.exe command-line tool can be used to convert an ESD file to the WIM format. Open the command prompt as Administrator and go to the folder containing the ESD file:

cd c:\esd

The install.esd file may contain several editions of Windows. Each Windows edition in the image file has an assigned index number (1,2,3,4,…). List the editions in install.esd:

Run DISM from an elevated terminal. Before running the commands below, you need to open Windows Terminal, PowerShell, or Command Prompt with Run as administrator. Keep in mind that DISM operations that access, service, mount, export, or modify Windows images may fail with Error: 5 (Access is denied) when the terminal is not elevated.

DISM /Get-WimInfo /WimFile:install.esd

In this case, the install.esd file contains seven different Windows 11 editions, which are indexed from 1 to 7. With DISM, you can extract only one edition from an ESD file at a time. Before proceeding, you need to make sure the destination drive has sufficient free disk space. During conversion and image servicing, DISM may temporarily require 2–3x the size of the original ESD image.

For example, let’s extract the Windows 11 Pro edition with index number 6 and convert it to a WIM file:

dism /export-image /SourceImageFile:install.esd /SourceIndex:6 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity

Note that unlike install.esd (which often contains multiple Windows editions), a newly exported install.wim created with /Export-Image contains only the selected image index (unless additional editions are appended manually).

DISM options

The following DISM options are used:

• /SourceIndex:6 — source Windows image edition index in ESD file
• /compress:max — compress the WIM image file using LZX compression
• /CheckIntegrity — abort the conversion if the source ESD file is damaged or contains errors.

Image format conversion is a quite resource-intensive task. Depending on your computer hardware, it takes about 10-30 minutes to complete.

Check the results

Wait until the message appears:

Exporting image. The operation completed successfully.

The resulting WIM file is about 20% larger than the original ESD file.

Export Multiple Images from ESD to the Same WIM

In large deployment projects, we recommend you to to perform image servicing on a dedicated volume with tens of gigabytes of free space available, especially when you are working with multiple Windows editions, language packs, drivers, and cumulative updates.

In case you need to include multiple Windows editions from the same ESD file, you can export each required image index to the same WIM file. DISM adds each subsequent exported image as a new index in the existing WIM. First, you need to check which editions are available in the ESD file:

DISM /Get-WimInfo /WimFile:C:\ESD\install.esd

Note the indexes you want to export. Do not assume that a specific index, such as 6 or 7, represents a particular edition because the available indexes can vary between Windows installation media.

Now export the first image with the command (run them in an elevated PowerShell session):

DISM /Export-Image `
/SourceImageFile:C:\ESD\install.esd `
/SourceIndex:6 `
/DestinationImageFile:C:\ESD\install.wim `
/Compress:max `
/CheckIntegrity

Then export another image to the same WIM:

DISM /Export-Image `
/SourceImageFile:C:\ESD\install.esd `
/SourceIndex:7 `
/DestinationImageFile:C:\ESD\install.wim `
/Compress:max `
/CheckIntegrity

The second export is added as another image index in the existing WIM. You do not need to apply the ESD image to a folder and capture it again.

Now verify the resulting WIM using the following command:

DISM /Get-WimInfo /WimFile:C:\ESD\install.wim

You should now see both exported image indexes in the WIM.

Now, you can slipstream Windows security updates into a .WIM file, inject drivers, change Windows features, and make other changes to the image.

Example: Mount and Modify a WIM Image

After converting install.esd to install.wim, you can mount the Windows image and make offline changes such as:

• Inject drivers
• Add Windows updates (.MSU or .CAB packages)
• Enable/disable Windows features
• Modify files and registry settings
• Customize deployment settings

Create a mount directory:

mkdir C:\Mount

Mount the WIM image:

DISM /Mount-Wim /WimFile:C:\ESD\install.wim /Index:1 /MountDir:C:\Mount

Add a Windows update package:

DISM /Image:C:\Mount /Add-Package /PackagePath:C:\Updates\windows10.0-kbxxxxxx.cab

Inject drivers into the image:

DISM /Image:C:\Mount /Add-Driver /Driver:C:\Drivers /Recurse

Commit changes and unmount the image:

DISM /Unmount-Wim /MountDir:C:\Mount /Commit

It’s important to note that you should always properly unmount mounted WIM images using DISM /Unmount-Wim. Interrupting a mounted image session/manually deleting the mount directory may corrupt the WIM image.

Tip. Use the /Discard option instead of /Commit if you want to unmount the image without saving changes.

Automating Image Servicing with PowerShell

Keep in mind that in enterprise environments, Windows images are often updated automatically as part of a monthly image maintenance process. Instead of running DISM commands manually, you can automate image servicing with PowerShell.

Here is an example:

$ErrorActionPreference = "Stop"

$WimFile = "C:\ESD\install.wim"
$MountDir = "C:\Mount"
$Updates = "C:\Updates"
$Drivers = "C:\Drivers"

$mounted = $false

try {
New-Item -Path $MountDir -ItemType Directory -Force | Out-Null

Mount-WindowsImage `
-ImagePath $WimFile `
-Index 1 `
-Path $MountDir

$mounted = $true

Get-ChildItem -Path $Updates -Filter *.cab -File |
ForEach-Object {
Add-WindowsPackage `
-Path $MountDir `
-PackagePath $_.FullName `
-ErrorAction Stop
}

Add-WindowsDriver `
-Path $MountDir `
-Driver $Drivers `
-Recurse `
-ErrorAction Stop

Dismount-WindowsImage `
-Path $MountDir `
-Save `
-ErrorAction Stop

$mounted = $false
}
catch {
Write-Error "Image servicing failed: $($_.Exception.Message)"
}
finally {
if ($mounted) {
try {
Dismount-WindowsImage `
-Path $MountDir `
-Discard `
-ErrorAction Stop
}
catch {
Write-Error "Failed to discard the mounted image: $($_.Exception.Message)"
}
}
}

You can integrate the script into Configuration Manager task sequences, Azure DevOps pipelines, GitHub Actions, or other image build workflows.

In production environments, you should consider adding Try/Catch error handling and ensure that Dismount-WindowsImage is always executed in order to prevent orphaned mounted images.

What to do if the resulting WIM file is larger than 4GB?

In case the resulting WIM file is larger than 4GB, it cannot be stored on a FAT32-formatted USB drive because FAT32 has a maximum file size limit of 4GB.

In this case you can split the original WIM into several smaller SWM (split WIM) files. The following DISM command will split install.wim into several 3GB SWM files:

Dism /Split-Image /ImageFile:C:\esd\install.wim /SWMFile:C:\esd\install.swm /FileSize:3000

Now, copy the SWM files into the /Sources folder on your installation USB stick. The Windows Installer automatically detects and combines the SWM files during Windows Setup.

Export-WindowsImage: Convert ESD to WIM with PowerShell

The Export-WindowsImage PowerShell cmdlet can also be used to convert an ESD file to the WIM image format.

List Windows editions in the install.esd file:

Get-WindowsImage -ImagePath "c:\esd\install.esd"

Export the Windows edition with the index number of 6 from Install.ESD to Install.WIM.

Export-WindowsImage -SourceImagePath F:\sources\install.esd -SourceIndex 6 -DestinationImagePath C:\esd\install.wim -CheckIntegrity

If you have a large WIM file that you need to split into a number of smaller SWM files, run the command:

Split-WindowsImage -ImagePath F:\esd\install.wim -SplitImagePath "F:\ESD\Temp\install.swm" -FileSize 3800

Common DISM and ESD Conversion Errors

Before troubleshooting DISM errors, you need to check that you are using a DISM version that supports the target Windows image. Many image servicing problems occur when an older DISM version is used with newer Windows releases.

When converting Install.ESD to Install.WIM with DISM/PowerShell, you may face several common errors.

Image Index Not Found

In case DISM reports that the specified image index does not exist, you should verify which Windows editions are available in the install.esd file using the command:

DISM /Get-WimInfo /WimFile:install.esd

Then use the correct value in the /SourceIndex parameter.

Error 87: The parameter is incorrect

Error 87 usually indicates incorrect DISM command syntax, unsupported parameters, or missing spaces in the command line. You should carefully verify the command syntax and make sure all parameters are typed correctly.

Error 0xc1420127

This error may indicate corrupted image metadata/damaged install.esd file. You should try the following:

1. Re-copy the install.esd file from the Windows ISO
2. Verify the ISO checksum
3. Run DISM with the /CheckIntegrity option
4. Use DISM from a supported Windows ADK appropriate for the Windows release you are servicing. When working with newer Windows 11 images, you should avoid servicing them with an older ADK/DISM environment.

“The system cannot find the file specified”

This error usually occurs when:

• The install.esd path is incorrect
• The working directory is wrong
• The ESD file was not copied from the ISO image
• The destination folder does not exist

You should verify if the install.esd file exists in the specified path and that the destination directories have been created.

Access is denied

If DISM cannot create or write the install.wim file, run Command Prompt or PowerShell as Administrator and make sure the destination folder is writable.

NTLite: How to Convert Install.esd to Install.wim

NTLite is a popular Windows deployment customization tool. It has a user-friendly interface for servicing Windows images, integrating drivers and updates, automating setup, and removing Windows components. NTLite is free for non-commercial use. You can download it here.

To convert the install.esd from the Windows image to the install.wim format, run NTLite, and follow these steps:

1. Select Add > Image file (WIM, ESD, SWM) > select your install.esd file;
   

   

2. Select the Windows edition in the ESD image that you want to export to a WIM;
3. Select Export > WIM in the context menu. Or click on the heading Operating System and select Export all > WIM;
   

   

4. Wait for NTLite to finish exporting the Windows image from the ESD file to the WIM format.

Then you can copy the install.wim file to your distribution media or use it with a supported image-based deployment solution (such as Microsoft Configuration Manager).

For modern cloud-managed Windows deployments, you can use Microsoft Intune with Windows Autopilot without maintaining a customized OS image. Windows Autopilot currently includes both the traditional Windows Autopilot deployment experience and Windows Autopilot device preparation. Device preparation is designed to simplify cloud-native provisioning and supports Microsoft Entra join without requiring traditional Autopilot device registration, while classic Windows Autopilot provides additional deployment scenarios and customization options. You need to choose the method based on your deployment requirements.