-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
05a39db99bef224495078c24db168869
sha1:
f72529f5f4831038b3f783aec8d5207175c0283f
sha256:
f37be6a7a14e63d2b44f67616c070b26b71266a3122c8e80cbddcb26f8cabdc0
sha512:
b152cb08a2cdd707284e19e5d50e22c2e0f1d00fa4aefa329c5b30fd7024ae01201459dfd77170f9f4f1f4c7ce3ff02191c0204cbcf55bf0e4e524e7f145b70c

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/jalu9uZGunHyUIFAmpHYwEACgkQu9uZGunH
yUKHlQ/+NbphEPoWUiYz3wUFRmzEQZ4cFze9C4cFE7JdoAugs4DYrQ07hLBx/SYx
k2l83IbyyVpvMdhRCyFLaAhbYNA47K3lfwBj3iFL9b7N6L21GXIX4M3czUDYGchE
aG+IP8Z5mV0AIhHdvovglVjJ781j2yRKLkP07OR6z5/zsb6VhRLQOgxodlK6v8qp
EgDqo6YDgdPdDg2zVwU/z+P+ybJsFjpN+8HrLgjSzixpSyYoL+ZqcBz6kYM4gunC
DYacw1N49+4QpsBs5wFtGoEnEsaBIoOXyRV0cp6WZ+1sZTKDXB47JMOZuNLMhi4C
SRFxwt4wfjVtuSqk8tHBF54PfDXCEeDo9WF1oTn1JLEH8haWLYSjoNPMK90n+rKW
1zsk5k/qtG8Xx9CoyG0HyaVXFglpumlLNxLYSAWeXyG+3KjDmSit96t4Aq7AQlj6
MpVhG2vOmjiOFf1LunmI4J83vrAFc72HPSjGMUkPaU3B9dJX9qlBojMNxcxpCZqk
xgNCLrdXO1C88GNP09iNe/S5TO6waKm1Xf0Fwz6pPb89e7a40Czf7xBWcBwMWD/n
hEPRYODc1MJ55aNFiq7S5CCx1WW6wknuDlOJyu8FfXEcGkti2eNDUf2u4SsKzEoK
BDrFfDdC7zX+NcjQ2jKisVYTEknl1m3L5sek64ZKaozYHMv0n7s=
=2nVO
-----END PGP SIGNATURE-----