-----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/jalu9uZGunHyUIFAmlnINgACgkQu9uZGunH
yUItcA//S3h8NP6p4WgUPSN5qzU5BDqOUbVhYc9cKY+1TmbvcCyBw0OCI6Cw5qvy
cnGGmkgVtdAaQ2Qq095FkZM109Rdgh1lbZsD8iNCZYIHmYsVSNXtcBFUgKTbSlj1
Amatk92yrb/ecq6UerWg+dTyuN+VR3YUkvXIUblG9XooZ08meQvHjAw6jXQ+1Uhb
Y7NUBffRMZ5y2SuQ0YPBNvxDweoGTodiLHwvmmTkvpQ4i+tpTEfeB3vTMmctlNVl
dHaIIWTvFYF3BIsmth5/y6W9HkhHB75YEluegtkgQ3rnO4ClrWHPmFwuF5fc4LCf
/RykBece4L4EALpISCDKuYR8kGnemOdnQxufs063xFmVlKiXJfQPQ8PJ9wBYzI49
rel4nU2E+iBCZ8/uocw/rZ+Wo8BTKFj3vlJtFAV21ukLFs7NfnCiten8leFSD/Vx
SGEu3+3ilnqCMUxpH+xe6MBSvSzuoFoL+lHcgYpVUbvB5eIGYAwY4nhL4oFGi3IF
RWkN2x28rTGP6G1RSAKmmIsja5u9XS32OuVShoJACF0qYoU3f/UsQzhJXJBP0mFj
n0MyOrxmdYcF8NsLmbiqc4OC+XSgumH012kTpWg+YOFHMWC8Kp28WuIkZhCO1svp
Tl/B8vV6KDEUVA8RIRDqqEmXAFT8kvdx+OwekkYWLkSnIlk0tb0=
=8pZz
-----END PGP SIGNATURE-----