-----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/jalu9uZGunHyUIFAmkgWwIACgkQu9uZGunH
yUJVYRAAsHMtKzLJiKJA72J66Zkipi/las9nOG3RWAD+DTvyRmm4YwYZbkAKLaEi
aw2Af8xyioEQ93sLw6gASPRJJq9uZuVkw82PebZNh3xEI3cYP9UYdYUTbw43MGsb
Hr/XnJ1Pj/9bejVJb/nI/0XFlQ/5LbzFrdOgQYr48xAs/7FY9j3iTtvYq3/r4gEq
1FSlbR3r5Rm3s4xetiSc+DdvbuSRGmxaVg01FSnAesABxmYTT4EbXpuxkHeK7FF8
xqOqusd6JIm7Hqst3uQ/ngsDC4fSDWZTdLjmVsMWpt+IiYUIiLnHRZtKayqiagW0
xm/a6dpgvSyxodqibFIbdNpyf7QgT8+YS9aKx4Sg2JYxlk2zEo+NS0eRYZ6mVg/4
7yfxxTLM4zqS4wc1QpxIZ6Ythbc+YKQH5/IVUtYRm7LpUDY9IQ3++t5ld4NoJgrE
gB8bDALjSjtflhb2K6x/IfqoCQWv/vwXz1SKdpLpgV5VBTUwe8OfpnoM7DJI2g13
TNeLohDKFp33a6a5qYZCtWg6nKUGEDx/2VJgUqPBArYiSSxbv7iGW63OYuYwW3o2
eUWNpKYwm/qSx9NKVt/xiOQK7WDvMe3IgT/0xf3mBNifyobdZ6kWGHnYC5WH0+Ot
MaVSGL9qNENNY5pml/ilHYq7y9KvynHVTGl+98EO7f6TBUCZvq4=
=CWWg
-----END PGP SIGNATURE-----