-----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/jalu9uZGunHyUIFAmoGF4kACgkQu9uZGunH
yUIwkQ/+M5LRDF2a0cJlIR1q2zbhWim0jR4iW8sUYTGHzfxpOsHaKiAL9TjgAeYc
AgViBL1GwKJeaBGKgKdtbS8hXGXmARHK48L23rnbZMhYkkYAuZCAWOLtNcPdxOmU
PORvD9W30wYB99s4pokiRnqBTLjqTef1AVUfHmm8ybUczwmjjCEj0WZuyhmtyd3f
+2Cg+wrLi1L1s9iL92U7eAKmW6WguG4NHR1Eh/xhAKx4aSimwlF/26IM+IaYBHhE
YS8mELfMvZ5k7cQQDPp/2229C0haBZoxbqBThSnSsLusJG+UnWK40DuZAiJAk2sJ
ljdNrTlR1A8zTeN4l20qeieIXVP2m5WD0oDTd3Hx6541inkvre0v0a8Q4Nmyr98U
o634rwg4W0YSC2NnK/wv9F09QK52wYIJ4B4ig2PdxEFARNbt5scIrpQckGhKvnIM
D8nUCOpOzb7l7rlsFqFFH8+iun3Or6pnLXh/ppMu/T23tH3yWJdf+LsTtY19PFr6
n+m9+nwuxdKWKbOMWWmUDdmcq8156T73TIpaVjM8Mci1c6p4QVgSPFVs5UU6ITVd
majPxzx97cBCLwPCzcOeuFo1ps3mHhAKXdOy85dwhP6cBf0pteAqXhHC7QNzuLtz
KO3V1NjdZTfW8IzElpk3gSaOSt1l2fR81WtGkuQ/8oAnuG2nzQY=
=TBbw
-----END PGP SIGNATURE-----