en_windows_10_multiple_editions_version_1511_updated_apr_2016_x64_dvd_8705583.iso to en_windows_10_multiple_editions_version_1607_updated_jul_2016_x64_dvd_9058187.iso
A version 1511-TO-version 1607 SVF will be more than 2 GB in size! Better download version 1607 directly. On the other hand, creating a 64-bit to 32-bit SVF (for example 64-bit version 1607-TO-32-bit version 1607) will be more effective in saving bandwidth as it would be under 1 GB in size. However a 64-bit-TO-32-bit SVF for the version 1607 ISO is yet to be created. Probably because hardly anyone uses 32-bit win 10.
hmm he can not read he does not understand pictures damn, what he wants with win10 EDIT: @EFA11 'Visually seeing this sometimes helps' - obviously not we waiting for a better visualization (the continuation must be more simple)
Out of curiosity I created a 32bit to 64bit SVF (smaller to bigger ISO) and the result is 1.90GB. Still about half the size of a 7zipped 64bit ISO
I tried to create a 64_to_32.svf, somehow after more than 1 day on a C2D with 4GB, it was still creating the sfv Ctrl+C! So, using the ones available on the link above and 7z for the ISOs: 64.iso.7z + 64_to_32.svf = 3898.857MB + 890.4MB = 4789.257MB = 4,677GB 32.iso.7z + 32_to_64.svf = 2971.357MB + 1.91GB(1955.84MB?) = 4927,197MB = 4.8117GB A whooping 137.94MB difference! All joking aside, I prefer using 64.iso.7z (3.80GB) as source and sfv.7z for all the other ISOs (plus 5% PAR just in case), instead of keeping both 64.iso.7z and 32.iso.7z (6.71GB) as sources. It might not seem much, but in 5 Windows 10 releases it saves more than 5GB, which might seem meaningless in the TB age, but for me is useful for other stuff.
Could anyone please create SVF? from en_windows_10_multiple_editions_version_1511_x64_dvd_7223712.iso to en_windows_10_multiple_editions_version_1607_updated_jul_2016_x64_dvd_9058187.iso Thank you.