-----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/jalu9uZGunHyUIFAmoQnXsACgkQu9uZGunH
yUJxXA//fayjnF8cbMeljcGKJbFM4FTVm87KBsiBYHD/EYeMw9c/7Sz0/x/TCwAV
wvhAY/pNxlQACZBd9Rhh+VgzG/zNSOoqzw/X1ArW92f/H+ye1BCLw3qKjMaHR9RB
ifCdvNqO4PcDGHbPFgxTILngqPqWQQD1izGSJ/blRjD0s5nqwyD7WCbLwWJfbrbh
NxUkMKHfifgkAwDAcXO3+B/l3NfJatp3GFYUzenf2r3SbHFQk8dSKn7gHKF47nTO
WHv81I9OVjKyWv3My7vYz2qF2013TkKsGAjfBymlOdMtsr0yZhI9X5pT0SCRp5qJ
kKnLmLqJtzTjrpgthf337SMaAyv5wedNe6c5lse0oxXuVrm/jV6xCoz4/9M9LL0l
y8TShDwfYmChM0jrCA99EjErplYBTORaqUYevl3U65+PmJnj0CJovDqUbsjwmwEk
ij150IDuLWjjo9M0VknHomari8pGJHPW0Di16TgzPaqaAh7Ao2rENOUUiOVBEs4t
up82ro4PmGoj8Z64FEE7sZQnEG0O/bUYOAc0Rub2jM46jQAypR6QnDTPLF54mnRa
sq9oQeSK8SUi4nMRBcoPI+c8TogAzsNFzm/RFkWH9Cm2P8Nn+Jd6xiO6WwY9FksV
HXz0j6BxLEeaQJFgDMImWrJ49GsG0CSDtDX3EBKNjfmaG20uKLw=
=XV/E
-----END PGP SIGNATURE-----