-----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/jalu9uZGunHyUIFAmrcrS8ACgkQu9uZGunH
yULVoxAAobSa4kwRcYjGnAFbfbL1psayLGsUVffqgpMKulcI21/OB9EYhk1fglJ+
VFhh3t8f2aXYVWoXe2OmDv5cisVJhnVRg2U2wpf1jahzeSN9JSs1ay62LJhZwHWY
T4TEi4nax7p/VJ17pXkjG+jnng1gPvjORKh/v0Kfe+UbVYx5ozpwKyBZBe97/9Nb
wW7HzMi9HnpbzuJ1rCU9lRsCLbB+w0cHRDD1nEOuSroqVM2eStpwgAPVh0/AgpOH
mHhHhW2Qai4xit08rGiJIPI5ASSf4DS9j/ODcWoIPDRFvGq3uuLZxg4JulR3UywA
khZ2+WEywnLiBLorihAjSSO5sOFESq7iVx3TnmJdtk6q8k2goQRdD7jvT/Ttyzif
RpXXvQmBpraMgyZ+BSUb9A3LzhdyhSEQDw+xz27BHq7DvCnAL17XDRTI/aV3X7NT
lEvYPl1GccCfboCCLlxy6cSs9vBlNL9BfEAXuOv5jRZRJUfq4/czDVZAFJEtGyIC
64+b+WMHm68rhnyUE3FsD1OoBYki/trJuXBwFihmOls99qrXJseOgLhfTrZvvyPO
/MiEkK+OGwvaA5ohrnacfCMTxrkB9TvJCaGXmVnvGGSF1vpII5sCy9v+JamLLfiW
7/Zy7zFS59Hxue3JA7QtBPk7/8MCB90vAaC+rphGg+GI0lh+A04=
=4/yM
-----END PGP SIGNATURE-----