-----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/jalu9uZGunHyUIFAmmBHeMACgkQu9uZGunH
yUK7ahAAs2gBiiDNITojgKiqgt1YwPy/JVVHbGL3fDhNoiq5TtUMNYbc3aFbTrhQ
xbR/o+iTaSKMMyJVNN7C1I7ESDsV2B+lFfeqdFw4+Y9d75iw3/iLo3BC1bZ2F4Y2
AK035c1/m6NSpJWg2OjoNJhPEuyiuBspXnr4xfGfRJkl64A1/8qe6HuwgMiOF/R/
5E2Hk7C5dVAB02uoszhy0MRg65sWuYqNNevjx6nc91IpVjbpMBEn8EqB9Z4D7PlE
3JLuRr6bzev+cejLpTYkKsgR+88K+0E6JDhgLvqX/Ak/ZATNsEwSnMssrlWa0T1Z
y7YG62+/V0HKFqa1bdkR654GC+3leTwa0yUSjMEUSo3H9Wvi6Ba+RSwW9/EI2SV/
mZxzZMc8YPKt6xqEANSvuSRc2OwmWbnchak8wTLn0cTKZdhR6k4Vn6BDnc8wYVxY
OemuamMcEPDkcYSGfEiUFKIaaiTjCSLKffg3Wq6tR5zP6szo1gWg5Ksijemu5k2q
K/rFLtSPoi3cg/hXZG76i0+NOcHjiv7H6Tzo0DfMeo6dgPLVzmIpbpo4PKu+3+v9
40kP0iYqcEZOK0r2Sht1ykEcrc8iwqYG0ITQhp4447AY5mfgtP+REYLLqW45fYmT
n5yyC6zXtvSv7+EuvRd4c7WjzFrChRPRJXQes6nbZK4bjOSgjZc=
=0ube
-----END PGP SIGNATURE-----