-----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/jalu9uZGunHyUIFAmkhwQ8ACgkQu9uZGunH
yUIsig//aRARzKCQlZgFPwJVunicI3HMtNbKgPqOLVD6sbWBnadkRkpeZ7uXPGKj
CQcNRc0+viGnI7VsmS7juR9Pu6bZ6q0XZaAXu6tzBFPTw7wsaw9KdBsmFl2DHuEG
kZCVLfTD36c0zxMMa2FJqol5up1VxNWK0urINJFsf2Kz3CZidn8zra47Gl/ugqn3
guY9t7YwLY+qp8u847SqmTS/HhmKOLKbLTayfnLvWLj30Ua8PsWpSJIy5QF1Et40
qiBgIhr41u+LRMDLxrryPjrRIGx1hbgzh0uoXRMH3jMVmRrna5lHhIlBzwbsclsV
OoFDWPhvzJSgr7gvA/OK1WWYPl669iniH0vDNZ7ffagJcSqO5Mly1lpvv2HRPlYf
q1qLzdMZJgCoP/AjHbrUf6P7GmOhRkHUYmilFZKOakhd8HtNQecV2eqnlRApoTAD
vGPnKwOx0j5PR3Y8Q9CZA6czEUjeQrrSiecui9MHXqiXjo8QE1MLnWB401llucEw
hnd+OPhoob5/KhAj06m5xCnYttCxICdVtrMDCS9KFQl2+eKeyBhzLdby5h7jubnb
6rbRZPbuH9e9kU4EzWneuERJRYuTz6BLJaf7zGFKxbRv3eSm6m022TDLM/x6nrUf
m+puhe7hcyhjsH9UW7jq4GkEFz5cWk2gPLUhHofUzi6d9ZHqGEA=
=uRUS
-----END PGP SIGNATURE-----