Windows 10: Checksum values(SHA1) fo WIN 10 Home x64 ISO download from MS

The ISO file may be constantly changing, but it is not being constantly updated. You can tell which version of the ISO file MCT is going to download before it downloads it. Run the MCT. Just after accepting the EULA, look in C:\$Windows.~WS\Sources and open/edit the products.xml file there. Inside the products.xml file you will find the references to the esd files that MCT is going to download to create the ISO file from. For example:

Code: <File id="375320"> <FileName>15063.0.170317-1834.rs2_release_CLIENTCombinedN_RET_x64fre_en-us.esd</FileName> <LanguageCode>en-us</LanguageCode> <Language>English</Language> <Edition>ProfessionalN</Edition> <Architecture>x64</Architecture> <Size>2861869874</Size> <Sha1>e162b8d78194d8fb9cd47180b9574292d559af5a</Sha1> <FilePath>http://fg.ds.b1.download.windowsupd..._e162b8d78194d8fb9cd47180b9574292d559af5a.esd</FilePath> <Key>BwIAAACkAABSU0EyAAQAAAEAAQCBK154a48ca1NUi4rwPvAb25g7qltZ0xm5HYKYLYA7AWrSEsmGduL1lgbH0GB0hLVp3qK3U6XBpudvCLTkcozadaKisCLDvCuAboPRgpkBjQ0g9jqU1bECrRgESQo+zypLSBtgL1vVsgHncefceZjxirjM6IeYV1Vul2St0BOcvDFQqnFLfFwehCUUs1GUQhNVOJeYUVGkEQxpvMCrO6jWzOvvFiieN6zB0ygCCsnLsk2Ns4JXe4SnsmgGf7tw+f5RjKBv7Hk3wyblOm0vzPnh6K77KhAiOcvO30cxEMHyK/kYOj8I1vHndjlqhvyD3e8qplpjQUVXe0DKYx1NTF69UdRqRv7gLwfvmE6hmJaTbe+N0DoC8Ie27WYBUiZfJSypbL282a9Vu4lNplTox6dfzf5hdE1KLiDptpCm+5rGTeEIQNIjYj7Ju0lmdDg5YobuCduao2ZsxVhrSfg0mBcsUa69uSL2mLtorZDoSS0ZEyoGudDapHiT7zd+HBQiUZaE1H90V/Zfjmmt/sbpXd+kDWs2+cRjCVRvSpqD8OSvSVO2ECR0QzLF4LpssF5G5exCs+ABvH5UMgu74rAGHPbqgSURURvxltzrVIFe1JZcv4YZwsGgi7JaKMdzF5EsLKhiLmqU0++tA5gKNFC4TwuUCP7X5eFDv7FTKWf3fmtKTE05sakAuAgTm1IPBZ5B5UtWctUwfLknsj4JlO4WQMd+sBg/NaQP9jRberZFyg0RRTXxJVRx+aBDaJdh66hF/gU=</Key> <Architecture_Loc>%ARCH_64%</Architecture_Loc> <Edition_Loc>%CLIENT_N%</Edition_Loc> <IsRetailOnly>False</IsRetailOnly> </File>[/quote] This is from the MCT I just downloaded a couple of minutes ago. It is going to download build 15063.0 dated March 17, 2017. When the MCT creates the ISO file from the esd file, some of the other files in the ISO will get a current created on or modified date. That is why the checksums on the ISO files change constantly.

 

Thanks for the insight, info, etc. Good to know how the check the build of the download beforehand. I knew how to check this after the download but not before.

 

@gcwizard
Did you manage to find a reliable way to validate checksums in win 10?

I am in the same situation to you.

So far the best way seems to download the ISO(not media creation tool) direct from microsoft (via emulating a non WIN OS and visiting microsoft dl page) however still there are not checksums available.

 

Since the last post before this was back in May it's hard to tell if there was a solution or if it was not needed. I do the stand-alone/offline installer of the updates and even though they may stall and have to be resumed I've never had a bad/corrupted download.