Very odd, the link I had from that MVS repo page that I subbed using the trick was a few hundred megs larger than the direct MS link. This is going to require a VM investigation. Edit: NM I made a mistake. I only changed the filename instead of the CID
Good old murphy, you only changed the filename, not the CID. Please remove the link as the file is completely different to what it's supposed to be.
just used the link you posted this is what i got Code: Name: en-us_windows_10_enterprise_ltsc_2021_x64_dvd_d289cf96.iso Size: 4899461120 bytes (4672 MiB) SHA1: 2FB2897373C4F71B06F4490943B3D564B0F0FD6D SHA256: C90A6DF8997BF49E56B9673982F3E80745058723A707AEF8F22998AE6479597D
Please do tell us how you would prove an API response to be authoritative. Do you want us to capture the whole TLS session just to prove no one (from the at least 5 sources you can find the exact same hash) just sits here 24/7 and, well even then f**king what, comes up with hashes? Infects the ISO in a few minutes after release just to put its hash on MDL? Other than mocking the impossibility of that is there any conceivable way we could "prove" the response? Even if we did, what if we just casually broke symmetric-key algorithms and they're still invalid?
Well I think that's the correct file and hash, but that's definitely not what it downloaded for me. It's a mystery. Still people are better off using the direct MS link so I've fixed all my posts to omit the original errant link.