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

md5:
2e528092dd8428d62ac5dfa69a46be7c
sha1:
71d7487b62373fd107d633b50b31743419eea92e
sha256:
b8cc442963f5abf7452d95aa0ac9e703024302110e14c90fb788fa0be33ce5bd
sha512:
731ba4c53953c73a727bcd636e18aac4eb8908d16a6258867bbba6179f82a1d45c942e70b61cfa01948776f95871a9b3c34a7c3d5fdf1d8df6261d77dfed7806

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/jalu9uZGunHyUIFAmpZJ3AACgkQu9uZGunH
yUKAXRAAmjSBlcIojoo+zQyiZ7r7onKzlAtIBx/M8tiMHiEqov7/Rd0yP7RPqpPj
kzRgAk/2xo47gGJPBgI+bZEeedZZxtOboiQy9nBewyhjmreP9kOsuVS1oQify1Td
ebEl8L54HgnBZjR4lmssUW+v4AEKdwrxnCKwnzLOpm1Pq5bPXGldNEVOT8w6nrG4
+32zwB2TdI7OHY/tjYKIuZaXHgpl1r8Ayo525YCO/bEYMt4ZrRFF4tPVMmQca4HO
Play6/QwFhnGYThNMjszi9Bputd3cgWAuCt/IeahiI5hIgU/Ao/hywKys9mJIPBo
ZVKiXOoWmZRR7+9a50QaLhOTSIjuOKi2MAiOGEH82hwmRNlZIjfYJm3USWdamuTB
ILqwG2Q5DXW1PSbaOyeGBvdAVEavDkGV1zCfrTXczruhz/KNc1t/HzhNqxmoGuw6
MFJGLNmo0BGyeeeoONH5DoCyEB70BEEwD2ulSQqu9/8l6Wn0Ty66mToB2ppDG76S
t9efd/iVPiaHl1wNk3o1bkiiOioet47KshKEwDsw6e1unVaqfn2yWlZZbjYCwtH7
AeZaKYuJgk2VqaOhzPJf1S+qNLws3R5GZOuCxK/XOjzrMJondxJmlt49rZhULY11
FP55JpUu6JCJEvVZOyG/GXOLskJHJG8Kv5Bh+0LL9Tp8fqiKlYQ=
=l41K
-----END PGP SIGNATURE-----