-----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/jalu9uZGunHyUIFAmoOYgAACgkQu9uZGunH
yUJZoQ//dtDKaVl/8sdCEwlsCBynve06oFcmOSPu92U0VFegRDg4rACTXDJhOeLN
YTIvbDXj1p3Zfh47+LjaJIRw2Hly0CQOG5po4/d8Xe+GPD5ejvCp7GRinvYKkx7p
nl8+xJSS2+y3cN7Qw/d7JUI/jsPnLSHHlwUxCRZrRwsYYxlZWOMJMrQqT3x3E5li
emq0fDXn5PaQWJ5OKrkvxYDLIbbtNEn8KNTnXN/MzF8IauuEnpwFN4qNmHHxvlGu
+b872vYTa0XSTr4mV4HoWi7Vdm/an7iQmBPFqXnafDecSshhti/JK0vHk8hQ2KUF
jHYWHgoMYfSHoexCe2yxVym2O4urKTrBnbK1Etl+B3VZsvPwPVvYTiR3Pp4AWjl5
BuJ9HNXCRSF6sqyNwTzPZZimuuBAd0dgY9eaphgZX/1LXQqzOuVpJSGTPM8JEgS5
p/FJIu2GezXZyKyPHeQy4v1JBO2JCYoilxcJZ72nTSvRuhkI0sLRTEOSlw/88fje
vBR0j9E7tldPNaYqWSsYgAX6kbA71T+PfJ3QqFt+o0bDjilxD16qjHwdKGQtagnn
2nsnnPRmAd/bxRRnC/EPh0Ba9HK8aXVPQTSixYUwlfA4FCzzcCtB7pjCUbis0zzp
2BrHIgkNKgFweEhcE/pvXEaDQsm+NUFm2I/FK9nNSe64/VPuLAM=
=6qQS
-----END PGP SIGNATURE-----