-----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/jalu9uZGunHyUIFAmo1k0sACgkQu9uZGunH
yUKf9g/+J1T7J7gcDel1WFxmZSYz/UkTkKuWCck7QlfDw8IxpMfj/NrQGd+4Nu4A
nKKDxXnhg2q43Rq7+kHXfFtWtucboNFg0NRZeIHNvK06mgzTFE1UrNVGR3YLmEEu
dKt5LQbsCThhbchhYXVOqH8wn+g/tFYhlthDRY68D+Or9crxx2ItA7Dp/bc0mB24
l+k4NZXzmziyXCgxF5zvzQmgcLCuyI1Su4tM6Mi4ldD/+mO9oH6n+cG2GZ7jBxQA
+C5R9BoiSfVCHPr5PfJGNo2IEbeom9NoCAeB/F2Mf+xDAOHcZiut//T9YyuFc3op
/lOgWPI0Ypd8V/vQrDLrZcYVf7XNDPk+dg7T2tvyWgOYva6/f0v8vrsAsjQ16AP7
K0riLXrX65x4dzAIyaUytE5YC6ewMYouLW8HICZXlp2z1+KOprctSlZu7RRGbIet
pJxCXC9j1WM4DwH3SUfbJdyB0qIWnpCjRjz63n/2GGpjAnfI96NR8/iOJkmdq3AX
I00kMPl+b+BFHbCpPIioJMr0BUDJbUMyw3FA894AtkZNojQiDDJk93S6jo6BG4JA
pGM4Hm9Jfe2BKPdm+DOiTCA6vHWro/JdpElhgLFRyPpWQLrUpYdjV542zRdzbjbs
cCe2tKHm+zvWbN6FQ80Q0qxKsZf4I5jl9KYLQcRvZtEAv40ojFU=
=t2qM
-----END PGP SIGNATURE-----