-----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/jalu9uZGunHyUIFAmm9L4EACgkQu9uZGunH
yULISQ/6A+HQH6/9fd33HXy7u6kxp5eLW74A4V94eoJaOQKsAwsga8EDZkeC65wE
FHZrbIVBrSvfwvYdnOIxYNrt1TDv8HWkkI1LNaxOUEmkWlpO/9km22aJt8I1F9Sh
4y5f6CY2i09XwrOhE8JOo3bJSwuq9c5La3S70XLtbYugT7D/VxgadSOgMFHjkSAd
uNGqPSDIrUqPLTwOhw38X/DprrGqnQsPxVwMrBPphph/PyiTo9QZoiFj7o9eTOgn
kaqe6cqkkZ/BEdOfdTeV5gv2KOtDUIQaAW2mg891QH5wS4iolgtlYvgAOXrljzhO
qVCshNGHEZXjcWChvigGt1KlrMRzAhjsB73fehusKJ2MMOnhP8cP6GrsV/R3X0z6
4ZMqvTiloLwTVGVXEbyY97usl+YCOTaIuFYywoZCz9f00ryfme9i3PfIiSH+ldgv
P0G2dkt9olkjJGoNaWN2uMN6TB2Ia1+bTkNrdNS8aAUEpGVzWaa3zKZMfzk/kfoJ
om1hOexa9SCXuwxJvltSNKOh1+qQNLZCP8HLa7VH0bvDlwpmmDnwnDa0ylp1HFzE
PdOSSofOcMVy+c4PxRsZXY99Z0yfVC4ophJEqTeZrkDLEpy5K4XEi/nHSKwiYqWH
QlVlqOZUnIrTMDUu00gcK0Cqw7w9kB/sNqKVxrEhB2ROTT7hNxU=
=VfBw
-----END PGP SIGNATURE-----