-----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/jalu9uZGunHyUIFAmqQcHgACgkQu9uZGunH
yUJfPQ//d8c+lNLTqbjw05aZuhsJtrTDwxWTYiyqJjjOVQ3rex/xam7bSRMhha13
TIf5QdmlJW3PGWubmtQwwGc3xJLkBmlpCQUYbYxbhYzCJK+T7c+6JWA6eMDkHhb8
7y1HwiTk4C1I4zjUHBlsXk65rxoH7A+2UwEaapcPKx3FZWRCjBd7iewlIVA4klU1
HOuHui/QjOJhGRDmgnT/Ghnm4erHvXDKRJCsBleF5yeoL4qHuciPriDzgEyvsKg4
O4A6QhkCGIp0SZLSsKXbaN9tRXOvyOa9fx6g9HuKg3KK8ZmAqKvnuhcUDvT6ZJig
Q2p2SBbCxt/gbJp2dz4mtSWMdzHqY5sZmzFofqFJ+NpQ50BFXLWDM+0UIK//6p/O
5I8spWeVKGuvzuwX061xpIu0lKRRtcfJaN+ss6lkFNY0WSHF/u2qBGDcZ8uJpu6p
MtcrL/qpt78cqA5deyELCMt59dbYkMdQTmPq3ug7ty8G6gWtEVIkcQmEAqaPu5eO
8OfJtfEpfAdMNU6Yxt+ldNxFziW2A62tvzo9xTk3Vv8byLfScvKI7w1R15hWq+rd
71ImGUtDe9ZS/sgy6qY28P+WI47BitS5fNNRPwhUuakAHibDkNflTOyES5nIHClP
n6MnLSfBZ1/yWkFDTT0zSn+FDZec/KUIXpWHewSZqH5Xc+KIRZc=
=C+z8
-----END PGP SIGNATURE-----