-----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/jalu9uZGunHyUIFAmlrF88ACgkQu9uZGunH
yUKUeRAArUZ/AZD6Q+3Oa4aIAqOV5x9uWcg0LhDi21/7Z3b+Pkrh3slkz3ju2TFE
4TQPgzWChVZVgOVdFYrc2z8TI2TzTQd41JOWB0DVsS1Wo8j0fUulJQo8664sNx49
X9eA0bFjZjHckschRV9KuUjMo9kQvw+4yoiGQcm7a2qtmsR2QrYWgjyB+60M0QZO
k35uJKiG71GR2bbfrDiqodC2rdKk1wJY35ZwK4vf2Gu4Gp+4ljyJ23nzSqhMWaWh
p5wUMstXRmQt9RPBB8d/4j0W/54x4AfvQv5EX1eHrDUMLN4+/L/X7SL5/QuCPURv
b0zOZ4T6SEaV3vDZZbAlgX4ISfjpmuxCPQcU41JAWTC6seWSJ1IKU6lTw5e78sEU
IGXhBk4n6SFdA6r/E3RpwMPoW5gFotkPRzy9eiKk1xjnsp3GgbHigYNQ2J6EoTON
rRq9FU2EA3chIZUWifGfHhXcVvmt9pMAbDSgJXHcRE5fAE1NS+NOfT+4L4l2xSSK
089DJK12f9ABQLJtCVFyiLMffHRFezW6OC0K6hr+TV8ksdwQhNMiFiE3BBPvooLM
ftHB9ieDmtkufnEbQaI+HWW/AXHns377UdKFFd2r02+jdpXWK0LKrMJHqB1dF5pn
4HMLe4Ou1Q8gfzo1awNmfaCPFkIA6siI3JQd/y6YCPfzyM42lnY=
=KzOv
-----END PGP SIGNATURE-----