-----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/jalu9uZGunHyUIFAmq+sycACgkQu9uZGunH
yUKOAg//XbUTTeu8jbp82Zpm7KRjS86rcnWitCINcGQSMurfT9AqNehV2hMEYayL
thKL5FdZaT1i85ZM+VHUk26KuFS+m1aIDkvxt7DCJhAo1JZJQkSr6+xPYM18/s3y
ScK3wN0Rw4iWR3UjZUKHjjfKSarRrFvH+ugD8OANjZoGXtinnDbepN1fGpwFTg9E
L/Bk0uA8nkZDoWuFZFDm1SQaXx58BKoZYLHPYHGj9zbcIH+LaVjOGfjudM+kBn77
t6+LLYTkWgi4e1ubmgoAhYEklrvOvhFwVAbyNA/qEZ2xmjS+h18lq1wN+TRfxclv
nQsNn36ffspxSbUZkQBfpsVlB7FBJ7p5b0yf4TNd+kdDa6Uzg4j6jUUalA7MDzl3
L+VhWoqIiaUCQWiRvqTxjg8xOrMAp1PPI8FF2EWewy7CJ1Q+HS7ar5Ztwwd4LuRP
jZYDIImTBrIzTgjofBFlUtTxsf6f5NVF9oej1STnQxd3pqP58xZizRQHtPX5IedC
KCraNjBfAqHv/ButuqMoDIphJyTCelgzQoeopFqf8poxQTCJ5pputDFu5w/LNoJa
hjBAiW7pH+oWIARhc3z8uo1+AYqPtCkRCseiX0Sc8ukafBqZuR//ScNHSRmtklkl
cbsjbfT24gNglv3aENx8yUNxlATXvaV39XKVekpWWtghvaU23fc=
=jZLu
-----END PGP SIGNATURE-----