-----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/jalu9uZGunHyUIFAmmAnsMACgkQu9uZGunH
yUKzfg//T8imgy030sXttR0fEHaKTi5KkNEDnMN8YkRYHwJh+zXRMoQDj80DDIU2
okA3p6Re6wQ4naUivVr+KwIgmWRNwolAQmWkOGG/YEwJWx3X89ok1GTfKE/iQp6N
WwKS4A9FWQWRoRfV/NCZzbRijHnwEIQKEKtTdxu0HFLHHUKmedYwwC8VPoL2OVEc
cqVx5Zz2VeepzDeaTPX4pbh9h1mnoe/kFx1juWcZdkWVlebeg1zeiKLn9M602f49
whhwPtg6Wpnx1lwTgVjlb5mAYwAgkpAPutGm0Rf1MX8EosWB0Y86WVuYjGsWgtd/
Jbl0oYycXgFs6SPhyVUUqnBUIJB88oVaC7m3eRj54wdnVoiIyB95kVgOvRs9cEZf
1+xIql3uYPszUwsyOgEhXjCt3Sv0baWnyES1siUetgazTfgaq+43ZKreu9TpRqwr
Oem5EQvpcJMC+//nUQw0UeMcrLDZ+GpEkO+UXbaZy/nXr+7IeAClqAnvgDqZkkJL
tfFh881XaXD9IhvtgFB6V0nzFCvY2TDV8/NhfoBjpFUxDIAP+s7zDKYXJwn/bh5K
8X+rkd0MlNayoBUfouE4LmF5i2cVAP7FQxixfTRf9Y2KrZNgWqcbl1gqLahZVc18
IOVy0QUTOyaLBLVA6eBpASQdAviYAvd5i4oKEsvUA+BvviVYcNE=
=cLLR
-----END PGP SIGNATURE-----