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

md5:
d71db59e76e908f2810b6dcf9b742ca1
sha1:
3713c76a9a230d30d2d28ccc0e1c164eb73916ca
sha256:
363f5edef02500bb9faf5a557bb5b77c463e3b7f11fcee283ff4d0614d1e88d8
sha512:
9b2ced771ecae2175569d0a6cfd02278ddd1d1d2398e48a5d9de31b7a66cbaf831ed8652cc101a1cff46a9176ffe9b835fc728fe1484a1e7c853ca2c4d9d813d

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/jalu9uZGunHyUIFAmq3TSwACgkQu9uZGunH
yULsGA/+JGGNFLcQr89bsBeAOFMCuP4bbkW+jwizMzn8Eh5vxUy6lXnaye4vYBCt
eGsU+6ekYnw0DXlm2u9wseeil8OMM0YMd+OzrcLRvxmo6S5PLPqpw/sXgApFdz88
LjXqJ02PA1k3r37f22NyvUgshUk8n35vRy8EYvv19AzuIFLhMP74Ik5w1kOlewwo
BxXJhV55rvm+2PNq+GO0+7bOfQkvsar3wRFBl7kCfIJZGrsF5bgNVzukZ2nmFiPT
Z22+f6M+eons0hwNKkb6mBZ9ZihJuC+wU9zHXy8SQu+el7NGqb9alQD4Rw7yQOwc
IGRxLtcbLLdWbxtZ5xyS+dMJ7OGhEBzovQWffWSgzCGZEnRTOsFFg9jNF75iuvh5
x3Cys08TCRxFpkH2mZJ+u+r3HorMdhLF3C9LyQHw+4RnXC9ouiGZ+KWl3otXsiNn
9LQn7GY2v1SWAYnCKo7J93to9IJjLwAFeG2ftzopQS6aNv7wzITlCTH2ovmLTNiO
Sv3jt0KoXYpon1V1VpLH6D1o+xC0q54Z8zanL5cLB+L4qT//MsAlmgadakoh/ceJ
D2b8uv/vKKV03sRwHM0CFKGOhy3dZaxVyLxBYJIRX++TsWN1CORg8p7q8BseRboM
z39EKMwQilNXAk3IkGxA9v9jt7xeS87lMCI9fF/20YCDQ5EDeb4=
=zHGU
-----END PGP SIGNATURE-----