-----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/jalu9uZGunHyUIFAmpXxGsACgkQu9uZGunH
yUIUNA/+K1ZxnhP2aEZ1ioSbYLq0gSmIeTb+ztwEu1GHiwp2rp9EV1WAcpGf44qk
yB5uwCGdd0GzHWyCRKD+z0BfK3VEg3ABDwi+cYVh5MR1oPhOBo8ZZeW2fX1Gdl7v
8RjStIzdO83qQ1OJiBbqxS1jWfQzn1vxjS84SVQ/yOol7ZZisuZR8fQ1JzhYIHmj
VznTSnmBbPVTcYLEejE8T0Q68nXVzmiCK+TYT4HbU5QD/POH+quF0CSyJfsOtrhD
b3SEAfDvI/ro+YAOc5GqIbc1ihb0rLQzb+Mee7PGMfNj3eI3gcOBWKUE/W3y6JgS
pdFVAaTq32dWx7TfG0NXCwC1w1DA4c5ObTocx/v/+kMC5SO62oTj4P6j+XQhm9Zw
WPBG9xsbExXmJm0AyNIPnvul2vjAdy5QxXaWMI7UQv1k7IWwA/N0++Llfh4sK7Nm
Pky+g9qNRaX+wIcWHBr+T2/uGgcmJ0OAV+q8Gaz9PwioDTS0B2eN5L3Uz2rrdvYZ
gHRwkdpNzJHB7XYrnux1xVQxAHb0VMsQqTmAIiwxworR+HjEYdzW1ESeyUaOUfo3
CXZiw+4QN2HV9PYPqlCh28gKl6qyMflO9mqx9fBNptwH08jmr52+DoNtn/0chYZH
eatcelcULLAl58FI1qbzWqOfM7A/VPXmycVov416Q3qFehG1Wrg=
=Xvsz
-----END PGP SIGNATURE-----