-----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/jalu9uZGunHyUIFAmpLdy0ACgkQu9uZGunH
yUJ3Vg//TXzVTLok8Xyn2TBKSgHAU3YVo4Kum0faiwk8eSrnTuHM5qEeHP8D7gN5
1FV+of5dKsce7dFCa3Zo+hRuSwBvSHj4VyQvD4cjI0Ca2JuNvJpbV1tmDKu8DHEt
F2gGWZ4VZ9vvTSQmPWvS5ybPt1g53nU4+3Lpn7pCistG5GG2hyUAmdaVw+wXBDsK
DQSxyxuwIpQFUqbH9LOUEBIGhjgq+BUAXD8Ca81amNyUiAyszf0TaW6C02EbZwkh
YyCmm9sSWpNd583WaXKjylncDGIAx3bIcD0iiVSJ/giXCRi3vBQDPkheG8L9ptaG
aVj09Zsst2bcGJPHjx6BQog6wwEHQpQ12sivCO/Z6A0SqYVJNwFGKXOV9LyoIELh
rfE34INRtQY0bTxEB6oEnfUZsoWt8cY9kxJZ6wTCSeAbKPIKEw0g1bRJWnUDyEFp
DqrHCB838zrsAaUa+WEBM0u0t97vITg2JfcrfRmNeGWc/XJyIg8DiR9xLkTXioT9
mrgExwczw4iBphgIPbyAWYJDvc3lWBfhRHHc86WRQJMw0RktGH65quFsVKDj4jAi
n39uMWKEZ6VRExS/2nu36ynlmzPVeD/bFRtRZyzIevYau33A7eCNVHrC/13nvpG3
Jaat3B/lX0cPuEOdS1LdNhlvq5D+6jHcLAgOfnFAtpT1V11z6eM=
=Ah6e
-----END PGP SIGNATURE-----