-----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/jalu9uZGunHyUIFAmne8bsACgkQu9uZGunH
yULsNg//dqlJCotWAJuiikcyzIR7k5kn2caYBm5KinZFyvh4WR56Q1OsD+D+TLZ9
bFp4vyNw9tIXpJvHdr8ZCjEJAT8dpDC+Fo8OodTthr2pCDTFJxtwZVPzvKPVeOps
6wHD728iJtNnL4sUiMKCDuEKDtCX2wY6wwK5JpKy2U2Wuag0lch0ic9cXfFFuNfv
TLQEnbu/WDNFRS7Kh9C+fAJ83WayCTtL/1cXhJs5EBPQ4L8Ar3UXt2ywM85m1z5h
NUvV77sq25elP9yTOYb/dBXC1VxQyNin/wNFOgQLtAZahe451R0ihJ1/6O1RdokX
wvrUeVVrjyrzgcRO/y8qHdIKfR1OLqpUxbO/PaefTT6P41lU5gTYavbaxmZYpDYL
UMIDO1XSudWAWn18H6frTc+wxfJZKO91s5P5KFSPZsl9lBsA9f09cHCB0+7OpMzf
1HEyZ400I5bbN2jORb7C6MjPVyTW2CeT0VXfpsExW4f4kTRWPtbuUKhkkpUKLgae
JPp5fgbL+FPAT0PPUuwzh/61K8Gm5+Mreaurq0V1zY34rB8kX6gIqiIiKyKwucnl
BelK+t2c/yBLnuUr9QZogD+6MUVWCDNLdKy9MNATATYGf7/yNp+eROADY2J/JISb
WfAEhbhJqqzVbMDWV26t5cOoYV9FTdI6OZhEnfMf+vAkVQZ0XB4=
=ViTy
-----END PGP SIGNATURE-----