-----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/jalu9uZGunHyUIFAmkaEOMACgkQu9uZGunH
yUJmCA/9F9BUCJ108QeEDqnDk3MbROv4fzfrBxzGTwSOLqu3qExRsgbQX8j6dWlI
PNnPxdC+M5U4luKillUJCQj+3j5q7oJ2o00SUbBhn1ZXbKpy4+qMiF4TFczYZnLb
99XMjhSoPfBJJfNm3lfd/LjAtTB8w2wL2sEn582lwJqlsIlEX8G5+8VeyQ/SvBaJ
HRpDoWBr9RAqo9QNegO/dcVVQI4xa05vwl06TTBPd4jXNCHLctWx6HhyR+n/AZyZ
/rnU/tvr6BCkXyCk/WQ7Mh3O0tihrjOLgrY3pNhl4rDaQP5qD+spvmql3jrNKyrh
ZREMmUKHvxiuEiwNDPgdHWDMaoeYasrnrX+0GhYSbXMacb0P+awHensMyylYF2uK
T5Ttl4KaJhbtvj9WJhg+e1vHzMoGUG63okqxJA2Q8sStd9GfFOV1RTV3+s9vvKGg
IIA5GseRjjtKz2GMSyrlGoXA2lB5tYJGIn4APqoLZaqBdfov0b2/VxLL4rM0lOdz
7eSHJeTw9kFec1KCcWw1/agkykDtiPCfQPoMB27+JxBkVIPCdrvWouCGQs0jTwvx
KFF19nfYXHWvQOZAu7nwKDvx3r4Vel/tNonKYA3yXSGwPxDYcUJPbdf/ScEASUOJ
H8YZWSysObLgTwEdB2Hwe9X1lmpHYUzQ/GTsQ8AUfCT0urRt6/4=
=gEn+
-----END PGP SIGNATURE-----