-----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/jalu9uZGunHyUIFAmnBE/0ACgkQu9uZGunH
yULbtBAAsV2ayoWOBJGnphvA4FoSfs0h75pEMNKwlv8DKSQzl1wfDyfzc1pqioyY
DKznB5lZiBsZkPg3BgoJ/ji5zOnXE3HPFuXlcPuKiexmtyJEp3pe9VDuenGlL9j/
HI/XT8JyXWpQB109WB9AGnypnGOQmYqZeAtw+7c5c5evXvxQZqMF9aOzUc2yBrQV
fcbdhyXP7FHRdV1Jp4MGCGFSdqihaeuVpRcv89hoPdAUKqkyLYEabk4iR5YYN8Ha
ldynVgX/Fv1T25OCZ5FkdQj49U4m12Jc1x+6u0H2C+roJowiHPk1K2+tYrTcSZZq
E2R0BTrkGtaAx8wH54kRHPEprWVe00o/8TwAnd8STWykuYjru6AZudZHJ9QUQmTl
ltR/MpjqFOtGNl1eIBlb3hQi5XvLkxN+/Y0OYAJdvXNxQh27bKlRKyfXFJkbghlM
yHk8Zbj+RvS571Ippd6dB5+I9xYnf3OdECh+Kg+rPQVIbbaTEW/fqHHE19953FZ8
m38uhCmjRL+FpS3JCopu3vRp4mxV5IuaJBw9oi0TtXqKwrzAgiHMwPCdQBFZIwfe
g1IXjxLzI957M4wEJXuQGzGGRO/OAWS8/SC2AUqjVF06mtYlH2pgi4soesmQ2oYh
GCxMOtp4LDVPYXfvEUE6GVQIKm3Bdy6LIbKs9YCEL3y2lbbZRLg=
=WPV1
-----END PGP SIGNATURE-----