-----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/jalu9uZGunHyUIFAmqIG1UACgkQu9uZGunH
yUIzTg//RT+MKzROH5xK+iv6k+cbjU1kw3IdrSW3BeAN1BiWY6uePKhcC4w6PlUq
iW/mj4mXNTMNK9vdQMxhD+VqOvJlXqhsCUhWU9xb9/R2XiuNq/ivOG4X8KQRUSqg
xHZS59bBRZz04tiFJN8QU/m5vCtoi6ZfZ6HZ6IuGEr1FphLg/pWSSJfGso7ZyUu7
h06bziZ3ek2/uU1aqYEUFWK+BdC0dtjP/VbkAMMNw/Hiuq/6PiKmTYP/KWrbTviQ
F4OKW5C9P75STF4GXtJLvHLlxLRpzpBT0KDA48ZHIxqlpKV9Qz/mgUJWu/3BC+ML
o1ax/vEBmyjASi9pzqML18V2PxvoxOgMDz/Pd5G4CK9CqFV/ijV7jG4bz2nsTKpG
c/NPSwxv4VgbROHcabynMT2VLE8ezcun8YSjsy+XLTo25badDlQrp2Cd5ZFoO3CV
sExqwoPYs1swVKoFmz3k+BPoHa53l8yQMCIVnKbe4xWWRrhKeuucq7Gpr5ywlSeD
Fg3r3I3bSO/RLZPrXo0gVBF5yTxpBDMydW0IgjFbH/rKEtfI2MuBFZGGwsTzivp3
NFReho9yxOrUUNFJyAfxW2AUkOdaY7ekrQfRHR4Y0lOw+TMjq2ckciZqGXuJcvxy
0yUL5fwfZufD9cZbcSc3KkVLbR4J/SarE7Oz3d2I6cpvCF5U2G0=
=EEWg
-----END PGP SIGNATURE-----