-----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/jalu9uZGunHyUIFAmmqYkYACgkQu9uZGunH
yULKdw/+McRJnDCBksSpGxQPHGsGy00z8+cADid4R1zP/z7QY6Nf3Xgwg+9zBmk2
i2k8P+12mFqs+EKlcFKdTmWZ4uRnCrYvJmUFYGh6BLJK1mE6wexmyB1vYWitW3M2
gHkRDk6zyuRMpRDjWhcE8iaEg2pOD/86RGYEjmI/MbNO5mXyGWCL9fJxHQR+cXIP
xly5MgYJh7Dh5l+WRy8jixvTbGq3KcPqhjWu97lsdN0XytKT6vUh6Qkt5+cKdxkr
64Swx8vXuZuM6ZJrBgM096V7PLJRhg4XOUyAOkJzU/BEswI02ErFobE5xPyYAUv6
N+utfa+hCEdMqSP+j4SSZ0hm6IzYO3NyKcutjmL/pdV0C7YlbzmmcEtPHd4Bl+J6
Zgir6TII30t41DYaZyjNQy9U99HxVf0vkCX+Twmm8OCFVVKB6RtuYzqFcFqYkodR
x3bwv4xabs0ECi/QR+lFQvYpCend0pUZvRhd6gpyfgAItP/tGFU2SF7m6NreUheQ
zDIsww7vCsDSpfct2JcxB/TG0QE5tTC25qValytZiSxPy3HEnRvTnxUWgaDcAwOw
fyvhh6JGn8bb3hqJs3U9ezW8OlfzIiqq1+dapS/RhYWZL04JZjBWF+BCogyYrPHc
WCstxIy+YEVlmhPmk8ipmRhVPxfKCxcIXIX10NM+wQ3cDKa7rgA=
=nmFy
-----END PGP SIGNATURE-----