-----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/jalu9uZGunHyUIFAmnFgkAACgkQu9uZGunH
yULthBAAtrCHyCVIuZfCj0/dj6NIR5ayz8v1omia3//vrjmrN5BqATGNLuGZ0r9K
b4PUE0d+DfHMLN4aYsBsM42xJmsMLxY2c6ttsXYegLveRTYwZ43mErrM/SS9ry3q
ODCI4uh6U9l3ry0DVhl50TuxleDlw0h5KFIS6+OGqt6+IFAzjxZWVhjm6JW7Z9hG
DL3GJkTVAuB9re+TQXzZ6Jzi8lrPQHPMn+PNDYS7LTYHxG1Tw09j/f6GCxa52zV0
brSX9bo+XOv2M5vCcN6A+DRTpY/WXFO+/eiILgxyV7/FkE5yvVbhSTR1p4nA+NsA
/yyLwG2g/bnTGnnVWAkzXaN2cReizbCKDNTSF9KMeeIo+7xjPJWp6m0K97SP5l1M
opbabE82pbTiff6o3188fbK6iJ15qLlhPqUoW/4MQMhD2g2f19ahhUy7rg4Ef1DJ
ihRwZcjCIdQB0mLZ2Xcwcku90wYj3vAUzqDaQRt2+dIVrwcnRL1wVS0VPRd3GLrP
pXRWtHOxYBa2n2t/NVyHaOFQ/pBB/57uY+Cik++nAd7zUa1z0vKf1Ae7Hk+pqynB
5Mq+Drez8tCT10OGdm197eyUKbXBpnDIHpZHk+cqaruJYSeO/iTU/wHLVL1YgXqV
Zqump3j5VQ0q14wjL+ZYObT3CEDw/9tLElS6u292hGUO8HsORiY=
=lLan
-----END PGP SIGNATURE-----