-----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/jalu9uZGunHyUIFAmo9xxcACgkQu9uZGunH
yUIvoRAAnwaw0vICFjXivA2sBCZPvv7sKyVLAhbCOOU+1z9K9MfChgpAZIPPX0pw
FTo7rut1o8eJHIE98nV/wP+mNTDg5BzdRKKs61S57mF0cCPOj0OCLD6oERXKl6kD
bhoVHFVRZLYyncU2/vIX+dM9e1zeRLOV/lWr5MR7n0SEQ2+VfDpHF15UBNtEa3Uv
gAhi9jE7xuxDCoZEifZoVhvGIZTDqvzDjcJ40bp9e27LIXcAGfhyS2yvHTRmn0fz
kRDpAItxrSkO4JWQhpaRLfb/4I4r6qpuyFWPspD5XLWu/TyZynfynZzHRIp1NQmT
TtXccJwz8hJTtdj12mHpcRvq1J58nDdhh3IP45FdJVDWnUIRObWkeGGRX8a7GOJA
m7CvR1kLVQxYJbCKH3as0u3HEt1/c4WFR42k4YBC7D7AVgbvTnRzmDkgWrf63NTn
o4LW8KV2ApsO6c+Mw8iV9/3ULrE7l1DffmlmnZdB4YNKDKMMVuLT22+zj5wSnfab
q5hS0a32zjcTgYiO50stv7kY0/NYffi4AicSD4Nj6OxkR69MN5UXso0o6HkSpxmY
ZrLSyel7mqHE7m159KtEkhN7TWPSaPSpnNdbYn3e1GGwqqv3tTMI5WX6i5leg1mS
d5YgcF9aWTLmuliR3jsaP1tjZaDkj/KFC2BIwfCC7q8lVVfUdTE=
=bosI
-----END PGP SIGNATURE-----