-----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/jalu9uZGunHyUIFAmmo3sYACgkQu9uZGunH
yUKCIBAAnT3IhJA9N3TyHHbagbeXGajggjzTzJVH1/u+FtPYiTmocr/n3zkwVBW6
G+3o5CreyCclE1VHS6JyfTd+Eg2Asd9XJxpjDepe/l35Y2t2834X7EKSLrNMn38o
v/0WPDlCrq3sZL/bjssO58cxS6WgDSKqQ+2aRnr3zjjGYCdTiaLW5/c6QFYX7mU1
T90CAIeh5NlfF+gDEgmHNjIl87cmXkeMeGHI3hRtE9wgN6xa/YsvpBWaL5dDPR0K
Ht1tJMXqTOOC4fEOiUW06Vw2TCLy1bWfMGkxe0DJLCIY6ld+NI5Iy89Ebwv9CTeA
4MVgWy2NvFwfpMJQwTiUCyNSTPtDuXoudA0xcW5sXIQFxFrAThBGq6fQeQKAsf3V
I1qrCmqPrTyyReC1yQGnfgc3UARyNToQ1JixS4C9Yr167xbOvkV/TbFGcfqbBRZU
YgbLsDlUYhvo2vVIhfj/V97nVeAx/L87KZi6o/LLI+/NXkkqthkQgM4SbyKb/uLt
ELv2JFNnmk8SOe52UPRaqWoQepuRWLRSOmDvkr4qvuXEnGBZQ2C3BgAoYO2q/mvX
mIUa7EPKCOg7JazZnoDhvU615ixr/VFePYcnTP5v5wIEMg6yT5CADjTx23yk9rrp
biNcP76mfBRtGMAU41gPMynurC7/0lsUF68G1UykKycJdXE2t7g=
=ZMH7
-----END PGP SIGNATURE-----