-----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/jalu9uZGunHyUIFAmrjm6cACgkQu9uZGunH
yUKBog/8CCQIO4LA/N1V+RYVnthy8eAI0Mfn3ing457C4tvb5r089O41NA6brXx1
I+MBUY/H32sy7GtHNBwhK3XSTutulyrXA6cCZb0O0TW7z1Ald/02hpT5oAUqSZ+w
p8oU0/6BDmYAAXFsL+4TvV3XdPtLQQnW8+fMGAa3owaqEoz3CaBYK5GWB8gW26AZ
68uh3cwQDyeu7UKLOe4jqXkkk6T/xoOfMn0JFLYznQ8USAYF6v4ooW7ebJJKjPLD
py/WXv9s4k1ZiqMM45pln5M2F8pDl0WSUIOJt+OyAOa/D0zDsrvek83MAh0bo4sH
FgHkAgW9QxBLTJV22kB7sw6bjuhYlNz3MxqeCmyAu5+W1GohSK38N7+r651smGHC
45o+SBQhFk5jrqmEAnHBuTrwA2M9Qg39J0dWfeBMrxmymnCEAPJZuPnOi2zWMZuZ
sNZAiSGE/TgFZCysYgxRj3cjvURZv5eGDxJtJ6074Wr5f7UJj4on8FTSQAeJkHAS
UOmWuu1v58eqTr5veF+1aLNQoBVgeL/hqhQo8cakQ8krKeyi70AB8rS5SxLPdW+g
IbrMXB0taZn3U89yLPqp42F6WhvNcaBfAJeKqv3HzL6iujSKDCkdqipozKvAe/TO
sRr+8WY8gttX7cnNUt/AGUwlKcwavoqb7dj+WJmIIQ5dIQS89T0=
=uF5R
-----END PGP SIGNATURE-----