-----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/jalu9uZGunHyUIFAmrzHwoACgkQu9uZGunH
yUIyhBAAveaPu8i4oZBRfwU7yR1ijY9trZ2xhMCWaWBFaWVCeXdR48Sw4mbl1h5f
uTzI5fEyPuY2fbampHIR8FiRI+aoI1w7Vo4pLsj5hpHxK+jVJ/+iJiz/OVmuJlng
l8n+U0qzM1T34cTm22JYt1n36ZaqmnzBt7BEBVzQ9rSbOVtXrYcYiJULkaYZ5tok
XKoY24R0taSG5aFQkbqEbALR8CCKbDoOwu4OrpWywiMMxsYf6TtSWTM65HK9Z43M
heTz4Byn9IML6wWURICy9gDfrihjTuVRJRCLpRlYhv21w1uM3zwMIRtn9kJxsH1h
fTeAc8eJd0k6xeCZdEf+gwC/RIBxBYBA/cA3RDoEpRjmct6Lr3lOHmaI4EUsHTAf
9GbBasWwDmbmpe041nomHJzBXNTSEAuYTGMcg0ylGUuqbNKDxlrPyHPfS3iEuAHG
/P9AvQKcsivy+i1anezegFqLHr4oDCJPGI+qK41Y6/sk0RmjKnHSb0r3EqwO16ff
PsAZcjb5qaNncQnY8yCaHZE/HDbP3uBE7jY7v63+ZwpI/mQJZCAj1Tul63eLp24q
T7nGNzOJ4ac47rSiTbzF/+jRt7KHIQhaf1ZUAnZlC0Zf/HXqxRu5xnJ5Jf7X3JoH
H56PcPtClG4BnAWz19D1efBwrbZQoTzRf4fjgC+cK++fu5YDgeg=
=44ul
-----END PGP SIGNATURE-----