-----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/jalu9uZGunHyUIFAmq13cwACgkQu9uZGunH
yUJlgBAAjACDHXMqXV10vxnlm861XulOyNIDoPcvaacpLSjHkI/jJtj/lY2c6qUT
dj04N9/jsBAdSHFquk2UM8SB6gKlJkhrKGsZTWWsTI14fUWUuz79zpo91D5dujAq
zxSG9NhkNshdTjIZM4B90Em9hKKnvcHNkLWlNOZbTrd6Rk6Dc7clIy9F7mcQsy3o
TxLNPc7pnqg6cUPZnLjNwPu45/JfX6mxfBbdwmlQVrODKxSgQFvdrHe4cJa5sBTw
NY/g1hhorbRrzo+EtDQKShPBv04yWT/R/aI6hiyDI3cWyodvayiuS2d7jEqcuQbZ
BTqWN6/VzVTCOPWeeJbnLuWhKlgHvw2I2F7bU/zCapsjWK+QoFEUixRVkU1ID/9f
bSFa2DegFXRBPlNP9xXi8ul36aEganvQ7OiKWFym7FvajUJaPY5TkCwnxFphn46l
8KOoLA/xujQTENMHYop6lhNZnxFkKjTeyGgWbWKpjYXUvzOJ+FYHo7B9rx3Puuir
tq7PRGFLOMEf7Z1iT5/C1VZoMuimAywsnnjb3nmk6yUSA2+wXxrIwKGtkQHjqo7r
Lr2C8+r+VgEnYnBbkPVKsCjcds2Srt5BX4tOYMJJy+10mzecab4G/+PAcQktg9LQ
ER4Xkx47aAlvIjNRFGYvhW1X9IrnAGfytKN7cU+1UgZJ37IOVC0=
=kAZN
-----END PGP SIGNATURE-----