-----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/jalu9uZGunHyUIFAmkyKAEACgkQu9uZGunH
yUJtHg/8Cglssr+2thqHDgJbE4ZMeLwaqNrxcpxPzTDOtblMwgxYZwhc5tAD6qMD
GefGEZltE7PQNfndersoswksSAZgVgNCmXCHF2WbA+Rjij2WeSP5Uc6H0A2k3WL4
RI0CoEikkEPgQOjs2otcdS/3/NsQTI+itD8UMusoBGYZQyy8Tm71vmKnLP7wurwM
MPxsJrqjnC6m3aJp48Nhc5EaI16CdN6kzuU8GKMLV3ksMQqbjMgSgOVJscx8wwX1
ak0hD6njgxZLa0f1XJqTOfkK68oNojOir6Bj/LIQ1BTzD/d5veuTJnL3vf9Dzm/9
gp84pams/sF6+VQAfzLcWOn7zNTc8s3HE+oGYHD/ZgmiYojT4KDm4JLt1H75/szt
X3jMVUk9z9Iivo5LESj6MUcTHAsr9vo4r93NMo0LYCF2Yq0lfySdmxCdyBPTPwzO
2b9UkFyxhonvU3XQTDU/55iWspgBtUGJwSvQ3pGbPvjfacjSrVd9bkzkHk0EUFnh
ZjaB5eX3lyMV90Ms26PyoZ2GAXY2GtcmTpUUIksjYZFFtgwJU+AVaccKYbcDeaAQ
77PZ5KjL70OwqiBqgvup6nrda4uZgUqQT9i8xYmtQKcw6jQY/SVR9mizBqNfhBYq
mQdv1rVfAqD+0E728NsFLqdeHMwyYhSMsOciSII2fqeFNKYI6cY=
=tb8h
-----END PGP SIGNATURE-----