-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
05a39db99bef224495078c24db168869
sha1:
f72529f5f4831038b3f783aec8d5207175c0283f
sha256:
f37be6a7a14e63d2b44f67616c070b26b71266a3122c8e80cbddcb26f8cabdc0
sha512:
b152cb08a2cdd707284e19e5d50e22c2e0f1d00fa4aefa329c5b30fd7024ae01201459dfd77170f9f4f1f4c7ce3ff02191c0204cbcf55bf0e4e524e7f145b70c

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/jalu9uZGunHyUIFAmpOLPYACgkQu9uZGunH
yUIYWw//VjDXZKuLlHgDlcHUKXYRwi65KmLPtWpP5jmOhxUyHq1skUBI+205fBNW
XUZfN7lsr83+YkR84WyJhI5BZUnNKCGSwLY6Itjv5eSjJqEibL6NkqfWzzGn1QdE
6/O4vldwSM2+2EOarM1UZpbtjdM8ygKqPWUZohBKUits3mn65qyGS24D6w7lhC8P
2HQXIko2Rc2BJ+XoKaUd+tUqKS2DOekoT8Ebk3muhJLOSCymdFpbQX/lwGczOddM
KY+jLrbBD/ul6PTdEitTSEswO1/m9nJt1BLsSNSsn38dB0XGd3/yBVOjUWfJrVaQ
4v8qzdWUj9f5jwpefeFEvz4tAfuTuk7W3rw2l0l6C5SxwdU7Xe/0FJQG9aB9WmAg
xu8z7Vymy1qNC//1J3gwWyFNXvaigGgllNagTuEllyXRDL/XH1mOUL1IJNYCGCgG
l9iuXWvJ/rHu7MOA5CK/evPLHecPJywrnHQ7NG/jv4+8ZCM/BDfq6i16bSacU+MC
w1pGzsEsuUkQn8aC/G4JdFy7JUv19HzoxaMA5GNsGQIN5W/rgKghIMwCe4wKwcDJ
cRyJiAEr4DOZwatTEGlT3owrh5HITV8l9ErtJ7uqwfWCPN5yA8Vtv4y/EdAYKTf7
pBKvS5g2JXnolKQm14MsOEH+x5GrrcvefFjZbagalIzGreTv7Kg=
=681J
-----END PGP SIGNATURE-----