The install.wim has given way to an ESD file (install.esd), an Electronic Software Download (ESD). The compression rate of the ESD files is even higher than the compression rate of WIM files using the /compress:max switch. ESD files however, resists some operations like deployment using a WDS server.
Microsoft's latest operating systems ship in with an esd file (sourcesinstall.esd) which replaces wim (same directory) in older operating systems (Windows 7 and below).
For people who use Windows Deployment Server (WDS), esd are not friendly (don't know why microsoft doesn't add the functionality) when it come to deployment of the OS across the network. The following command prompts can convert the esd to wim thus allowing the deployment across the network for newer OS (Windows 8 +)
Get details about what images are inside the ESD file with the command. We'll need to take note of the index No. that we need;
dism /Get-WimInfo /WimFile:install.esd
Take note of the index of the particular OS version you'd like to install (in case the esd has many images therein) the number is what is inserted in the SourceIndex. Am choosing index 1 (Windows 7 Home Premium)
dism /export-image /SourceImageFile:install.esd /SourceIndex:1 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity
After the progress reaches 100% and integrity checks are through, you'll have a WIM file alongside the ESD file
The WIM file can be copied back to the sources folder and used in WDS. In the case of multi images in a single ESD, step 2 should be repeated with the change in the SourceIndex No. only. This will append the index files to the same WIM file.
It should be noted that ESD are highly compressed, and when converted to WIM, the WIM might be slightly bigger.
This just saved me some major time. I wasn't using it for WDS but for fixing corrupt DLLs that sfc/scannow could not fix in Windows 10. Thanks a lot.
I can't get this to work, i have it in the same location but always get access denied. i tried giving full control to everyone but that didnt work either. Any ideas? Maybe my path is wrong, this is it
C:New folderdeploy>dism /Get-WimInfo /WimFile:install.esd
Justin, you need to open up the command prompt as an administrator. It's the dism command that's restricted, not the files you are trying to modify.
I had the same problem as Justin.
I found that running Win7 as the host computer and using dism commands on a Win10.iso Install.esd file does not allow for the Get-WimInfo to execute properly.
After loading a Win10 VM I used the Command 'pushd' Hostnamedeploy
And then ran the dism /get-wiminfo /wimfile:install.esd
Received all of the Wim's in the ESD without issue.
Exporting the Win10Pro to a .wim now.
I am trying to convert an esd file to wim format but am struggling with the detail of the command prompt line in the above guidance which is:-
dism /export-image /SourceImageFile:install.esd /SourceIndex:1 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity
My esd file is in C:UsersJohnDocumentsESD and the destination folder is C:UsersJohnDocumentsWimFolder.
I have established that my version of Windows 10 Pro in the esd file is index1.
Would RWKSHJ be kind enough to spell out the details of the dism command that I need to be able to export and convert the esd file?
Thanks
JOHNSPILLER, what feedback are you getting when you run the above command?
Also, if your current operating system is Windows 7, please refer to SILLDRAYGG's comment above.
RWKSHJ, thanks for your reply - my present system is windows 10 Pro V 1511
The command I used is dism /export-image /SourceImageFile:C:UsersJohnDocumentsESDinstall.esd /SourceIndex:1 /DestinationImageFile:C:UsersJohnDocumentsWimFolder:install.wim /Compress:max /CheckIntegrity
The error I get is Error 123. The Filename, directory name or volume label syntax is incorrect
Hey John,
is see where it goes wrong
/DestinationImageFile:C:UsersJohnDocumentsWimFolder:install.wim
Extremely helpful, thanks! Was about to try some weird 3rd party software and this saved me!
Very handy to know! Saved me a lot of time haha.
Very helpful. Thanks. Saved me a lot of time and effort.
@ Tim_G
Same here. The first hit in Google I think. I started to install it but looked to be bundled with garbage.
@RWKSHJ
Is it OK to delete the esd file after the WIM is copied over? I don't really see a need for both files
It works like a champ in Windows 1703, make sure you are in the same folder as your esd file when you do this process.
@Ozzi6752 yes you can, only after using the WIM and iit has no faults. but for backup purposes, you can keep it around.
Have tried this with an ISO created with Media Creation Tool. Am able to see there's 1 index in the ESD, but the attempt to extract gives error 11 - An attempt was made to load a program with an incorrect format. DISM log shows:
2017-09-21 15:25:38, Warning DISM DISM WIM Provider: PID=7668 [ReadWimHeader:(2268) -> version/header mismatch] C:install.esd (HRESULT=0x8007000B) - CWimManager::WimProviderMsgLogCallback
[7668] [0xc144012e]
2017-09-21 15:25:38, Error DISM DISM WIM Provider: PID=7668 [WIMCreateFile:(415) -> Fail to read WIM header] C:install.esd (HRESULT=0x8007000B) - CWimManager::WimProviderMsgLogCallback
2017-09-21 15:25:38, Error DISM DISM WIM Provider: PID=7668 TID=3960 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:1440 - CWimManager::Export(hr:0x8007000b)
2017-09-21 15:25:38, Error DISM DISM WIM Provider: PID=7668 TID=3960 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:4862 - CWimManager::InternalCmdExport(hr:0x8007000b)
2017-09-21 15:25:38, Error DISM DISM WIM Provider: PID=7668 TID=3960 Error executing command - CWimManager::InternalExecuteCmd(hr:0x8007000b)
2017-09-21 15:25:38, Error DISM DISM WIM Provider: PID=7668 TID=3960 basentsetupopktoolsdismproviderswimproviderdllwimmanager.cpp:2273 - CWimManager::ExecuteCmdLine(hr:0x8007000b)
2017-09-21 15:25:38, Error DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=8007000B
Any ideas?
Thanks!
Electronic Software Download (ESD) file is a file downloaded from Microsoft download application. This file format is usually used by Microsoft for sending upgrades to its Operating System and other software. ESD is encrypted and should be decrypted before we can see its contents. There are a few tools for decrypting ESD file and converting the ESD file to ISO easily.
There is a very popular command-line ESD Decrypter utility for converting ESD to ISO but we will not talk about that utility. Instead, we will discuss about graphically converting ESD to ISO which is easier and safer than the command-line.
Quick Summary
Dism++ is a wonderful tool which gives a graphical user interface to Windows dism utility. Dism is a powerful command-line tool from Microsoft for different Windows operations like adding/removing Windows components, compacting the Operating System, installing/uninstalling Windows updates, backup and restore Windows system etc.
While Dism does it command-line, Dism++ uses a graphical user interface to perform the same tasks. In addition to other useful tasks, Dism++ can also convert ESD files to ISO format. The process is as simple as selecting source ESD file and destination ISO file name. Let’s go through the process in details. To convert EST to ISO, do the following:
Dism++ (3.5 MiB, 7,701 hits)
The conversion process may take some time to complete. After the completion, you will get your desired ISO file on the path you selected in step 6.
Hopefully this will save you from command-line complex operations for converting ESD to ISO. If you encounter any difficulty during the conversion process, please let us know in the comments below and we’ll try to fix things together.