-----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/jalu9uZGunHyUIFAmrVzqoACgkQu9uZGunH
yUJlCw/8CB+P4biKH6Vt4xfRPR/zGNj9Po/MHMF1D3CGCuzwpKypQ0VTciQWsOSD
OWg1EHCpEoxpqmbFTGQA1uDAF8eLkabCX7IetBzznqcTv0bHV3cFM+99bCxgL208
cRYBywTM15vSnvD7j5Bl8Z/pSXBQ+mxIbGpgej4pIN1I7wa3nRm38R6H0/fchIJ/
stISfMdOsb9IT207sRrduiEJXEID7Xa2fmCh3Z+TfsaXfAKFRDMDrpmBpFaCWa8S
Zl4nzCZQAGwqhn+l8oDZxUoxuXm/tP26ysh7hW/qDrt9Y4MTvjMKh1kHeVBuvf5n
v8h7gQuDx5SHy9rS1Kdc2TGiCE8XYwgl1uN9KaFaZxEZ0GcYAO9ZLPhK7/mYPAJX
r5elNRUUf10os498NCIWsZR4CT0ReQlS6gsSghZugz/eKnbiD5SXiOIaKmtgvAaz
tP4h71/8eWC+4ne97wG6/CtombwzolWnIUfCMe/ig7KSnZyJEdKkL3M1A87Jqpvb
MZKhul2JjCaFEhWlqCOPdIfKL00r3TjDGLWMv3N+rcRUbyjDJaqIH2Byv9IQNfqJ
Ch1yUCZ9rURvzkBHHXHbg0LgLTiNnsXYBAKOBin4nZacbp9dsztbuHL5ulA15BSK
+sCB/qhEzOOIoVY2khBB7k45CF1WZjwGSoiMDfkIEWQBLqWHp3g=
=k8/5
-----END PGP SIGNATURE-----