-----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/jalu9uZGunHyUIFAmpkJIwACgkQu9uZGunH
yUJA2g/7BKH0L4dBPIRLyP3cgejbMoNGeLkhZIpqaSGjqYiTY2PfdAJF5NTbaRiG
rDxodAj8flgoKl8cAt1n5L+Ptu4gBy5Yy5KAiJ+EFjzmg/T96tlUQhT/wynXViaW
j9Mibb883MLhxfRHATm3ha38nVJ/K0AFT/0Nz/eQnqjp1NeNzaxEfbmh5FekeA6R
8OrkKI/R732Cz1J9jvbiWUfxhis25tyZjIQOt9wleFvjnmGlGO+LIqy/2jLsOEn9
M3xPHop/WPhIa3PDAxYIngaHOKd/3lufNLl3XXZ25AgVYMdqDwBgxSC53cQ2l1Fa
IpqAD52ko3zVF4NAlsVQn6NHtPHjUf2bCoiaVywXcef8ZRYt5CaBa3LEhJorJsIR
Aq/3OCVZwqHz8yP1jN0WkWrOZ2jlPiPwDaYfYo3tGEnv4AgTHNhtqpKLx3ppvebR
ZqSFb1EH7y6F9Du+VLH0W6ebrIyj3wPiShEj29WL97HLacl+sNSMOIgor4GUVxHG
pMP6hjghu6dGeDH07geXUxDn6hWC7855WTweiP4pA1lsgKun1ibVbhyd5Rh2eyuJ
Dq1YzypNo+ZqBAnyqtFZzULCcIQdNFWCEfsqGcUa8EnOlZWT6n26V16ZfNy7dXt5
uuM/Noi7bcTuBftaAB62Wv+poMD4blREOOEo+rI/m7XLVS51WAE=
=nkzH
-----END PGP SIGNATURE-----