-----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/jalu9uZGunHyUIFAmofpnEACgkQu9uZGunH
yUKpARAAhWnB39FCgMjCzeYu7C8qO87+hUEGYnw1cf5xTqmLSCMuWzEfUaWO1g8i
JqWjhOrn97QoIWYGfPsuBHBT9zMkT733nmtC2e/9EucSZKML22OjAtRvPmZy2svk
m1xRMjUafCUBG/Wa89clwRgLO48GogNT7tUlS1H7SDcFsJAZI9ef5+WqgsQ54OD+
H4lZip6nTjFeQ9dMzyF4rVPtGIdJDMtuyWVsysGQ5+ZAa6i/o7qCNhtSZYxpr9FO
z7emyinEkW4AaEQNeGF1gfSRzFm9riKvBOht4rup34QL6IRVa+3QcvB+naMgNjKf
j/WfpjiYTPUxjI2dQhSYJJwAfQwU8GDHcAHbKnKmGEf3i0w901+2cLnA49mTCiCB
acvzr1mqoKSCYtjXt4CVPM0QNFzGFsvqKDjLtOmrIltHvwDv7Gjw8JjbGtdGjsCd
95fA4mJSotWHjzqJfPt1TXKlFSVK4HPSalLOJuZIteYkEz1fZhUSTqi+QsTnDCOm
gpD1w2r7IUVwW/unXBL+cICoo1EC+oTBFg7ZwrnFGu39AMQO3I+KfUV5CEqvnbJ9
iCqT7B3uZFe+hexWxLaX5BaLGnzYUb1D3LeDtPbkpZ8Q5YUAiTkMLhBwD87/mJym
S7Lru6p22NkkA5n5L+E48k3Wwm9ZcL+BHKTGqXf1F/HV7kKlnUE=
=GKNt
-----END PGP SIGNATURE-----