-----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/jalu9uZGunHyUIFAmngTJ4ACgkQu9uZGunH
yUI5eQ/+IY/pUMbGHXYTJLvSSXiW5yUzL7UyoBbNkOmRz0bnMwiaZca6lq/jBGDZ
ElvmK9PPZjwzZfxfhh80LdIlyjVPl6Sy6IbPvIKKsWh5j7txFmuGV0CUY/Ffwd9P
gtqV5KzlKqzSPzL40fMvAYRpqGlawB0dc0dE/7D3F86vx5XsPHZirGYI/cf/cy1+
eVXtVUlUUpBO9MTQchc3Wva+nwmNGM9jaUiCskJFWwPkZ8gKyxGuW+5gyw2P8Txl
MragxL/iZGg7jw86oPaV/xF6u9Ccm2pMBIAvi0yeJbQX8jnocVgDUax6+XR2xqZG
EkkN6u4DMrTkUYnMPG43t9OKPp761TTAYdF8JNFyZet3wc1iVVHwCOWO2Gm7IZmq
iYtg/LV6NvkJZFSHAZD/GnbjCAcg8Mrd6PARgQSwsyNErHd1RWVxyCyGx6LS1Grm
2b9Vc9axwTKgQJdKuYtQ6tlOQSdKk6It9zepmfLLFRtIluVQBKWnMgczNvsnxqZk
N6wXBYf7EqcmhjknqCjlKALZl5dUZFgaxv1AQX2EpdHEJMDZr21Eb90y/TC8UXVj
eGv0eW2v4DqsWFR6QhLhZN1/xKnY+lrSZV6ppfyAJM6/03boIrQBAN215TX06jWK
mtWwTZJJHuY3+P9QlS/0mnlGmjCJBSm5SQiS9FS37GZeSDz4938=
=0UGR
-----END PGP SIGNATURE-----