-----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/jalu9uZGunHyUIFAmkm5qIACgkQu9uZGunH
yUJlbBAAsLLwYNH8amaZ4ce0gYeZEFlgZf3YFrjQGRKIKW5ZFlUOLrYKRz2rBQFq
MZA8490DdljvrO2YpVti0BbuAtmGylLZBmXEpvrjXHD7gDm8FGuaL1XOfC0ic/r5
dzT4XUQHSjREWU9lb09B+qPQ270aLl3yzyPpiwYrCliGZC8KoiNoIIyZpHAgBHmp
t1i0Mg1raqQfJGefTSeKQGPTnbzP7DG1RSnQDB+6wXuPAOpTiRxejlavtUbgbU45
6402c3q5kJbBe8AbL724THTDqsqNfJflfy6SpS81MXIFR1TTapdUt1rK75qgIjWP
6YqoYHm0B0lDSd/Vc010jOkXX6CSbz97ECtxrTgmnJHMAqvCT1xECAnYfMRppvwG
I+37USLdvd9PfUNIascnIlyRHhOYuSxp0M6lBOKKct2NpzWbV16oYNLM5v/nlTbz
7Xsn2hRtyutYgJ5a3gsjxh2Shc3Vz2pSQNcIIKHBJMYCnsBGmurivVmTn4ONC85v
9vzd/o1lscjx56zcvqSLor7o5dZ4PGSKPmOHQfWI4/XTS3IpfCbNj44WWS7XJTgz
Z0/m1iQQPaoBjfZgeRVTyfpDuF8sbYMrkOJGW9tMKtCouw+vp0LIfScAjfcMyvfg
o3C8t8x6JxlND5vWvx1LwSsrRqCaCF+G0KyovPb6AX74HrhbLnU=
=9kN3
-----END PGP SIGNATURE-----