-----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/jalu9uZGunHyUIFAmrg1FwACgkQu9uZGunH
yUIRPw/+L3JZhFvsouDXoUNHf7MuGOVOeqVhXO0bcsLeGB/U2l9XGR8Kibf8v7iv
4sRRQ/1fEFuu1vslMMM1NcyPooMdVGtJcmumgkBxPPEwH/NY81gXtrBbR7EmJY2M
acDgUdfuj1mpA9hK2R8XnRR440KKX1FMsNxJgDu/NBaOMPH7loGyaTb4MfJ7AVI+
5hpOLTY0d7sKWDxbfjQhOspFup6Jhk6iVAzwxiXqcrBV615Q/Lh+feJ3rtWvaKw5
xfxxX8cRbUAftQ8GwqnNQB01P49Wzx8kWXh072esyamS5G2kNB8TXuL7hjrqZ7bl
ovWsxJwNwq/YUWX3qjWwQdBmIj6DvQMTGXDFoWrP9w89vHMK798mS7nXaKLRCnwP
jYTuhSjTHL6Dy4uH2L1p6I5iBU5NzFw2eIBqKDGhAzmo79IXOE6fO+vcU9gsNiks
z6JZflX8sW0oEodRycbt12jpZmpccVYeARKY1vuwL5aZ0T0qRIbqiIcA4BYUWjsn
n7hEMRNxmNmuMOAWYAKZxaMIXIKYIcNXU80ADjCIKoy3umeN8eEoAOXs263fRh6v
OVzN6qYvCwAVF/+HIZKnnP8XgAXckGNSnKfw0PtHKiTjZU3pqfiHBGDTzMZFSKaD
Eay/LyKM1FcTqus0KhORRMlrZhEwHzyALTi2Gcz4qg5DlIPwrMI=
=4wu8
-----END PGP SIGNATURE-----