-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

Use https://www.quickhash-gui.org/ to verify file integrity hashes in Windows
or you can use the built-in certutil command as described on https://cryptostorm.is/windows

If you're concerned about us using weak algorithms here like md5 and sha1, there's no way to collide md5 and sha1 at the same time.
I.e., you could do a collision with just md5, but that would change the sha1, or vice versa.
That's why you should be checking all 4 hashes, or at least the sha256/512 ones. The md5/sha1 sums are more for CRC than security.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETYf5hKIig5JX/jalu9uZGunHyUIFAmmfWmYACgkQu9uZGunH
yULPaxAApxiUiuyeWTKNDEqzKw9NKlW7pGSz6jAuM1rgiVNltSGrHJOxr0le2QX5
T4zLao6ckBnVts+rRCEnckxlmmXmmjDW4AwRpL/Jwnb6AWi0PANwsLJ9DfVBtIfz
SR0S0u3TAWRnIxgjX5hLtjQkpHGt1e3IjDL0y5S49w74RphTnT1/GfglVh7t81xX
2oenRVQj03od5CW7X16aMoZwKoe2kE26+fYA/W6S26CAr0khHrJgEJk7y1Row5Jq
0pqepecuvUwmw4LA5OwLmpghkeaz9QCTjpFbjTuYcYKW2iyrW1HmviBjymUY59xr
ZZfQOTz87akgvwSxnM3QHolLzlWFD0EzxgIxtHoEKIHeUnZNfBiB+owhpNS7cKRO
Uc5v2nagF2UbdJ/2kig7icBghi9KAn9cbG3NWfXmxil3C19SCMqs7VGWGsb9bDhB
pVMpSl2MbNloi6EZDog+KZIFRiZjQq6C/KEgSi+ZiD3TF6AzDSAtrhvvc7ha1EZY
6BnTg3PC/srEMtY6jnrED+c/HSSeZx+JWlWdhtQYRQjUCsZ3Za5eWyl/0qxAS1Wm
mVhun6pZWkNBxqUk9rwJ9E9RyIwj15eDQfbTFxg1vE112F1lEdAfWzBdfhT47Sld
+XpiWSl/lhGs8mSaT86oPksIlT/XMd59luY0JgH+t4hXeexdg+s=
=dLAV
-----END PGP SIGNATURE-----