-----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/jalu9uZGunHyUIFAmr28PYACgkQu9uZGunH
yUK+/w/6Aj1sCw48KsZpyeJ9SEjM1tXWJCHR15kmejeRdFF1ZoHLZtrE5H1Gyq/+
AwhOYCp3w+qf75Dp6ZcjgHukb3u+aQcZ7xB7Abv0Rq0P6vQtlxuv1gDR07nK0xnM
Ve8vzF4R7lqcQUWZNToZ3+0Wt2bpOSuUieQ/tny7DR4s2acMnCxRmxnrjcpe6aSy
Loifsw3bIKNAHPu29o04Oru2wQ/R8jKS46qZ533oS3dlT7yQPOg8P1/7EEiaJDem
g7zAZb9YOLJoSLd+fZu/1OQE/7n9mB1XPEMMJng18+3kGFychQhQcEHDZpR3UGwc
M551iPEyZqssJetXHZgFRi0zEzYkpyLmCMoICR+eHin7NjzcK+buQBz2tDZUpqTM
8QygJnqlZlqL9JcmbjUliRBBGmXM/nq5ttLJ9VhSIbBuR9ShQp9J5JB+0Cc6jizo
ZzWKwBTYT+BK46+cqwaAWgKTgQFE3rTN0Tf0HLi2+OypQvxegO4nX7joIu5uIEti
PYR8eh8VX97pBx1th66VsDJ7b+MEXlFI3VLdOjMFwIsj0jdHNPytILmRSobiKdXH
DcDC261ZK421UV3MTyV6aPceu5B2U5Bxyun10U+IEq/2cFSGzqFLaBVjH7T+b22a
Wv6U2jbAXBIniHXGk2rMoQCGHu2+7WY1bWTNMH/dibBI8/sm/fc=
=uH9p
-----END PGP SIGNATURE-----