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

md5:
2e528092dd8428d62ac5dfa69a46be7c
sha1:
71d7487b62373fd107d633b50b31743419eea92e
sha256:
b8cc442963f5abf7452d95aa0ac9e703024302110e14c90fb788fa0be33ce5bd
sha512:
731ba4c53953c73a727bcd636e18aac4eb8908d16a6258867bbba6179f82a1d45c942e70b61cfa01948776f95871a9b3c34a7c3d5fdf1d8df6261d77dfed7806

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/jalu9uZGunHyUIFAmp4v5kACgkQu9uZGunH
yUIjfA//TNYpcEOHf+91hqoTSjysZ0PnbcRCz06LKCN/gl9PdDZ5I68vUKF1F9ti
xu/v5WXBLnXycB4Z0VbqWTMp3pq+NfNCiKRsMHmmphceBTPtHEp/6dfZdS5SEBJ6
evPWWoisCQMc7DUiPQBbORy0VKb9Ah4mEYwFwoj9U6cIvumBDHLrLbYmsvypp7XV
J65w6qBEXNpzLLS3RDlDregHVKQ6jy+jW/3K+0YKJAPVBdpFSLmoO3jfyNFrzFRv
O5FfDBABaTDTsD3qOYa+n9X8voNSF5hpPRjeccGR8YjnYY79PI/wbHdGVlZR+ZUi
tf5mstHJ+GIiDyRu212NI+pXgGTSEx3Jv/j4xtKxkKUsWNayroKiOSlYbloTFg7z
K+lkbadpGTZmIoJ1FHXN/Zwwl5w2cyJ+UBIVVC5GZ9K+UsoaksWHW6lB/EMD5YOk
1+zQGOON+kZSvnLh9SasmuEcMZVvzcjOTeDAf9/l2cA/fDK8Y+vSTApz/XwMp7UB
esQ3cGqu9Nld+fbDxGBcWW5zTAmjI8qv03g+7jw5v4e/kqUe9o1Axz6FXKi8evmX
1NESByCYRyChFSDsNQx/Rp68Bm8FLDXFKDgzFiyNOBTZsA0SAnVAnIP3Yv14tDGF
p3rZkKpjo9axQgkMviRjFYztfiFjZJpoREPuszCi2mqsNvPhdAI=
=383P
-----END PGP SIGNATURE-----