-----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-----

iQIyBAEBCgAdFiEETYf5hKIig5JX/jalu9uZGunHyUIFAmnhrAYACgkQu9uZGunH
yUKi6A/2JbfZfFFZnx/U4tG0RNQtdF75djGcIb5bRmUa6j8m5dbJ3HjVkjFH3zDb
LjCYu19YmqCm52pslReGFdCdCk+CXaxSEp6QjdojOW+9LVdtApjRmhF/ThFPDmUR
LISQ9ZdDDkRj61C850sEMTFoZHecrSBSpYp0vMMbz0hlsEdzkWOvaHwirIQPAWOG
bKA5HIKgnke1aiPX/r3JOhja85d5yyWrrJ4x94+noMkTzkvfKplO+j0KuTHnTUCb
TqQfeIy7gF3Q4VhuM48xPJm+rz2mhulDAInJiMBLuTM2EMaWJttw8BYXwwZVcTxH
mfVKoqOfLjcRs7vAs4hDYExyqCDXBZZFOyDYjULvtaKh0CbdNW080Df4IowPpCqU
IMlahn0aTmOnTP2Lmh9m6nR5oJ/+JhLfhJHZbH/R8wWI28Nb2xu8qqETmrn9hZld
m68Jp1COafbqA9XL5JigLK4SRzWDHQIwJu/Jm1UUEgOWOAyHkOqUK5KTDAF2FW+q
/yOav/AZQgfrl3xw1jIVyjBR2bIv5emm0CBV9TqmPhB3Nw74I90KJLUXEakHuCIJ
bgydF7UP9nwvQpNMVCaCtqcs5v6JeLhSsDpYeO3dfRZtLF9F14mkm7lF8mnCG/qn
yMHK1V9hJG2ZA8IJF2TkPrMHWomZGyESQ3FbUrT2QNKGbe8R/Q==
=RTCP
-----END PGP SIGNATURE-----