The ESD folder on Windows 10 stores compressed files used by the system for updates and recovery mechanisms. Understanding what this folder contains, how much space it occupies, and in what scenarios it is involved allows for informed decisions regarding its management, especially when disk space becomes critical.
ESD, WIM, and ISO: Comparing Windows Image Formats
Windows 10 handles several system image formats. The ESD file (Electronic Software Download) is a highly compressed variant of the WIM format (Windows Imaging Format), which can itself be encapsulated in an ISO container. Each format serves a distinct purpose.
| Criterion | ESD | WIM | ISO |
|---|---|---|---|
| Compression | Maximum (recovery) | Medium to high | None (container) |
| Typical size | Lighter than WIM | Heavier than ESD | Variable depending on content |
| Modifiable with DISM | No (read-only) | Yes (mounting, driver injection) | No directly |
| Main use | Download, recovery | Enterprise deployment (WDS/MDT) | Installation media |
| Conversion needed | To WIM for customization | Usable as is | Prior extraction |
The ESD format was introduced to reduce bandwidth when downloading major updates. In return, an ESD file cannot be mounted or modified directly: any customization (adding drivers, modifying editions) first requires conversion to WIM using the DISM command.
To delve deeper into the exact role of the esd folder on Windows 10, one must examine the update and repair mechanisms that rely on these compressed files.
$Windows.~BT Folder and ESD Files: Role in Windows 10 Updates
During a major update of Windows 10, the system downloads an install.esd file into the hidden folder C:$Windows.~BT. This temporary directory serves as a transit area: it contains the compressed image of the new version before the installation begins.
Once the update is complete, these files are not automatically deleted. They persist on the disk, sometimes duplicated if multiple successive updates have been downloaded. This is a point documented by the Microsoft Q&A forum: users find the presence of two distinct ESD files after an update, each occupying a significant amount of space.
Why Windows Keeps These Files After Installation
Windows retains these ESD files to allow a rollback to the previous version. Rollback remains possible for a limited time after the update. After this period, the files become unnecessary but remain present until a cleanup is triggered.
The Disk Cleanup tool (cleanmgr) offers an option “Previous Windows installation files” that specifically targets this data. The Storage Sense utility, when enabled, can also automatically delete temporary files related to updates.
Offline System Repair with DISM and ESD File as Source
The DISM (Deployment Image Servicing and Management) command can use an ESD file as a repair source, even on machines without Internet access. This is still a common scenario in 2026, especially in professional environments.
The typical syntax looks like this:
DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:pathinstall.esd:index
The index parameter is critical. Each ESD file contains several editions of Windows (Home, Professional, Enterprise), identified by an index number. The command DISM /Get-WimInfo allows you to list the available editions and their respective indexes before initiating the repair.
Edition-Architecture Matching: A Common Pitfall
Microsoft emphasizes a technical point often overlooked in public tutorials: the edition, architecture, and version level of the source image must exactly match the target installation. Using an ESD file from a Home edition to repair a Professional installation will cause an error. Similarly, a 64-bit ESD cannot serve as a source for a 32-bit system.
- Check the installed edition with the winver command or in system settings
- List the indexes of the ESD file with DISM /Get-WimInfo /WimFile:pathinstall.esd
- Select the index that exactly matches the edition and architecture of the target machine
In case of a mismatch error, DISM returns a failure code without always clearly specifying the cause, complicating diagnosis for inexperienced users.
Disk Cleanup and ESD Files: What Can Be Safely Deleted
The question arises consistently: can ESD files be deleted to reclaim space? The answer depends on the context of use.
- ESD files in $Windows.~BT can be deleted via Disk Cleanup once the update is validated and the rollback period has expired
- The install.esd file located in C:Recovery or in the Sources folder should not be deleted manually: it is used for PC reset
- ESD files downloaded via Windows Update in SoftwareDistribution can be cleaned up by stopping the Windows Update service and then emptying the folder
Microsoft has evolved the Windows recovery logic towards “cloud rebuild” scenarios, where system recovery involves downloading an image rather than using a local ESD/WIM image. This approach gradually reduces dependence on locally stored ESD files but does not eliminate it for machines without reliable network connectivity.
Storage Sense and Automated Cleanup
Storage Sense, integrated into Windows 10, can be configured to automatically delete temporary files, including those related to updates. This feature is not enabled by default. Its settings allow you to define a timeframe after which update files are purged.
The ESD folder remains a discreet but structural technical component in the maintenance architecture of Windows 10. Its management poses no issues as long as the distinction between temporary update files and system recovery files is respected. Deleting the former frees up space, while deleting the latter compromises the reset capability of the machine.
