-----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/jalu9uZGunHyUIFAmk87x0ACgkQu9uZGunH
yUKKuQ//Q4SrB0AGUuWZGmx1ryiEkh7IPsyCGtolN91Q5kWcAKSS3rUwK7JbXjt/
TyHTcsliJ4O5Hmfs6eQ8E7GTkVF+OfXtVNCscaXRIL1k2OrI59xmR/EtcCEA/2WH
8Fhkd6dVFastoNvP/3u00eEOHJ12lQ2TqMYr5L9RRA6uqMX4s2jvi5Ga8GnVEjd7
E3PTP0kgBssv8ezPZpywCBjzd4/jcOL1gZjP8cWhy0e6sg45Zy7WZA8cHenbKTnY
ej3ox+RYAlshEnYiGohqh4JUkpXhnxs5JMcvmtEKUjQINg9UxlQPlzO3UXgnN71j
jVxsgZfWz1ke1B/O5d1TlpGhSOHitS44C6pTWQd96OreaQ8GnIDb9c/ZLThiv6aD
zxZJly4sMAcug6AVP0s4FrYX4JpioaE3ugqsrj4gqd6kzb2TSLwZKxiYeV75Ggvt
P1DykDh6HO1RYbfzYKG62o4gyRuFT6AxpB6xuT/bne0CMwyLXlChBxkWC7nbHqXd
1jH+M/x6VfHE76wh3NpFLFxCls4b2sWigybmSgbCBOID+sFmYwMgwNT9CU2IfZhJ
DMDM/dX7cFbiAzc3r1QoNlELIwm/dj7iM9bXtjn4cdxzThCJpgwzvatx+JMJWsUx
VJmi2OiuDq3mgwH8H+PYNgy0d2GIjrrYjfDiWSTGiGkipiIoj2M=
=0r9Z
-----END PGP SIGNATURE-----