-----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/jalu9uZGunHyUIFAmn7E74ACgkQu9uZGunH
yUKVWBAAp+RRGk6m0anEtImt6ePicAxHfYuAZCl//dAtiOZtRoSRlTM111zcmZTQ
Ulm6/fCJ6Ndd0LVFZLhNf0TEUeknUKbAaQmOzwi75GxKDciFgluvb2ljH8Xiy+RY
wwAoA/7J7IJ0qMlRvHWJRxLQnJ32+BuPOZi6mijYDL9niLhsFRW0FP41r251yHPv
LBKBRYMH1sPQ2/3JdaRzZtLDPqpJuBLBMzSdWexkPjZVS4mmqNqM+rFEwYoLWQxJ
E96/AIkpLwv7YYvkaCeTY75jk9BiVhqkvBftj8NdKcTYKL6qxKHuGTE+/SwF+ugZ
BBWUU/KvpRSzSu9AidqcgFxfIx9zkn4mjI1JVp7JTFPSPDic1jocK8tdNMOQj6oP
cYHfJskVGp2yw/nW6a9o9rZ26CxbosxxtQRrAS+ix26My7TYyHjIlBJApuWmdh04
et2Bdro0KOWkz/AugLkTx2v6+QyK+wSo6i4L9oGAhAQDSa84xi7gJnaku2jgBths
p6M7ECj7c6ArJ1m/vaCKhPlJMSFyS2+YRSPN5FmUbKGhLJxipYnwsayL41rExain
n3DCxbZKOV9zTM1fWT2YpGaTXwMR3IMfiD8xPmm6pjfp0bH7ezsL1PkgnW50YnEP
Q40KmoZGQIqWz/6Rhs+eImDiT5+AW4DIIYOKpoGzrrZf4hSTL4o=
=wRc+
-----END PGP SIGNATURE-----