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

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmrZ9lsACgkQu9uZGunH
yUKLow/7BVFfwwFAqHlqY/ejatUJxhei1GsliACsD6h70paI+OWawVHDci5Cpnet
aEGYC2SrYyxUVQyHHvnw0N6vz7tLGl+zxRJboFf5jd+sYx3HWfBN5VFmcX+vngY/
i2lIcyjsxgap5woBpGclEIuIjY6jPHT7KIWKEtYprmNjd/B8lsze9g094zSnEtLe
ItJksVlP738rZ4Iv6el90F9meTROycrSSdvigH4pbgoFD/BQ2Uog3Lc1fA1DUTme
icmcmt8sBhu8iJGNt3ovyCI3zHQGYsZTpQwP1FxMSCHhuAnnu7JsS2TG0SvYTP4L
KhyoFVn34+f5LwuQgRmb4fQhfJVOY0YG1pUIMKXZX2qt9QKlh5Cy4rZuwgwTVfd6
NQAOjo+Vno4+bDPV5ZN9uZRLB7evnmklfnCyQPYQvXH0whhDcbHP9YiFh6i52I77
rZrjSeHpMzWUKYwsHDS4ZnKidO6zu+MwO3lrZg7r2jhyyL5exePHOuorK3D6Hl8u
zyhUgTAVBGwrfbIluUXtg+UYqQxQcy3tSf2eaSHP2nmK7H26d0HFnaERS1y6AP9Z
L+RkNksytloOGmdoCx4qlraQggRkXFjtiW1+IFrxiSfaO6DRlkwVvGOXA7AyJ2LP
lgVdKAE1P6e8KYXjnvlkwXnCpdKsuhnfY5sg/xwOc5fsSMNXVUE=
=tBR3
-----END PGP SIGNATURE-----