-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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/jalu9uZGunHyUIFAmlxzagACgkQu9uZGunH
yUL3pw/+MndeDRom0fXhho1TGR/n4+QyvRfnv8WrhHDK+fST+crhzrlaLCWSxCK6
zDPXmGMT5x4JVeu+MaB5+J7Dg0bTKJMPgP1dortclEgsPtyU/ol5cblcePRhernU
sNufi9RtylfTkGOPLqV/HJC/WVJp/s2m07t7haJCev/jDshmDpmhTNVihpmTi7+x
ReHJ7IauS0+vxRSk+UKdSc19JvZwQ5HQCXbt3LvQpRpZ/J8NtS/67sScarqfHiFd
jRalDk2jZVjYarUEv+wQ3hOj4g03/EgHjZzvf8SXWxlhdjQKv/g6+mYBtYN253r1
FBknG4wEuPov/HGdkk1Q3PKi9REcpZ2abOk2k/vOC2XWyKuBLQlcz8GLS0F+Tynj
Hk+Jy4Yhk9pkT9eaYFo1ocmXHJBorzuUr2ZpqXN12e9JCbI4eryUJOW30BGJF0m8
6OZHv+vMVj1BMNkupa6kfdKGlVT798He3LY9zxaGcJMa5dNsff+ldHGYtcVEaA7d
B7ZFnXDH7Ph7bBedCYxWVcUqIpzM4DrBhs9NStNEfNVfy4N01ptdqzjc+LpkdfRr
jvU7RsQsQNdHmbI6bHAcnixCOjjrzksVuQDQJU6QbW6BpM6xHT1IarCag5nX0GZW
eukqfspk0PnZP+XPB3FRotBrEnOwxCyeROfkz1mP0nWqY0IsNbA=
=kOc/
-----END PGP SIGNATURE-----