will test again and yes made the link to smaller. ok here some hash dl with the exact same computer, converted on same SSD different partitions big difference. dl with uupdl.se.v2017.09.20.03 File : 16299.15.170928-1534.RS3_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO Size : 3250151424 bytes CRC-32 : E673ED50 MD5 : 73CAD13E2B3A4A5BCDDFA22A614C4E6C SHA1 : 30C91FCCFAFEBF68EA3ED55AEABA0AB158711A31 dl with mini server File : 16299.15.170928-1534.RS3_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO Size : 3641743360 bytes CRC-32 : FC2A906A MD5 : 24605CF52CB99D55737B5C680F4872BA SHA1 : A6BBFBE381BC78EE855FC555213EE7EA738F538B
ISO's created locally will NEVER have the same checksums, only central hosted iso's/esd's will have the same checksums. In the UUP's, the downloaded cab/esd files will have the same checksum, not the iso created of them.
why the diff in size -and for me S1ave77 is faster and smaller and I thought both were suppose to be doing the SAME Thing. oh well live and learn. Thanks
Just downloaded 16299.15 Pro x64 en-US. Installed fine in Hyper-V. Path: E:\Portable_Files\UUPDownloader\MiniServerUUPDownloader
1. uupdl.se is not created by s1ave77. It is unsupported fork with unknown to me changes. I never used it. 2. ISO's created from UUP never will have the same checksums because they will differ with identifier in wim/esd etc. I have created a way to make the same ISO's from the same ESD's that was implemented by abbodi to ESD converted, but implementing it for UUP would be too much hassle. 3. ISO's created by different tools can't be identical because of different implementations of working on the files.
^^Since the JSON is response from WU, they really don't seem to exist ? And it was the chaos release, now i remember.
The problem is that you don't know correct update id. Update id of this JSON yields only ~20 files that are irrelevant.