-----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/jalu9uZGunHyUIFAmrNu3QACgkQu9uZGunH
yULNZxAAqbmAfeBraAhuWEHh0tEKPRSR+P6G/Cq+MMxA3WDDss+GRHAWx6JWIwKD
plWoumJV8bvhiYM0DmzILFQmb6xEa9gJ+H3qmqle0pJNkycLuzggT6hTTfhAm+4h
cscNtJTW2joIF/QQ/sFpfmQsUcKL6dSP1+M2VOlKX6xzghpGe7dV7piEQPLpjVU2
cHSVw+1STyRK1sl3QVNQZTBGGOLCZImrGcZ/6C5SRdmTW/hBnJXDnNo3ApazbMpx
FBQMwa8ZpIRmrA+Q3y+6gtktWvYFMFVO/PsaGz0QIW+r9fp1zGqIDJmypJZg2z48
Qee4rLxbxg0EWls7c0nphZFp09qZDy/hSMc8Lk97BO1z0ANkruas2+tkjDyCZsTo
Ifb9IHgqn5ZPgv/K9NDwmgwMVHP7Lrt+tqjL1oaWo+0pckVMe8Qk2J/gr5vGFQsT
ex/P7U2ROcns4lWQMDo0IICbwRk/hdOFqo9Y0wIkZAG+xIQlvogX57yMVXSzz/G6
rNbL/D3mfj0AhnoSMe4QYJ2x3ui1fvXm2HxSGoizNrAeb4pWv9ZQsef6j1gYZjke
iOBbu9MrVxfNTV/ZD/p8fUrr55gH1Yv0BYFmPdxiyVqkAKWwDIoDtHEDlcHMFwcX
tpj3bG+kciCQQuFkauR5qsklyF+rENkWwe81/snSiidjhUesL0U=
=nA/8
-----END PGP SIGNATURE-----