-----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/jalu9uZGunHyUIFAmoc/LMACgkQu9uZGunH
yUKK9A//d7kyUl0wqARS6+M4lthHLGlvbtet/r3YO3GH5VSBTTnbJs1eHDK1pw7a
xLM+USK4cqSVch1sfJ8xuszq9ZC0S3/z48NxYUlgwl2285+ksAhUEWylsoNWBwqd
63vdguZo8WIAXXVHmYtzu74JfgQYn9QsXE9b/8hY9yiPuzyEN9Q6a33bZSn7usKd
kGgtrYxwCzFMKz48/HTm9xc8Ldu7TticPihynxdTLspg0ELSExqJf3OuvdJmWv21
rtrqWSMi198VbE8SGMLUG6dz+HcSBC3Hn4Oph9fWNwD+ZDABrSGfCvqpuM7qM/kW
jdoCvl4otyRv252ULuCf/iZ4wViotk5K1TSNNcNinftKbqn9Y/ZcnJPyZANOhTJ3
IJ3paIoJBcyZ/+jCdWl2UEdCSYa+xiWzbRutFCQ7268Dg1tPYdbtENbcPvJIOVk8
a8Jy5Pt1AeEs9MT41CwtfN1iDl0/ZoXuX8jlpNKC0IGdpxAH2rGChltedeYnXktL
rDDypNFRLFq4rmL5QWCNnoXe4N8aovTYx54aqUZfAz6ykVnUDc4wGS16o7CfCl9f
NX2GrlDf3yyYGQ6nj0xQ8pyS3SJcNe0TQ8cfUX+QZ+F7mwGe7JNjRHAwQ3uUvKKr
4/8vG4Pq/ei7mXBnzE1yAJ3CwZMmFjVhZY0TxxddRLxO6ivuB5k=
=0MkV
-----END PGP SIGNATURE-----