-----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/jalu9uZGunHyUIFAmoGb1YACgkQu9uZGunH
yUJLPRAAo2mF3C9cqGhwa/UbhL099QtQ7rAlSzU01guuwftJVSg92NGmbDba3Wtg
EUjMwOTgQjU4+qW3Gff9LA5GZx32WHLDaz7GRs9SPKrnPZeEaVhqeO+wCEVF/bUm
SkR55FsVr4i934tetIx9HMTGjPLGxf6D36iqQZvxJyONTAc/RQ7+aPvdTdmiSlAb
eNUTkp9mzl46H5SnCauT9nYXZIrt6Ug9Tqyv9ZV3shSFubPTvW1gUj9O9esVgc1N
abdc8DP5d6Y86oKC6VIMxpMxS4enX2dqf1sBmZxED985ZG7atsK9Pj1q55pMXQSC
smImhxIdx2ehNptqRd+/0Vf6DSELN3xtH5+R9FIFmDWDXqHwXce9m38typfFUHqH
UXwNSA8mrqsOjbuULIwXmq6iTcbNOkOiv6QTdNMZ3YA3TDyf//1Uf5/PHE9fAPae
zyniaZEb+cvp/MIj2fkL7vj6PGpWOUIPW3uhgexOZlVO4MvwXb48O8Sx9JefKeYB
XSF8x3/FWX6V72DLoXZPQ9iubkHNdyCqvmeZzn1GWJ70fzIKkbfPCSAT9RGQahyC
Dpidlmo0m/dKnVXHBj/qYMRjHNx5ID19Ii+KEM+7EbOjZlRwjraXLoLVYX7entPr
j24wsL4Y40D8ifBj2frkE2LN6HcsEYeLPQBJRcZHlehdcnOa9LQ=
=DuMq
-----END PGP SIGNATURE-----