-----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/jalu9uZGunHyUIFAmp17zsACgkQu9uZGunH
yULJYxAAnt4vnQ37+5oDRMgAUp+c5BSe5UPdtaaqsLTEe0ELoNxpTSaKQM6Lvr7U
uIHV3HUPg4n/Xburga0MAmcJ6gwOAG9KTSEXltvnHbnMWYWwf3M/Si33aVApwwKO
vdfL4pfe8EvAlnuoeKVs75NiR7GahKo3iWBlgBk850Omvtl0VVUJyaCAbDQuwe8I
N46YawYPFRkfATAcs09ocdI2csfTtheoDjycq3ZAZZO8/4CZ67PX2Y41Oejk5LnA
pqVf4jRV0OBOQFxs0UxtRDMyVexmlXLzV9vxe67yNF5dVoPTFg5cJXi/Rrlcke7x
TILV1Hhd6dopunGx2bfrY3RaZvOjs3pbaIZuQiuTHbnC+3CD9ptwst7Ijvp8jp80
lhPQpsT8QuM2NXm+gLsDaSmy5UH4fQWgDj0WlhvU6p2PSKI6/SS18ZekkAfTAEiQ
fQtG1etMr322S+NY6NelBbZZOdg0R2KxTcHWs9DwZ3k8Zggk8D9VKnpJV5j2XyYN
5wx1Qddo4NV4aneISA0PR7HvB8ZB7reWnk7UV6Gs95v5/PveA8TrnahFvBHui1p8
iZQ/lYfcYOCtLGEEV3lanywkukOutK6Y5NshlApAIWDu2GMyMdywW2Uu1yeWz7qO
gyc/2/tfBMLGplt+Km86dgRQsFNJlHQ8BJQzSXYNfIeq99ALlPs=
=1cbF
-----END PGP SIGNATURE-----