-----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/jalu9uZGunHyUIFAmnOs10ACgkQu9uZGunH
yUIg6BAAipWebqMDSsTFjnLYqDfZLsdyO4O8FA8tXZxPURqKJyKjM9Z0jzAao84U
x+nPC3bJAEBzImtJr4GriBn3QZkEA4MObeJCr6K2/hj2DioOv5JZEwa4kgbcJEtm
sdN6VAR20UeuVIw3M9/++6Yuzif6MERMd9y6FhOfU1frvoIIu7JrCyN1sk7Hfslr
DucN+2hvM5CvhY7cIPv5QupYLfl2L32NhOZHUr8Iz0USJTfKMEkIugkMhmaFOezr
Os6Rk2P5Gzd5gyrzWkyI7lAVZ2mI4m6PIje6s9OtLFOL+F3HIRCzGLg9vRNXRXPg
IyP0cwSlZzMYiUX/95x0P/oLurr7XtW2CIbsCIhokPGHQ8KeZDL2wqD1LdSDOHV9
3brZomzLJaNvTZsnoT/0fVtrlpYzuyHHyYMqIMSwJOTKDbPT34r6nednb+T8HSdw
Cr0NEtImMQ9c/NkNKkHE0J9ni+p4a840MswZr+GjzU0OKXsMOs4j9xlgAmbYtHiA
HIY21FbW3aPUl5KEkkBi03p0iLkhGaZvFYLbiHTazNWCpS+b90g8YQQ/aHqccqP/
jGDCdQbskY1J3mcwWF6jyMrbhFCZYDWcaIJfD4Byr4JO8Ql8qYpjXz0ockV6s0TZ
ITYbKZBw/uGh746Sby+VLQ1692u/8ZiTOMtlr76Pm2DDcmjhpPg=
=Sy0q
-----END PGP SIGNATURE-----