-----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/jalu9uZGunHyUIFAmm5hccACgkQu9uZGunH
yUL7DQ/+Iqqa/zVDvfzlBmYl4LT+C/9hP0j4Or68JhwCjSxqlL2H0IMR2dUNIllx
FbYZYsGWB8fbvHNY6YgA8gMU0avqD2vpkzhXk4/CZ888710Z3aVlddDEbYUoov2Y
BSV/Crn/NjMUo7txj5ANLZmJZm3tjCQC30DdOpxv2Vthi8qpNCWeanrM/LzsZ0Yx
FObIrxtLD1Wungew0TLiI29GasVjLK7qmvP7IkzeVfDowzzGIETegjHLgrA4yTx2
LIh+YNc/WH/z/i/CkFwnIqynlSVKZpZ7S2uPdGSkvshmXwtvqIJv/+NU+LYw9B7I
VjRTPqcb4ZpxQecUHNUjcSBbfkCM8zI2e8Rr1T5nVJCrSbI6YF2uazWbLJ+oGfJH
jhciaTNxfA5F+A5k3eQZaaouxW5hQMW0JGyVn7CTTKCPAyWenlM9OMhZnniKCLvc
pkXLgPcOa3Gc1jDqD8dXupPx+RuHxJ4OnB1nNWNFv8042rRNYwqPtoPZovZ8WVBe
6u0VOM4xDA1GCS/eJUFOvaHlvz4/De8P1iEXj5InP7BOA5I2rd8y/BAnMyQUvreL
C08p+zOsFqHIQ488Ujp16CRgCQvskAyT4NHHRMO6fpyfSEB5pB4F16iF6PH2MUIG
m7R8eU3/SC4aegAGJph27CJzMJjB/mjMv9UsMde/OEmqqLxSqgs=
=6JDS
-----END PGP SIGNATURE-----