-----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/jalu9uZGunHyUIFAmptyzQACgkQu9uZGunH
yUJcnA/+JZy1qbgxIGZ7firFsJkt9YMHGXipLydKUglgyXI+9ggI4dtSYhX3XGIC
+hcRaIou5kAcY1cGxqU+VZHlpPps7vz7QIDZprIIgkYHjmARJ+vRFstFSm6aoYmz
KwPJzTyioDwTXD108mK/FiDntPvmaFMAikIeI/lsiXbq5nsZQ6cv0Ue3/1k1AFUv
cMguEk+T8ouAWm063ZLrEd4PGWFEEJEuPzY5WPtKyci9fWNS9vUKDQGopG5DziZa
H6hdgxasuA7MpSmS70iDqnC6NOaAhEl6+GlnjFT97hOwfD7ju56bhapF/rEULFXB
FQhromxr0+lQYoRJtbHOpHsvKakJGIcmG2Uj7UM+1Zo4g0NmsAfq6S8DoE5MQ9Os
JTNm6s9F/OI3BQBj1NrNS8pRXgWr6dGL5rBfpjFkTLAUIl6bTgqOUagJHjOAD0ha
+OAcUi0yU/isdckCCu5wQHonsm/EZNNGdv7E7hb33082mZ7ROhpGM9kHiJ8VscWQ
XUaZlZpNuoQaK/G8gdshyKYoIf43GmHNqpBCOLqQHmbOstWsxs9ZAFvCxm1Ft6x+
hEQrvr+hNbZOZytchiKbDTXBODCeOHzL9ni4c1GnR/O9bfXqFSAzahSLO5i1GFV3
Aj8VKaLrTG6KyoF5cDoP1Lpus9BBaG2X67qceywmE1PeknnmBqg=
=R4l+
-----END PGP SIGNATURE-----