-----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/jalu9uZGunHyUIFAmlCgcoACgkQu9uZGunH
yUJT7w//fHX7WtplXAx2vSxCKLFZWzyt2eZfPmC/BGi8BaKddR8GUqlGRI76XAVV
WHnnIozG/3fQn42O3gu4am+t6xU8f3ochBIVO9DGv9eOqqs9UlHKe5Uc5+04IlyL
GMBp2265jNcZhDDN9vNXD3NM1F/fyYENRJnJ6dLaXUdhQhSwinNVEjVzdaAxJIhk
V9NcpXjMcsfnlahC21hb+mMzqnt36PyzWXtRErAGuPfTp9YU8jq7Sgfs0sCV47ow
Vv9Wh0lnHTP//slOvanWQ2UdOv9Offbuxa65n2tOoBkMNkXOrp2S5tFZa7cY0J7O
I0UgZrY448UDdX3azSyswvmw/H9dHre6W8l5Kt/qglg4mdCh9KaZR4Eb1KP5bTWE
agE8JQnKIgzKA85llsA6olrbhDDWfOmnlu/APdukuDU7H/NaI7TEt6hr96eLTudR
aqGtjx2inMGBK/TIvSBEd2re/OHpvCKvXOgpOjAE8SFBu8yWWFW/7dEXmKu24sP3
qyWqR+M7I+vwz5Wrfd8B1RrLDRpJSxD+/VWfLrFMVEnRuG07CMX8sUtU8I6HsHu1
JXFSULvaSbPkh5NHM3yGGmkw/xge3vuJHTfiK6dQO4aQ0zqW1lTErVela64ob/KZ
hoKUgFDcrBgq7vYU6/D7qZ7uI1bbSfV5vCd3E8ujVrvVpjx+r2I=
=iPOH
-----END PGP SIGNATURE-----