-----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/jalu9uZGunHyUIFAmrTJNUACgkQu9uZGunH
yUJr+Q/+K91PaQdMHBdQNIiXSyL+XH4N4CyyEmLs4+Rr5tMlilvPOlvx2GdxZrtd
kS0fCqIe9NfKxOiWYxvJX91CEawih2yCS+2zdhies9VscjakSMI6ihHA82LEG9DZ
Kfw+Q4tO37g6Yt3YbDeapwkkD/HsAadLqJDp3cHp8Sjhm+6/3wmmbdAQh3PjcUsL
0ImXsu0P1GtewAtxW8P2NH15zaWcmwLKSSoPDW9HCwrk+icjqvaHaGDcrY7IjDgy
mI3F4TIsEwsF2lTWGc54o7UpIXTUQUccj+WkwR3C/30BFPuzyR6mL6/tC3ZCDg0r
sMj/tPL161mpU/6p9ApnDowH2Vr+YB5wJH4LU4jSxlZUCD0fEk9h+iBG5oKOkT0D
4PpuUkm1zQD5ngwsgyZdSyDDoHaEJLYv7TRXCMMf27BlYkzJ65t9VnxuKO0siHzu
G7kogNrAMnjqJ4neLvsg3YVlvQ+IXvT4viFZCC969zqUMgyqcK4jImr3aKZSC7xe
0eDSnKdElgysG01CCrKVuTPn1noaZoHVrfdf0QlnXjzu5TrH+dqUETJKAFt12+fA
jtt0/MRpFxg4qLhI/i4GeiUTsVy18sOcD0e/tqtWAr+lCFVG22Ls8a6H5AF8Xvtu
iEveL9xLqAxE74ukvzmeP6jUSs3KSVp0y7L3zpiCSi6b/tLlWyA=
=KLqu
-----END PGP SIGNATURE-----