-----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/jalu9uZGunHyUIFAmkdoEoACgkQu9uZGunH
yUICYQ/9FRmPDmOAUlmXMWAu2X+oitU89lg7gONQ89HnP3r2jSnGgF8Yc9nxdFNr
7Ux33mw6ZdfZG6psxCAc3Q0K0NbsRrPiWfr+cq62Cm/5q2D2vFO7tB0Qf7HO/8By
1ZzeG8m/5Y+S+THpcSEDMjsrCqIHNMpXlP5f9Gdfgh0avD3yh+sDxdtsPbXeQ8Sj
d5T2qRyV1Cn6Ml+FxRpvYYmJ1KIbG6xJV4ysUeo/4dF606X+Q5fi8i+Z4a6cz8hY
gHv8hAy4dbQdAZ7NeybTaEBplaBL5qBfqGdtUSFHLkxwths6XDGkDHK7tRCuqfSf
g7SAS3b7sCm7gRp9vjEDa7heoM2EG087pKgVf51fZ98GiWRzmt4mKMIq3V6KgU7/
oH5eiMOQuCBP8jeGw6b4hAEKV4qbOAfyDdFxEf4xxJmOEScZXS/0zTblUV5BhaDF
TZ1LOt8RN4XSurEUqOVizvg8W/Pucg0VSUXlLzdah2Dd6Zrf7zYqkNm58oF/eca2
daVp8kwQa3vYHMcbzwUCm8cdBDnY1Ehc9lI7A7W7Ve2lgUQXgRtykOr7K2ENvjLT
dbvmmFIvGdfO1iP1ONZR7YlU1XRFmWO0v7kSAtqhj0bibxwtZnpL8bBczuuYo89s
QSVQbeAFsPkxcjRgHkbrr8yWOSHbCJT3qI2AAZkt0Oy1IHNCiaA=
=d1fS
-----END PGP SIGNATURE-----