-----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/jalu9uZGunHyUIFAmoJ/qcACgkQu9uZGunH
yUK6VQ//WqgPDthRclMN8Fv2M7LP2ln9VDvOZpF6celu21nFDFBYO39PsTwA25aF
FRMKlwToapZtjtdR6mqs7FeaK9QzV85MDWGVjvLjl/7/gLif2TQE40CkKdYqpGwp
6gI4Xwc7+YoI4uQwM4hM4Zbrsx1e0aqjr8qPRcb5BsqK9tNrv294BMqc25zmuYfu
ORRMIIK4iPWoKoO6I7tYuT3xnauVD+cgO2qfDE2t+O0N1GPGCE0Wsf2EoWp6WH2I
ZJbwQwgdzr8pKHwrCszDxgkym/7VYGwHpEE2xFjADvicMWHah+e70hiRC5RB2RpA
/6NLbn5bR4SbhWnY1BQ6gTwyd+MOpYuhpgu/EZIHN2mp+6GIC5qWEB1Cuz4sPQ9e
3vHFRrfajHcWsWPQTXqWQ14aKYxhMapBS0XeF+ojgFhH8FPNuRdEC29ILqqocsxI
pQq4+r+Q7+rUaxqGJ4yoT+hKx80yf3vi1CAy8K4uhkyP+eKNewM7fDcUeJ8QNvoe
kKqNzMnHzm6vcB++2ptO4uYYQCrE28eX3fzs/geBjkWkfUVYQcGSYU2mOoGuB/k1
aFicUrsGU6KbQNEd7F38OH8cBZBhhet0P9krjakTgsdBwAQ4vt7vZTf8Em1eQsAu
hrCSU4P14XZ7m/oASunSiJ+0FBp3r9lOhKHt6S0Y5IrQsczTZ2k=
=nWyk
-----END PGP SIGNATURE-----