-----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/jalu9uZGunHyUIFAmoOySIACgkQu9uZGunH
yUKEjBAAsbjnau4JmB3YpI8R4+iui0E5tR8DHJfOZNdMkCpOM9+L8nULGb47278C
lhz64jtCWdwa0dxhBgR2RkLNNfkc+pGVeuJIoT5ChEXi0XpN1ug4kjJczxULeMMQ
wMnk6xLXHQ6BpbULp0OC/0zgb7nx98FAEPcxZ1TWMjocTVMuwmahLfv4WLbl1b3l
q9DvzLaIPZl61/lhfjmZcndLDONkGn80QYC34iaG+P3fGamLGzq6ZP/W5mS2mTtW
HWI+/r5yYKfxPnkWn5AGyeu28ghqQNF9HtgIKnh+4pyIql3ZZcmDjkfGKFAPcdTk
PstXzUNk7Zz/ykuebAw1XR5s3YMmOs0BNUW1mcMUm+LCXysrGisDrMFZ1Iky9D2F
i1ZFEKcoETGUA5nqPcLjVfB9SSXVzE645R4Ud7ckcXhYrd1Vi2KP0cfY64Z6VfKb
fgSUuUO+eYk6bKwGjxDRV8g6thVw8wKMA23zL0MxS5Zv3BJmRJKnq/Pixs5+hNRk
339NORg/JHYIJHlHqIrlMuKjHE8UdMrgiXw14FpudVXTHsw5rzd+cT9AB8yYFtGF
zzNssZ+7Zkb+OSOSWOs2Vuf9P8n8vSZ/DFy5ch2BBqteNKvhuH2H7TSlITGAqKyV
rcrBiUEWQoINF2cOcJRf8RkOvBnzKJtKi0yVgaikSBZnXRk6Bf0=
=Fewy
-----END PGP SIGNATURE-----