-----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/jalu9uZGunHyUIFAmoXjGQACgkQu9uZGunH
yUJYzhAAptqpnyH+eFASdE1888ayyAG1AebWI3L9z6N8HDJvnQaj8iUfX/Edyetb
lXPR6VJOyeG69g8Sdnb8E770xbctVOUXdwL0CUcgRZSHFbN8K6FkCHiRBh3GaM3w
9DxPXsqrk5tJYWr3N6yo0Kd69Lp1ywgHMZ7sPs0+GDMShh4BKBnGk0CpY9NRQU6v
lutcB/7YbVCdttb9WvJszqMGCUpRNbJTbgv9JuZC3t4OxV3O1iFMYddsP2+VWke1
O6MGAb6JpNWZv6tx3KNA9t/lRyXgNqz9MBnxhqWbF/4AXUErDZpbD5Sa4V+8PL9X
Sod2RBFLq12DSzUH9AScCFYB/pw5wI9r5pl/zMwtUhorTBOiBG4cDsCOLCbNyWSZ
tM3d7mPKGTjSnI2C57/TyLTv9MqnUOcgXV9Y30vXoB5W0VRSRUyXjnAjdPLNrTxV
4dQBwhEv7TD8wj0OzdF1ET/V1zIkSllz+GRIzq2JzKcPOurg4cfTD+HbNfoNDhhW
4RbeuekS7je4JuVZpMO6A2SWa9Selu/EWStBvm6rQeefcWVahYhT4Q+eWM260Jgw
0lqy25PFzi2Vvo2K6FmFB59MRrfN2VxmAg4DLFs91SmjEaltzgJYiS0vpWz336LS
SqN40H0qeKFY2UJaOkPoryRxAyBlKPlIRlr8cGTS+hLXTFh2CzA=
=ou+K
-----END PGP SIGNATURE-----