-----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/jalu9uZGunHyUIFAmpq8jkACgkQu9uZGunH
yUIn4BAAmVjSSonASLZcAJHXFWJP3w15IcQJScX0x3HerT14X0HKtxQqjwY5Gio2
meUs4CQ4Fha6Vwz/HRYq/y/OGRBVZCy3FDPSg4kE8czMhdTqmzfOFk8PGjsureWH
hXJUa+f1zL5fMyWFZfU3hxZDH4A3XULtXOmTrn8Ggp8FY7LLSoZ9lBzMirDKtYxu
PCs0eSMfQydfIeVkR9H07NgplP3MibZHtAy3ijThgKPJ3upCWECVWVncf7Hao6ZC
LvJyDWe16wubchMy1jQDkV+zlKmWlJ9LFwMAA5dLG+m0mSmyDbZo61xcG01WFeYl
lnRFLNqUirfxvWmA5znt3DtABa3zVl5vMUHXEsf0tN4lmdYyfVuXFOjM5HL4rjqf
c7wZoMqRB0Uy/IHJCFQ/9UJZrv6AV0R/NqXhESlKAuRg3719LV7ly0ryhUD7XdtO
y3jLb1liymotorIinbA6ZqETW8k45I/QTfcmQDVC/huswERD4KZsp53jLev7pErG
jUAB5lej2NKwagwRCMkN6OWJAfAOnKc2MRBfSEbPnTQx/b9I8sVVLJ0bjbpqom7v
SybKCCQBf+EIBnlFI3ctU6Ly+8BsYty8oJI+9ZUlPq5M/ViQaKmHE6nT2eoH5Pxh
QRxmNQvTTan9wrXDgIrnVfol6uQTgMQpKFw6HnijJA2ZR40Du6w=
=WypB
-----END PGP SIGNATURE-----