-----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/jalu9uZGunHyUIFAmmIpswACgkQu9uZGunH
yUJVuQ//ZyryFUxCIet1ehfQEEGzNMTh4Ru4FL6oOS7UUVEh7FiagRHj6pDhF+g6
hmF0MWv4viRFKum1IQeRSYSXYvcObAWm9VJ0zrupxJ62uyPWRSAKKEYEwHvp4pco
n1pIDnxOZnRdqEu1njYhHoTIeNrP0aF6Pkv0QJwonKZJH8+xmA+fsLXhQ+5rSPVS
prYaWh3Uw+1adTmuFDBN+4qnLQPZ41Zi74h4kJAQZ8XGyo1+hnt6sGJw5pElsoK6
N56P9vHyd2RvMnfTm6wb+GvIveR2Ss+gJ1Pl5qeK8rD68ytV/fRccCwrBsG58naM
46uNecbR2mU0jgAlM+B/NtpU91RTHb+YepZgHFWYcoXijzMZkQyqMcEmAmUYSRZv
mydWaMSLoQwHIYTZR80SQkTDDYs8OEKqKlQInh0GHA8aH1+9ITE12t2NyKRdZSfK
fJZP3zrvjp7xuaCYLOSk1PrZ1nAhQZpPqFPu212sZ8zEUho0TsxFb+0QBOVeJAEh
lh2RkS7wkbKh+sKjZ8mCAc677Fi0dNrKwVBT4nSkf3TZ9f7vgOpNURw9tsAH6OCJ
V/2Q57t0c+JHRnFuekSGmtq5xLsiyEW88SlpGbTs15KCK6svmZZpxRQqA0BSwyRr
utQOFN2x0afjd4DksslOLkEQs+YgBO7TR56cQiVdJ27+qWhqh9I=
=SlwG
-----END PGP SIGNATURE-----