-----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/jalu9uZGunHyUIFAml5angACgkQu9uZGunH
yUJ/4g/+Iekp9/njvgblU88wzWl0ScfrKVZdIeI/bDcLC1GX1KMNtd8Z/0/7Fd9h
y/5KyxxDsItSBBBp3L1bzvi2aTPrtEycGK9QwXXqbCyPD5djerBMDOidqptb81+x
SGQiliUDaV/UVBAORyNb/9V1WpNWGeC/3Wwu8+zxaYBz/T0vEK7DoFYmZfhvyoHf
KBDELdxU72xMknRCJtWznwTSBgrmm5sEIde49QGJdBlwtmClyGnvlB3rZDRYAyRg
TotQFWWKVX6GS0JXVJvq1Xl4X7RB1fDbjdUbjwOhEsf/47KsGbYREKWOcCJo2KzU
RWnN++TYf+JI4SutAHc5mTTFdN76OYW0kZfvGoZsvCGpDqnzYom4fTHC/dYCTZ5w
eDbFcWickvdv2iRCGFROaakR5p2cfIb1DnqO6+G9p78Jdh2v0vTA+f4g0HA15A2n
ab8H0poJgrkfZuHU5EHsYl0c2pYy4KyUxc3Fh+fSNOKmZMIckhOPBF0407GBg0FA
82i0e1dgTSVBGaf92+Ja6mN41uYSjifok3g3OorLSAv6O9spL9U9ozSwEt5NjdxG
LthzuGfKHNJtSx3CZirEwHzAJfdfsxYyxwI+gUyfIVjU0cYnXkB4DN1phCsq40tL
S0c4XC1Z2eCxkDBzITzb9NUmrAg+fwdkLWjTxHd750//X+o9Y2Y=
=4wIv
-----END PGP SIGNATURE-----