-----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/jalu9uZGunHyUIFAmhp4KAACgkQu9uZGunH
yUJt6hAAlFfMPxr1BGU9nzs20XEpAuhXfqJpzvPPW62bVjVt4Kr/8Xq4s/vVu148
9lU+X9XE80IqT5Zbx5HdMVKBVFcAkMfUld5bKxIDep8gwmATM3EYbdOQUDNWWA14
Hc2YYrN32N9ZbyNbM6cxAkNKBBdG3OOTX5GcanUT6IqZi9EyPVkPWVcsySR0pcsg
Mo4WOC8SqQtnZyQFisvODKoegkRPxzMtaV3PpceqUOWxdgMR3rdluWHHIkQQ8mN8
2kOgdanl8nrCYhWFuKD03TjFjKP1z3WfWVwApgJ2C/+Yx/+Vr1EAUj6oNJ/aqp5F
pvbklBUAMBwWJOk04zTSCnW6wkbs3JQ0dkqgIVQTWOPsOyKEw/9fLUo3OkWdEmAv
RRQR8Y806sBUihq6yyld6hl+w05oLoWEkO4HoDbu23A8nT9S0QPRAyazu41PlwGx
Sdj4H6YzRfZ+IPRH16TmIkI2xyRDPRoGfDxvW2Fqv7IivQr9g8hijF21c1oUZGdp
JVGGu5l8vycgwMEwIeDzrzLp4eNvAFKLHlTEcJaC3dAuYVyTLkxQ4FteG34PJ/qO
8K9oN+0vhFhAhLhhxfYxw9Q0TACWdmCDYflVSNVyadrirEPo5Qo0NB2XzXVciUeN
h4kSUz3lRG4W1d60JBlZt3aX8zsz4fgfIG0oxDgojbpHe8tiMDM=
=ParH
-----END PGP SIGNATURE-----