-----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/jalu9uZGunHyUIFAmk3i0cACgkQu9uZGunH
yUJ3yRAAoZmnlquHQEeDSH5BID9rF+Qr9g/PcuJQn6NCibsMrOAa3FreKuB3G/pi
2DlYsB7/Cx4/CwMviSVKNBrKj6Bc2qDPQjJmibcfrd4ePbfpcpCHa5CXEDvq6bWq
Zre8Y0FPloiidbSbuPwE/1xTm12OHGt4+PRTMsVW9NOwj/wP/uXuILEfzcZfRml5
pJx56fCubxJTzQMExALbBfsUSwo/4l1PTJ7QyVHQlifWc+ymF4uzjPCIslNfOfA6
P+v+elUuCj6g4aCMiqLBpIUZg63F2/CSeAiIZYynD8H/RPyBbqG6iBfRBX4SdsEu
5AJ3mdnfcQgFDGz2ixwJ32dktbSL2t6s+W8kaxaQVCbUp79TaiAbvoE42Oipp9Bg
28Zkb1m32dpkGexAuurX0vfLExyzpjXUfVmvQEqi/b9VwAY3Zw5P49VWJD4nYsCI
08c5juv9+ZLboa4IrVpdGNecOLmpAVwNCWodUbZWbsRn9yXu/ouItTPqxZS87o+Q
qsq0eqkNHL8wtaefM+abzrze4KM494A7F/Lcm7HPJicgvFsUX1E0jVpuVG08mRk+
Czmq9p7vL/4RRp7+W3Hp8CWhfUIPVYkZp9Hutl00JTAINjrmMrGckHxc3t0y78Rv
ZOUMFvoBO44FEo9fnWDQJXUxUshbULGfTSpvQs3vm/0gNZcNuGs=
=BQuC
-----END PGP SIGNATURE-----