-----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/jalu9uZGunHyUIFAmnr6ScACgkQu9uZGunH
yUJ2ew//V1XprBhKsmmj6QQ9PgBEP7YGUnPsh2XdYGGRG51r7c/OFjDKmoJPIBMN
FDW3cZFOwHoFL1g5i+zFHTmP/ajCJS2Psko+smFWC9YHHemKKRnn07EVSQEqSM/5
d+1ACpPY2xTQIsBLHslEfiLejHS0k0NQs4A3oGA6mAH2Ancz9vY33B0Mulb2aBfI
VRhCvzYwLjG9WfMbHYuuGeN+jPFyUkq/tyVMuycyvU54c/cab8+aimXV5cDELQCK
Ii5M442u/4T9FgDZPIg0BNvLKFnfnRI3J66hatWhicQAeOgeb1BN4XLlRdEEYKJU
vxSgJPM0Hvfc0Ks4yVnlbCyHvncmmldoPWLpqZxUqDBe2ufb6K4nEktbLNUnCdQy
XKdCs2cnxTj4jKstcKn1wsvjxXBT0qau0yCPFtaYNAdujFzGBKSCfPgyXtAIGhxu
M8yh3ovZkh78OMaTZEIYEPx8itmXTxphZDWZf1kEy36uaQCEO5vJc9jmbgnzaYAU
7dv/2f8eIviwaedK1vY5+Tu2XyFXBRkQoswLSkOF24aDXrUjzgTRD0cfU6WOOkY/
3knaBmq7V9dlYasKm8kpqsN3IUGVYXEAl1LMtc3cK8EKviyNU4gLSP171c6XFNWN
e86RGZKGSc1CSQkag7x8199pbDw/QuvfF6mz/oAwmgeiHh+h2Cg=
=ThE2
-----END PGP SIGNATURE-----