-----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/jalu9uZGunHyUIFAmrQaAQACgkQu9uZGunH
yUJkug/+JWeBdWtvNwG1uyB2d0SLNwqmIp5nAauy2mQzLgIXaC0Mwd5RqegzBbIb
JUel2QVSDBU2rhbSgBMvMtYqIPgga12fNkSiy1Qq5ylr2HyK38ps0S7kCco+R4LY
+1Ot6DfvYWTHlnqVZZPSbwgbjX8cJiOuGSrKURFiJYkLQTfjaWfnQTRxMI138FPN
ISHO0cgtagh6LpG6NnJRQsDMdBa9RnxuBtIeqeVg58UKO2ndVDtmuz1/3rUXzH6j
kaPtrVQ+vlaelTPnOFneisP/dA4y1GevAVyqZyzhb249hD2QwzewSSbGInYT46bi
1RFgniYqipQk4ezCHd5/Nz+ICXupmb3A6fJo3hYw1oH/hgsEQMqlHZjw4EKOCzD1
SG/nOZEIFZ3giIIy3VK6w0jFGbCcxbrm5CCXjEFN6MBawbMavV8vHYeAGPWLBRY6
KQMqp/LVKHl/uMRqnHoEFoSbo45ZynO2rtFx61w3TzEkGHgtfpfP+C6ZDGJbaRhd
Ob5gxTolwb9r4QvnoSF6H2YZlwf2HpN6/Sn7vaHlqJmHnoOmAQdUdTQhFi21dIkR
bHL0ww2FfaTJZX2LbK2Ts/iaU1sF0xOIjFWW0L32+y96PhEJjXFxVa1FdW5qvMT8
D9vxRgmaWgiYeDc2BKZxMQl/gyCPvXoU/kT+mJB9lSbsfDT5oj0=
=Zpxd
-----END PGP SIGNATURE-----