-----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/jalu9uZGunHyUIFAmniZekACgkQu9uZGunH
yUICQQ//agvAVyg1t5TzbbSqCyLoOteRu+lRc7OtxupAzt4uX35qcWKZR02D9YSp
DOt/SaArw/RCLkTpiUmPZ8AJLL6gXTv9ozHvS8XbTqEbwtmP0FLKLB/PnYY2J7gW
OtgUfsjk8EQbVXIdeyuYEwYYiQu1u4mYv9mvLX0PhJx4XXaxsoUhf7wzfkmXraR3
JihuTMA8w5rnRqxYslZCpKwYaKOKObuZqGH0qAoHE+8K+4XiZ8HLaH6PnCxnhAxb
0zF/rsAaw0fT+hne1YmM+1aEQF6tbmtZoblSF+RpSsdsM/v/uFFZUOqWpLlCnzhM
IyBz0th6IoB18gBMfN1QNQXo+wujTQFCwsKdEzq7u3ZQbxyq4EXi/8XYACQQXk0q
VdHM1qPD5WyTxv4Xxw34lCvY2PsYn2fzq/396J/8lOx/DU8C3GzQBUc6sRJyNJw4
VJnlLsrV6mQsHZtFFVeectbmtzQSti2At6o3NZLkTCw3TRmqDmW0o8iAI+tIMLqE
j1nbLJU6aOE2BByrj5CamcPimdIIpdoqj1PTrfVD1CzHxbyy3FaH3TbQIrP2qFeC
PDmlLMFkgjdw2f4MyUyuI++LY+Dsn2Dr/44U9F9L9ENPkYFdg+JJcS0fKxYyHIzu
yQxmtqPBocP8UBIuC22ggVj1VLOZxrakM9kwXg8xzun81Fhpuuk=
=SeBS
-----END PGP SIGNATURE-----