-----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/jalu9uZGunHyUIFAmoPJ0wACgkQu9uZGunH
yULYiw//Ur/JCkuOoj5l2MYyjZHUIwyFSN/YxH41mqVVUGCwpv8+VAlRyw0QHwZ6
fkw/OFgaVesB5Kvjalv99a3sllI3xaVy+PGTCGA9ioiIxfV5KusbJ1ZkhQ6HRrpk
5jcv9qPOTtHdC5+7QGNQdmdQYwoY214T5NDoTRXuDHqh16cjEFDUKVI/Dml5QYni
fKu5H3UzllAzbKFRaimvxfRulIwYFxdVmxNk1uljpA1FHOmzMxub7X60FaW5+JT1
evsuIqWbel2PYaN2TqUlQsiDvOpr8RTcxscigmPeSzpJowUTngXaZ284H4jiYvyk
XL9T0IC/VV5Ot/4jgEn3vWWNDFieUOBDm6NIVGsM24byNjl7cvXzI3ZSahz/saOS
R743zuOmRyoqCKjeONe5XSOvtEDYZUSi5dtLqAqofY6AigCQ9HNBfwvlpuDWaxXU
c9VzGBOC+b2tkCsvda/aUH09rgkmLXNbmEbcx6TJ8+rvayMKQue/bDGZhD9JMyE7
f0XizOHTN0YO5sEp1Jn0XAC7tlWb+Fd0k4muLpTJPwQZShrRZ+vj/3NzPO+F6MqR
a5NvBaG5ExwYZ2ZglS5byW/azxH5IfQpxCTxNxvo6a0ceTRYNTNJG9RbL8kY8n+v
17fXQGnSkQrrhFKJR/ImKFDYnYannl8WqZ0KHfsrM03QHY6nY8Y=
=K/Ty
-----END PGP SIGNATURE-----