-----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/jalu9uZGunHyUIFAmoL3XMACgkQu9uZGunH
yUIq0RAAknDErlfJNZLjQuQnhUQcofqXm95XPVFvskCSUtvHb2+lonHq81RB4Wqk
lMRrPm52D7SniHZZhp3nG7/5A8CYMwN5+2ZzYNrmmHKTahXoIs0Ad8w1jXHaGGiE
+Cm3utQcYL43Wzb9abD9pzEMi4gXObXwgNK83jx30dqQnfQSMBF0hpO6nhnWlRWm
nXASRmc7EWxTXF0opbP8uCSBLKb+rQN/xWN992XcdKNIkTSBCdAYaOS9ODfCkbIX
qlml4DiMYmZouTfZhJlknDdz5Vmd0G6/y9L7/l/9FSYPZ2JnAIXcXfxARNtxXceK
siwRlyuMyMlm+KfR5q7Lv9Vc4NO73WGs25n1D1y6PviSeJoOlaKVI/RnNj1qhKP5
18U7L9LYyYIU/YH7Vpv/NRk4PEf9f77pspY79tyynzBKA1ZOFcZv4axYfNLjjB0j
w+MwNQs/chtXgtGRNXbbGevHrQ4fhQllwQT1HNlx1y9Kp+vI5cgTYPg1Wdzv1/6M
MBuA7Anb3na11OQxDxVqOkZB9P4Oftx6PB8SU//e7+EfaVyYB4XWL+UB3vTM/xRA
WmRG7aqxpv9xbshKBaNt9lgzGg6jFdPb486db/BRgixJKN/5pOza+OrGBB47ZtDM
GaK4oyWas/afhWPTFnDgDm6B2bExMkoyo7Ytp7xhwt5wDgV6GVc=
=dH0f
-----END PGP SIGNATURE-----