I know you can check the hash for an individual ESD file but can anyone confirm whether an ISO created from an ESD file will match any official MS hashes?
No, it won't, the iso is created locally so, it will never match any checksum. The checksum of the .esd is the reference.
After the uup-converter-wimlib-11 conversion of 16215, the new installation will see two error tips。should I back to uup-converter-wimlib-10?
I have installed 16215 10-15 times and i've seen it at the first one or 2 installs (win installed just fine after clicking OK), and once when i installed VMTools, now i've done 10 more installs, i never saw it again.
Only for insider releases they use UUP only, for normal official releases there will always be full esd's,
That's the actual WIM/ESD file version (reported by imagex), regardless the inner OS version fixing...
esd-decrypter-wimlib-29 - Fixed label for the new 15063 refresh ESD - Implemented busybox method to create identical ISO/WIM files from the same ESD (thnks @mkuba50)
Code: ============================================================ Backing up encrypted esd file... ============================================================ ============================================================ Running Decryption program... ============================================================ Done ============================================================ Checking ESD Info... ============================================================ ============================================================ Creating Setup Media Layout... ============================================================ ============================================================ Creating boot.wim... ============================================================ Using LZX compression with 8 threads Archiving file data: 726 MiB of 726 MiB (100%) done Using LZX compression with 8 threads Archiving file data: 117 MiB of 117 MiB (100%) done ============================================================ Creating install.esd... ============================================================ Using LZMS compression with 1 thread Archiving file data: 7917 MiB of 7917 MiB (100%) done Using LZMS compression with 1 thread Archiving file data: 895 MiB of 895 MiB (100%) done Using LZMS compression with 1 thread Archiving file data: 831 MiB of 831 MiB (100%) done Using LZMS compression with 1 thread Archiving file data: 826 MiB of 826 MiB (100%) done ============================================================ Creating ISO... ============================================================ CDIMAGE 2.53m CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2007. All rights reserved. For Microsoft internal use only. Scanning source tree (1500 files in 54 directories) Scanning source tree complete (1712 files in 99 directories) Computing directory information complete Image file is 5529010176 bytes (before optimization) Writing 1712 files in 99 directories to 15063.0.170607-1447.RS2_RELEASE_SVC_REFRESH_CLIENTCOMBINEDSL_OEMRET_X64FRE_EN-US.ISO 100% complete Storage optimization saved 18 files, 133120 bytes (0% of image) After optimization, image file is 5532596224 bytes Space saved because of embedding, sparseness or optimization = 133120 Done. Press any key to exit.
Is it possible to add an option to make an ISO with the splitted install.wim to fit easily into FAT32 fs?
The winre.wim from Pro is different then the Home one inside the muliple editions iso. Pro: 433 MB (454,324,224 bytes) Home: 433 MB (454,361,088 bytes) So, they will add up and increase the size of the install.wim. Original install.wim: 4.39 GB (4,723,125,802 bytes) Modified install.wim*: 3.97 GB (4,268,822,978 bytes) *)Modification = same winre.wim in both indexes. Compressed to install.esd: 3.01 GB (3,235,377,152 bytes) Split wim (install.swm): 3.97 GB (4,265,861,774 bytes)
At the winre.wim file - the amount different, and the volume of so huge ESD. But I am not sure, within an hour I will check.