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

md5:
05a39db99bef224495078c24db168869
sha1:
f72529f5f4831038b3f783aec8d5207175c0283f
sha256:
f37be6a7a14e63d2b44f67616c070b26b71266a3122c8e80cbddcb26f8cabdc0
sha512:
b152cb08a2cdd707284e19e5d50e22c2e0f1d00fa4aefa329c5b30fd7024ae01201459dfd77170f9f4f1f4c7ce3ff02191c0204cbcf55bf0e4e524e7f145b70c

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/jalu9uZGunHyUIFAmpGEmUACgkQu9uZGunH
yUImqA//YDcPyWW3GLsVu33PuautYblDN3JQsxW652LtQZeKoB7AE6oFTpGj18EK
NyuauxW8I/WcSB+2VxtI7GhRa4qLoyWlWNEXf9kOWzWuO+eGFaQrviM8k6NDNSuM
Obf+AW6+6zenjTs2PnY9CJTTc8DZfGpfShYBqAdPs3wjRSdJueYrbdaA2bibFfpY
nS/vSmhSfCKVekFLOsKCRgH2aW4JQdwRDgWhODeJwpma2iyEZqmbXum8/UHeN7TT
yV+sSRjeAkv1zsWvKNIwbEmENLGAwqyQMgyzhORR1YDBNSNc/SlwXCsOQLlIo+rE
sDRgRLX6WlWhWaU8ftgbhZ9BMpiuYAVVTILEXzibhoUFTrbRg5YBNx+dDhR8zA56
6ENQiT/RCRwsHzNf4UeI4vtlDJgUEzIH+p82425M2CQ4uSfA8I0X/xvxt9imlCHV
WwDdMMyK/cudwjXId2SPR+39ZezaVAWEyDWK9uEZ20vWWl8oN1Jk3dKovafiAsNE
vQRC4H+pvZMASiZDns03d5a73ddhk0kC0Mwgw5XqKx9/xhrPeBsfVvTxDnkV+aUh
4ghRtD/WnN23ilBgWqmCWILsF/jDXmH8C0QnZwbNFcT9hoghTV/gBkzTj9HWdEQ8
5OMcHxtwyZXAdkBb3JJef3s2+g/89u+58QJlU3LkFo78CA2WJ0Q=
=8UVC
-----END PGP SIGNATURE-----