-----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/jalu9uZGunHyUIFAmk1hAcACgkQu9uZGunH
yUKSaQ//Y3Y/+P6Bw/OrO0AB5H7mjl0JLvcnvzw7/mNvcgH5u3BBlQuJ/fD0zJd5
cSxYWHkpXl4R6kk8pmxOxy/CBu+wJgikTm2oPOR9p7Hvmto9pmR/G85CqZuMk+C1
Q68Lz2TwaV/TlsLtNs0h4Q8o0txhTC6ijr88g2dnC7cND2FtB8Jrv23B22rlfX9a
oa6j6blg+40FtQBFgxZ5DWrhCD+SIVfSqnhsSf6t4Ls1jZk476ppvKmMwtB1x/rz
1QZC/zEwDWzvCxXW3La2vOnv+NKPSjfQiQNvMZHmpwfPSMqUReMLAQPU6BuP+Wzg
TaEc/2YAbNLBrk4cQVjQdhzzEUNgAOzPe4CZEkMtVPJJdbJuuiZW8ToRKkb2k6Dy
2pwgCdF2a1G1vGOxtH5M688gIm8teoCt0Xg2lBg4nHfa2pZy8vevTy7ws41Y4pX5
0OaZ36eCV7hRBcxvJM7qCatt2fHqIqM8f2+iv07js/Kd0JO5N7QtWWviy6aStDcH
cajzwtOeWi6b6wziCb8XFUwrZjbVwOrBpQruzHm8tNw5QU5Ig0D+pWFZjKn7oM1n
TtXVUnfmzXX0rNyBuqLmj8BR+mUKhIKa3k79BzenXtseo6wza34enGmIm7hTuyuQ
TZAHx48M9KEBwkANdUzT2IQkCSla199npz7CXeDHY2jDPP/kZKs=
=Qy9F
-----END PGP SIGNATURE-----