-----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/jalu9uZGunHyUIFAmmhYFgACgkQu9uZGunH
yUKLLA/8CvtU0kcQLq9vfU8ipzDGmFZHfEZE89oF7UcOliwyDbCFsdYWFNM3SMbG
QSQDNrpc7MxVKNGKgKaudHMA3SdpyXniloNYVO9nWURailEvJHCnxPAp2iEJktis
X24eacgT00zSntbeBFTOorKY/vPEiw1NJwjrirxEhEutwOpqbw+fr/WXoaJ9mjTr
6HM9EF1l4RIN0jdpW+EAmr1hCtAALZ1DU3AP/wpbzx4cB7zGab2+hjLszSR1UuZI
58U/tjRxa4evxviHFXLXCWSXuAwAXkP3hwkmVl1//mUbf2kZMC7JCKXGibtASGc2
sUFn5pjfB9gl6hv98IaO7OWxoKq4ta9tQ4eXM9pClLRVcdcpicXUqvOS1hPryWcU
3EVu5I9M/D1PT5M9HD8jPSkEdCQVJ/PS/k790cncgkBxG1KKckfY2o9v5S2glWS5
9FDVi7p03bVJB3RD15u5pjy37d/hpr0/mEl0ZRMbR2K0pRF0NjA8ybsfQGXPjIdD
TIks22MGQDzNEhTCqgNZJBC/JicOYnqHZXtKDjKiyT/MsCjulhqAlRRpoGvFjLjV
y0gi4dTYjHouzFStwaWrGeO7XoIwQZotofPOOUl6yaqNBwQZ8k7hpYJoF3eyrQ3d
9fnYlHL3nB4nZHr54RX4++03vUniGIKbpRrVG7dbJMjFEdYX2aE=
=NnnX
-----END PGP SIGNATURE-----