-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmrIRasACgkQu9uZGunH
yUJLdw//cHKXoXzXrtkpSwdGcjRAflAjnjNiRvQIfJ5WqQwXI/cnMu83osoysfzd
2vlHdQzkOSaH8ubt0BosatbRZ7CVaNBC5UO50CY+teuuPBqxOTvlL09bGcRTuAqa
+V99DMW3LtZibN8BNQPz244zWZOHhlYQLZLkwe2Av7IF7gf819Wep/Z3FokYAVUu
rVz+7JvsqqLk3BGW2Swc4wXHdTLI1t/yXGJlpgP7Ojli8WdJX0pZ0RZajZjLE58B
akW5XoCdp5FitOwxPsOBThBVhRAEdgR8tAR7sskPtQPmN0TSeiJ0pBSftWgAbboT
mNFS46o3SftoomaJTEPKKE0G9l1m7XRdHRGQywX5VBoWFJ6UNpSKCTD/6IAGQABj
gtFRKAI6vH43f2hokZaDDnRi6wrRW1CHgw1DefnIiQ6DNJCIvErceT/Ual1A38oW
LQ4zGl7bBqAwoTbG8z1/Py9RZAqTzxZX+/OhMbYA60kgUPob2OWa0Oq3JwXQFkd5
No/to4PDFd4YbfughOk6cOy0awwvZfO8VCIOo2tt67E9z4EhVagalJatrbRHXxh6
PSN+mthEPtxwT86yeuE/+WJgq+AS/72WXBmnmyevyl+PsB7jpRevb7t4lByH9xWB
D8oUwLNX4Ico7kUpuEcrOmQE0W7Xu3gDeICr8fgM6oMUbTwpxbU=
=SNCl
-----END PGP SIGNATURE-----