-----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/jalu9uZGunHyUIFAmlVhTUACgkQu9uZGunH
yUIW7w/9E9aKHuDgL9RoAXsvJW52rQCtJOJp11IO6Xta6A+Hk8pnHUz6G8XIK7Ao
tH7nYO3B/oALn2TJ4rZWpK/2JGFhYmzSdEAxIJ1Ta1Qvax2bjFHDYGrhHFmoEVDl
Bfoa6wlHD1uoz58MfZ267sGEPc7K7BiQS0QoohyRD+yUBj6BPHpqf+59oeWd3egY
KbTWvhRZdXiC97b8mL5kCkO0m4Ii0IYSY6efzhqgCmprTSjLrG9tWgXYbwgxvl5f
+vwPruvu+wZggEarCQYCXsgo/UhdbR5zurmJKc0Z1a6vLjaN+VegT2kn7cqjvnw7
TQ6xv4zpepQ8RUuPGAaP2IqKfop1Wq5k8klePfrPP1uw8PCf6NGP7RS3zykzMBCY
Thgthvb98W1x8RA3gz+Y83rXiK82j3dkKbrz2Mcz/scSpDJN5vJQKpkLfK8ZZS3O
SdGBzAwvdfJDI11ZU4DB7aGQ4pSm2lQA2pXRQqVEQaKDTkvsLWY8C3Vqawg77ary
oe+Rgwx3Wub9j7690gaQvmISe8AEM3gsoZiQFZ/hzpolE7MG02HYJe9AcOgsCdHP
lnZvOl3t9JIN/aUFLjwJg/kwk1naIFYlr7pf2uO4dmZ7TOhPnSl5EmjiOFm7ZIIi
3/D2yeTxGwHcDALUPzk9xrFZ/pJ34ERmrzuJKTv3Xw+7vmO4Kkw=
=Bm4G
-----END PGP SIGNATURE-----