-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
2e528092dd8428d62ac5dfa69a46be7c
sha1:
71d7487b62373fd107d633b50b31743419eea92e
sha256:
b8cc442963f5abf7452d95aa0ac9e703024302110e14c90fb788fa0be33ce5bd
sha512:
731ba4c53953c73a727bcd636e18aac4eb8908d16a6258867bbba6179f82a1d45c942e70b61cfa01948776f95871a9b3c34a7c3d5fdf1d8df6261d77dfed7806

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/jalu9uZGunHyUIFAmpi0EMACgkQu9uZGunH
yULNeQ//akKEJ4O5dcShBRAoVoNeniVmoXr1KQrfs4WTs1Lk3IZm0zFT7ax+OuX2
JngPvliol+mXHQhWdKidx+74jN9R/aD2HfnrEY1rqa5WXgLIUN+TO1Jxpq5lBM5k
ZkwZtxswEc9N07IGTieddxZGPRFdKXRiQZhZ2o//CRpK47QiBvWKUiZz32xck8YB
XaBOWK4Msrj/1XSXo/xYlFSIMJ8AWUWobBgP/j5HRquMVrZamYTE5HKiMm/4t7G0
p1wdtTV8ujfvqgwSAeybsz+ZxkxhAYCYL/wpFJwD0DEUFz5VYiqolaY7WCoX9ent
boJozI2cYOGuM0s5G0YrQOtbrRpDD553uoLMasa5yCDwMj0m7JkbtcF+RFTwT3kT
9UXgO0RMQ3D1u7gJehrwT7YXrPulZSyb5YYC+JmcYiOtnA/CTWYNpq8sy+EMcOmA
+aPcyJhnTQi4k5sbwPTEMWF8iFYrFMPXTltEGs2M2Xz/pFcH5d5EUBX1iGLPelk+
IyHDk25+ATQab+CUjk8TWLATz+cDvIHYaylr78t/ApdZVVL6oBC2+SD63lFz0egm
PgJfFpuY+1oPho3ZlByWR0b0Xd4JfGV12VsTLc1FawUndOwaY196/iUMGyIRp+WK
+DOdoLi707xeBAwFLnL00XtLboFOvu/gDgoAof8zUPMGvBNEoQk=
=KAX1
-----END PGP SIGNATURE-----