-----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/jalu9uZGunHyUIFAmpVB4EACgkQu9uZGunH
yULs0BAAnkB9zaOPxh04fcrJZtzXp+31YfC1rA1Mq6wYJfqifpvbA0x5lvgrzZRu
EFTY4k7Xtyoaj6pd8aG5ocQCX1NzOyY/ak5nyDMjTODNaVbY+QK1TWJg1FYERzE8
VJ9NfuBZYaAh/c8bjSTC6CRiJwYKsM+Eg3Y2Q7Cmmb1ijmoojSDQFYrTjDCk6FjL
P3xpwjyde3LiErNiRaAqjLrROHb/KjiuQnVRfVumlJxPwxUfolEYQQD/mfTNtC/Z
z3MmiLiboRpPUtPfONvlWjYuyAP439nKrxu+7vmHK4I41RJkKmX4pfxj4wig+ApZ
b163K0y6yMhIXS/83O+l3DBsrB2fBJsxK71s9A4nRQs56tRkIQBrSfKAssuDHXCv
W3H0w/ueWfSOa9dqzErZSO1UYXxWze6yvHvcZIoGg8Zl1JySpINtQ9s963D6ldgN
xnllYHgGBoxjU7J/xOHGODiXuqONGpToLe6KH/MfQajTZbl4ppSTx9f+cPcM336c
Qz1pmVCfihfYw+GLxTzb8NU+d7auLzrcveATh9CGGRUD16aI952yiaBQM8nEC1j4
3uVNAvlUb4x16pqwk0pSMbQfjxltW/bLVSrwWot++tLnADo5N9XzNuUpOdOMbNDF
eeBocqk85tu8ydNlpOUA8WXC05o6P3BU2lPU6i1q6cWYERkgLLw=
=IAfA
-----END PGP SIGNATURE-----