-----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/jalu9uZGunHyUIFAmmOqzUACgkQu9uZGunH
yUJUQhAAkACQsI4Tt0z5vge6Tz109AS7fG4BnbtDUEZLQ4sKq2d1I7i+VOZZiKkC
4O+YXd2AhgZgDTLYFIm+UFYpEMWh/WGC49lP4zoW4I+Eg6W1vKBtZg2Rerhkzf6Y
FX0XONpwrrpWj3qfWt8o2R58U04Ama/WKgKrlOisoiK9s1FIVY6VHsKodTDhCqFa
eeXZEUB6/UGYi7pIQA9f0kuWGWcBEawHKAJIt4smtmsibmCJjeP16lbSWm2RT3Q3
jaEj8QSMRn9+t3CM0jKCun0e9BQohqRQNtlSGctGOusXkPnX1l05LwMMCY/vNP3Z
6ZQ2xbW82vSDnx1UOBuOXTjizqyS0WZLNpEwhGuRi7sp/c3XzgsW/zr6iVYRH7V2
fya6IL0WMcAyltIE7tRGw9o0LDjzAg0UmhTproEfv5ZnWNQnwSNnTPzcb2A3xxqw
+69HJBVnnYkOUlIENoyipH4x2HCdFIPdNKHGmzma+9l2/j3mW+WRm2F/6NYTwygC
b6KQm7sakGAMfXUT8jxQu90w/698waovzKtf3GfgXR4ipgBMxCyJMebWbEiLO7G0
sHK03z1XPNdQpggu5CZ2pBap2HljCEp0v/eQ13QnX7sw57AL0s8hWkiaieU896H2
tDUApVmK2m7FKOqcdUGzj907TwBfadHM50/pWrWusA31WycIrxk=
=AaP/
-----END PGP SIGNATURE-----