-----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/jalu9uZGunHyUIFAmoDa8wACgkQu9uZGunH
yUIQRQ/+JYW6e/ak6lHjAp8vl9nBFym6iTnhNcjDhIpkUQdgmfnxyEHIrJqnMlwl
brYRYUA3tmoKsb8uD0g0REpOvpP0KCCTbMvHL82oKe8f+tu1GdluJmGl/LCER2jd
s7W/bbhkrJu+jHfsF63uddFMZAcZfmI8SVNdrf8IoZ6OG6alaw9OdHxtFvFH2QCh
Wc5Vikqh3m837Lvd6jtnZxpAtlXAwctiY0Y+6JBDJyDBfZ6X2rjQiHDkdfKNDt58
NsVUZfo0dglUmQxci+Y+Obd6WTZjyJr5R1s4kswQU9FJyGZRfp04BdVw+CnXoAg6
gIlfqAB56OHLyaaT6oF/YF4yMny6zSYg1WcyWA/9fTl1UniI+Yo2PNTiHErhwDeG
aovSry8ZU6aakWNMho9lpiupdGvwG8wGwgaS/1vRK4RXREb62WSrTa5SpITokDRR
rtjxyrqPCh5BNYXIroxcuoc0HgrxunjoCTEwygpH8RlaYmzIhlFRFCF9euCJ9AqD
9202l2ratL+sJr7SVg9zFe4xirUCv694LK/T1ujFbMdnQl4ASWIdrg6LgIketmeN
CYwKxn7+QpQgnQAfkt9sLIjJggqhqUedFdZdrEc3VPP2ylqJ336JrVqjw2taZlFS
w6OzrUJORuAqG/6ySSuB1guiXpEA01vGCbHaniKAsNJpXecLda4=
=Hf50
-----END PGP SIGNATURE-----