-----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/jalu9uZGunHyUIFAmotOKoACgkQu9uZGunH
yUKkYw/9ErNceAzfzcv75/AYtj4iQZ5obQUyzRDjcAP/Bc4zbAjnO/s0FhJwUia+
PW4+Q3zndCLS8g6sPYiTDAEdacQ0Kr/dWE5lIjlevXw6DAcw00W1tFhILNfRHnsK
n1mkcc+6InWG3uevZFel8E8MQdFicJq9v8SBmRK8uqSmiwd56Vxf2SUeJ/xf3PqG
dl71xgbf74QojPUVXQj/cXJZ0mJjtj4jek/eQTO7Bmit7USSYTjM7PdvSibXx0ML
YmlrTIYcg0plGooHvN0vz/2lNa2MS/ojTUFXyRXxsAa2oDWCBWDB/hYivpHUwz9b
4mlWSKn1Fb77A8AlufqzF2BiGxrzQUAY3dMT0Bh/3nfgcQYwd6GvlHidcmfY2o6Z
QaT1aR7kgkCE+uwTL+kaK53XcSxGTwBuyCsRsqbQUqhcbHelIjC01CdRs6CqF3Cq
Most12DeDKlLIfWWCBC1+/pq8r0gNkyePHrkSzHkSmRtFyr1fgOMf93SSmAbkxz1
KSAcZXyo15e3z3YCY3sgf91Xlkxs5R0z1CYRIk6L+bF9Rp+fhcOximoU48wjx/G3
y/cwPnHXYLs3CjCkqtc0su1bfadAwXGvu7KxNfPdTz5gTV3dkkSdWM9jz/Jzu/0F
2Itbi9Fmod+3nuqaeBuZfbpB5WoqLkKNauhGFgsj1YgexUGAb3c=
=0qL3
-----END PGP SIGNATURE-----