-----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/jalu9uZGunHyUIFAmnrMikACgkQu9uZGunH
yUKu7BAAtwplSPVOoo5D4f7hAh0/zONXGXSki9OpHXHhIIAkjqPhgisVFFeFuKbG
OK5oh7mrfD66eVylHRw9Eb6Prfz6YfQHYIniWrvMIw/WQkGHlLMAj6sL1HRW4UFH
YJOKrisnFdpVsBtzlZ7G3r/EJXRwLXIrlIu7NqoVzS6pn+c4owFOKE+ENtAGys2w
YIY4dTnMZX1RyvGt47PObftH5NsJazlUNt+aMUS3i/qBMeuCg7d4t91+nZIl9QCE
Ac+6WcbGaAlURe94XsGZiZw9WkaY9aiHPWXl+g7KhTfJAGfLyBU+vAkyqYl+cxfv
EiqG81njzYe6h2YUq+pvtL6w6QwqzhuZW5hitG1kx+ndkWnSBuYRu3gCh/Zp275m
s08DT5C89hhyatPJlPzfB5MSdwmDZkcRD+uRUdXml4A6pXu4digEE1DT0C5CTRsY
wryIntKfJ15KjWAUmScgh0DZP2mMBfT8IvVlFP4W5AT9Wt8rrc+4QLFxTOtazsyY
RvhC+I9PQS3oU+pvDbugbpjGO8rQ2j8WD0nUdLFzp0ZyHvPOY3lj7j1IBKRCvbAj
REA2cL/pha87xECvyp2M93olDOtRhdGzHT3RyzHktFRXUbFPIjp9iAV5csvrQ/EF
8faZxInRlfOhKuRz10X/U4Ag6CSzxjlb5+xygjWgTEBETwmRzbc=
=5KBg
-----END PGP SIGNATURE-----