-----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/jalu9uZGunHyUIFAmruzk0ACgkQu9uZGunH
yUKHAw/+MBE17rRrhg9j967r9vqaQKjkheIcx0Ro1zYQh6ucch8YfRCVUCwN/zcE
4eu4P+wPgRI7MQRH4TGFgwgOti+hsotHzNLC6WI6+RA8PKGQwWK9ygvj6FEt3Fbk
bryn5cOEj/kT+DlOLp4qVPrKJm3xvDCBHXkpcKtwrJf+yhWIiCVpQEQk4K9ByIx0
rkVHF0qQZeU7HDyPYcSnBSuxA7jiVwCt8U1lVXk6lee5AIGnKKoeFMxHhZaDHsvt
sfxg+LqbOw4twJGd/WF9NUmotV8EJp9wVWv6ifWAXLbepYZmLkgU/NG+pjfYaEwH
m1XRoN5SQo62decObgww4H8Rp46AUorgM8beIf19pzRYoTtv7cn2nYvErJafs18J
ZyPJBNZsj6sx6XhDZtCzDHzmRdDhdOQXM9myXQpSNEULDUT4zQnxlzDAOmebSzLJ
FAup8k12ulLgZCX3wVt9NG2M5hZqjLOR9qhUIoe058xHw0eKKQdSoXglglpzLmrF
sCNdDNAwJIYL2EBXI+71gpK1tmYKJFVEbo9In7pnj2dd11ow3MQjZ07LlOBAzzT6
DDVCmRfGO3bztLLeyFYHbRv7NILblVuTlKIz9MQbsZ6QhFe86OJXXzpkhICkUlTM
tskPOan3MsFqc4tH9D0m1wyL07PnOlFSjeMRE6zD4DVyyIN5fss=
=8OMZ
-----END PGP SIGNATURE-----