-----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/jalu9uZGunHyUIFAmlhtooACgkQu9uZGunH
yUIWaw/+Ls2trAOOE9w3SpnT2P0MmMpUCqg7B8pU4a39ae3GI31DjgkvNV7dnYL7
1AYrDZa0rsniP4sEMAIV0bmrNWoMrsAYIDytiYQbLeevo3FbeArOpGlj5dMUXOuQ
kaL/pthNE1SfS39teujQTPgP6uuJLlu1taxzxIEtqYAL4Be6+zoHOL+fPd07wm6Z
/9fDHz1u7A2PxPE8eg1H+URh+Gwp9fL8K9HRivdQIar2lEoUh00kfsiy6rujc+m0
AnrlyTWiGAj2Q5/t7Kjqg8uczzsH2YRmo8w/4slYZIu3LBHx2xGlErhCMZJVYzli
5VRXALum47+6qhxyBGHw9Jdf8PoDDQrvx1kAcBqJSpbsyVrA6p/QaUsb3taB16z2
tov/qn0RzSoblntFfYfipJz/rZXmCuiBtp3eYdEI7WNLb0Qj0xrsTdoD8muTWoos
POjm3jjW/LG9MddxrjPMA9oEKbYEZIQM5DVzs7uFyj5ktBX+J49U3ctBieuC6tei
5kwvP3bSZl+Mj2Qth4G3alGkHzjbCR/sEK+ZNexm0THtKsz4SIFUYPorgcwLYGdC
Dqmp5AGF1LdWuxgBqVzchV/UF74YzjsPhTcB+oOSxTxslJfO1hr9kMZ4pn7XWaYo
aLjB0SE0QFv4ZT4OjZ8gB3JTd0wauzneWI5VuE5n04G9ntNlgec=
=Rbem
-----END PGP SIGNATURE-----