-----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/jalu9uZGunHyUIFAmnt+X4ACgkQu9uZGunH
yUJsww/8D0z8jcxqPUycekQ1Azh/sTvvJCYeosL+4BeeohzxkQAs9x3RbLBf2+US
cCorzQksocd3Z9l/Xh/NPPx5iYCz48KGz5D6cQnFgRFH6wKfPhY0IaG6d9LfVpu8
26ihLGGbcHjRsZE897kBoTw8WsyDUt05sYoUspjJJjW0+r9BXQEklTp7dddNHE0R
0Fmy/xX/6bBUyQ+fRRxi2hjaCMkuNB+1+qlJGAjIGRY9hoQgA6VpQULurkVR7eHN
meQLzIIWZcJKKD0sdiywOBXt1boDntbjTbncv/ET/Z3WKpaQi2G+X7oJxG6NfNCs
p83XSmbHrXfUVPMCNqk60Gb3Pnb5Hv9AbkK8C3vLiqqN7E5B8mwCTEUaj87lhqPv
kzVD1ZTLrU1Ux5Pum3Osaj5NUBd1BLlmArrFjFcTBFCpLjTamvLMIo59SxjHT6Go
VlzFQ1WIsMaJfjVdN4xjQ/rB50bTiyBIMgpLLs/Il6T/Xd8sBlwCvexAYcoSW7T6
mTTnot/uOLvLEd69xHlIoS60RmxOg+BJ6AFWcX/cIp9k6Fi4lgcH48wiSRCOZJpK
sdmoV88WLFE9LrsoWGup/MPYd0txKLTW9Id/2VukuJz73t48Z7tp4mvQN0tChIuJ
NsNlx1wDu/2d85YRX9N14keUrHe/S/L53ckeu/701NKw+ZVfClI=
=AO7i
-----END PGP SIGNATURE-----