-----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/jalu9uZGunHyUIFAmrr58EACgkQu9uZGunH
yUIO8A/+PaM87e2jKyBsS/OBrzyZvlpc6JRGsvMqElJ00kmJbB6YMbVeiPwV/rl6
wQ+lOb+8Eiv4Fd1sZ+oosMAcQwHGTquNgibeQYeCzVszuOg/8gqKlUHHRF609heW
0bxQRL4gMiN80gesMFiVdjeJogWdOjpMSAZ+1QkLafd7hNl2CjpwGONtdHsBpdUL
yl6WM1vQcpw3t7wiBa64DPr/6m0lt1Cjv3lLexPvHO8vp2F0Ht9YIfhgogM6dIf0
TQyrBaeUR485MQi3Lw6VzM7F3+iHyDx2g5byYQyDZJgUO6nLZXGWwGhqv4MjEGQC
WUMoREA8NkzGxZAImk01ej69R9hd8XxZlnKpQvknwawaA8rSE4OlH50nGFclpG7p
SQ9lVVWKQBpkv3+pPfIT3g1YF4BnhnSKbm1qjHNf8MWZ4ScBUKGObvVo7hZy6ewK
drVS4qY0Pp0zOlJLUOn4T+LVm7AwzwF/C3f+mvo0aM/wcYyU1sk1XmdBC84GtnTN
T515rYlwB5rEiNObySeLsCymlbbs0ByBTqXkR3P02skp8Ick+doc7vHc+xBdEWTj
HvbKjjZT287TW2uAICVmksKjZK+TSjh0oy3PAIu3z3mFFZtt4KCGKBV/jdtuDsYg
NfrHxhKj27isQE+ms643SjKNqe+xOKANOsKjxyAyUCysp95SHXs=
=gD1j
-----END PGP SIGNATURE-----