-----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/jalu9uZGunHyUIFAmrJsJsACgkQu9uZGunH
yUL2JA//SbtnvKx09M4gjlDNy56HdGACuSG7aS9j2/Djl87H0K9iKM4bU3t5WUQZ
OtIS5ttbLmiZKAv+TgOBvZ6JxytlA4ToyFud+AwmVgIuritA8crjCMJ8elAwAt4H
YfLZQp0qNzDtpGvuTKKuoBy0Lf7FAAlawX0ZJNuzYOXKPnr+ZfPNxvzGNXguk6Vr
ZyII3LJ/XVVyJlRjQ/wnubDlS4TkhMfscuFuxfLB7yX/yas8Vcy5uaJD8BWfaE5s
qg5TM07TAQP+1t6axPU/+MR2MzXqyv8mACiVObEBhF27q7gQWQMwtnK0HfeyrHxH
iiZe5WRlPl/hKCyPWvPCz3+lJwprrXyAKpqCvaLP/Wd8b/JRcsUyA7sl7yLY0U8a
Kqk4hXvjFn+s7G8v6u1SFY5mRS7H2o3oUfdDb5b/bQDsWpAGF8y51C+1L0UGGCLy
kx0kM0fycs9Rfn4FhTAxRlPsHTMXCUamGJnUQ8gsJsB628MFLRjaGErjQt5J0Ewu
8ndqqcku5TdiemChhky963QGpXGqvgq2+jTZ2boYK6We74GGZnlco8v4nfGDDpeY
JFxRSsKg8oyX1nWhECjHXZUkFFWrfnGZZeRIRQNMQPizIzi96CQi2NqQqGlo5bYZ
McKKi8+SqR2K6VORypj1UgfYzxX9UxsC7HEagk3FdMq+f86omlg=
=u5NP
-----END PGP SIGNATURE-----