-----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/jalu9uZGunHyUIFAmrUeEkACgkQu9uZGunH
yUKjDw//WLSByUQGXvxrCDxYhWS7ZNBU1ssF1iupk5F/WOJ/8wkqTJ51mrfXN/wi
nBFAadXVIbgPXVHGwlUD4s4QHAJ6gmWfWj0F05swhYJdpJ0E1ET3t2mqDZ793YqZ
dbc8/oZ+z7kQSy5u4VSzyNWbSBBJslbh8hVwlwhySC4rm1e/vE5zVguQ4fsr45SM
nFxRtBWp5kEUF8j6namCKPkCqcTZgMju90mFw+sICMle/dVJuaIkUSatQiB8T/xL
EfHBJd+GYaKVPG6XFOhDNNRINdjIi+SAbk43O6+erAsAIcmyDYMb+dkdM+LWxAu/
sCFEMq0N+l515dxjgrFAAaM2jJ0GHoUgPU/n7xLI7S8rm/xqOOsGLk3AEnEa0tfK
yX6A1Fng42KUxuJGFiP3d04+HAnAoH+ioUrNqeT1zPa0RSYe3ke90myqgXZWHkpl
XSwtbMlVoPguH1zdDEJ0NIEQvK4LmBciyB0AAhGyZQw9P2cq53w1bvYHutWPA72i
7cvSgKalnUavHouI3hkHXNrl0gTUNoomotcbMliE7SFqIx8dk7iADQ7yMfhcJluD
o31YIiZ4lOofkJ0N8/AJyZSE0TLG2j3RNX83mw+wjFzFIXYgRQ55PP+TnudEjRpg
n48go9sp7SZyih/f1NTyLFQjzovgraUvixOB3UzMXrgYBtxTMVM=
=pHhc
-----END PGP SIGNATURE-----