-----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/jalu9uZGunHyUIFAml9fUEACgkQu9uZGunH
yUJ7vRAApMbliNOTlPGi06mx0KhN04+GWw6sLZaVMMIAQAnuwa2h0d15PFHNE2kx
k/Ulu9YLw4+uIXP5qxPbDFUVhLAo8xdI93cOeGGNJMsVbysmFfk4XJV6VpXC2e+f
/MVVLappp7TpHRivzGs/GSp7UD8/H7t8vG1NXXifdVgzMapg/TeFVZrDmueiOfyB
JNPMB5FSn7Soj/HBDGZeLuxeLszCtReJ86Bj00J52mMmZBhGJ+TZfL64vpKZfLxG
uPHJoIa88Z2lBEjU6PrTtYvMDT3frVJGhmCgY9QhFLzRWi/bvGiFQpkJ58/+9P3c
sL5w8or1p6+U1IQ8z506BqqXz5TchJn6atGU33EY0U1mAYAdMoMa+LdC/Eb6YaHp
YEx50FR9Fmks2HeVcBwnDnRaTZOzfx51EW0yVugGRzSnePmSXsBb7StpQl+sHuup
uGpZFFLQTaEbmVVeXGgbfWhmLAcwtwHz7C1DLGybx9SzMNlt2VenRTHWiwz7kwti
MsEMgSecMy1yAMGj1B2iQ5vQFmc1UkLyuyDLNS0H75hh1El1A16F6FoeAr1qaLnU
1oWefJrsRIhZ2OyFfsbNbQ+D80xqxkjgIzRUUrdIQzvSGRsiMmSbODUWEuKmEh1Q
OWZzT/4LHNTaAI86S5P0CjnsTrTwiZzWbCwjyYkQ6f4tgYoUlY4=
=vEQK
-----END PGP SIGNATURE-----