Thanks for solving my problem. I have exported everything, compared everything and winre.wim from \Windows\System32\Recovery of install.wim is the best solution as source for boot.wim for my image. Also WinPE index 2 could be used, but it lacks some recovery tools. Index 3 WinSE (setup) can't be used on ARM's DeviceEncrypted drives. Index 1 is irrelevant. Great. Thanks to s1ave77 for describing index 1 "Windows Setup Media", it spared my time. I have used abbodi1406's solution posted earlier: Extraction of index 1: Code: mkdir temp dism /Capture-Image /ImageFile:install.wim /CaptureDir:.\temp /Name:container /Compress:max /CheckIntegrity rmdir /s /q temp dism /Export-Image /SourceImageFile:install.esd /SourceIndex:1 /DestinationImageFile:install.wim /compress:recovery /CheckIntegrity dism /Delete-Image /ImageFile:install.wim /Index:1 /CheckIntegrity Note: For index 4 (for example) change code to /SourceIndex:4 on line 4 but leave intact /Index:1 code on line 5. I will try the script next time. esd-decrypter-v4f IMHO should have an option for selecting index to extract to common.wim (not auto-select index 4 to install.wim). I don't know, how it selects the indexes for ISO's boot.wim, so I didn't tried that.
Hmm, index 1 should be simply applied, in case one wants to image the setup with oscdimg to ISO . No need to export it. Wimlib-imagex is capable of converting ESD to WIM directly . You could try WU TOOL from my sig likewise. It offers the wimlib conversion in '[W] WINDOWS IMAGING MENU' .
The script was ment for one particular purpose: Convert ESD to ISO extracting only install.wim/.esd is just an extra bonus s1ave77 already told you: Index 2 and 3 are the indices of boot.wim (in same order). of course that's for the regular x86/x64 distributions
do you think it's worth it to change the produced iso file name to be similar to MSDN schema? i mean like this: Code: en_windows_8.1_with_update_x86_dvd.iso en_windows_8.1_n_with_update2_x86_dvd.iso ar_windows_8.1_sl_with_update_x86_dvd.iso cn_windows_8.1_china_with_update3_x64_dvd.iso de_windows_8.1_pro_with_update3_x64_dvd.iso en_windows_8.1_pro_n_with_update4_x86_dvd.iso tw_windows_8.1_pro_wmc_with_update3_x64_dvd.iso the number next to update is to distinguish builds and for Win 10 TP: Code: en_windows_10_pro_9879_x64_dvd.iso pt_windows_10_enterprise_9909_x86_dvd.iso
Yep I like your idea abbodi1406, pretty handy. Hopefully the red number four is just an example afaik that major roll-up doesn't exists
Better to use the Microsoft numbering, since no-one is sure whether Nov rollup is Update 2 or 3, let’s just call it R5
Agreed. For a moment I forgot this is about ESD files so the more convenient way is to use M$ versioning scheme, IR5 will be just fine.
2015/01/New ESD download(Example) 2015/01/9600.17053.winblue_refresh.141120-0031_x64fre_client_corecountryspecific_zh-cn-ir5_ccha_x64frer_zh-cn_esd_c5a93370a8f9f3c0ab67c170abfbb5381d0b0119.esd 2015/01/9600.17053.winblue_refresh.141120-0031_x64fre_client_coresinglelanguage_zh-cn-ir5_csla_x64frer_zh-cn_esd_de98a3847f3091467fd8a5a35525dc16890d5592.esd 2015/01/9600.17053.winblue_refresh.141120-0031_x64fre_client_professional_zh-cn-ir5_cpra_x64frer_zh-cn_esd_83270db5871fdc588540e3010e044b08f614af03.esd 2015/01/9600.17053.winblue_refresh.141120-0031_x64fre_client_professionalwmc_zh-cn-ir5_cpwmca_x64frer_zh-cn_esd_c781862fc3e93f25558a59952f08a30f7b6c53cb.esd