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

md5:
d71db59e76e908f2810b6dcf9b742ca1
sha1:
3713c76a9a230d30d2d28ccc0e1c164eb73916ca
sha256:
363f5edef02500bb9faf5a557bb5b77c463e3b7f11fcee283ff4d0614d1e88d8
sha512:
9b2ced771ecae2175569d0a6cfd02278ddd1d1d2398e48a5d9de31b7a66cbaf831ed8652cc101a1cff46a9176ffe9b835fc728fe1484a1e7c853ca2c4d9d813d

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/jalu9uZGunHyUIFAmqzB8UACgkQu9uZGunH
yUKcfxAAti0I17EUuhaU4xSJPK6qDEnS9lkVTJZb/gbPIwo0BGYARSSFsgPihbca
ONphRpE3rBP1pxKCQMEbRDsgBsXSMikQ3AEzd4gTWOgIk9uo12XxzmVnVjEzvJPe
zT4uNoAkQsf78wtIYFkEy2JgK7bqmMUbMxg0wmlkq4BCtI2E9FmZuy79atuaj6wp
wBUJUtaAE+aWnHvTT/8RMsIC/O37iK4hd8t1CwdY1eMrijKbylW1BkTT8yM/1q/w
QVIGKxqA1rrJqSvvsJEf87yR/0tGTcSa+rjzTVLvA9jRTwpsqv6DdbASfyk+OZFv
NYBxbawn8kOvT5Zp1ZVZl1sUyADoQA40EK1qb1fy9NnCP3Dw2uvbHxo87gwR0U/K
s1SWjv8hHp/eltcYAjVWFVar7RRYe+WDYTGtb5ae0GgI2fzOpI3K0Kzsg9Eemcce
y6WvsMFeC7aiDjj+bnb2ZqRl6wHp5xTxbzBjSAIVZYvjEF31GPpc4KJPf7rJEbMi
R1LptThvjEpOs6Z18nueD2IHGLebd6H4sHS1NE4dBM2FCet2lfqbI4VG5PvrdiN1
s82b2NTnQ6lN91HfbM+jjCD3cpK9gN0bGEpQ0oCb/lezyIp5OTU4oii++QAGLGda
TT5BcxIbFujyPX14QSnYvXo6/5At7Bw645cJ4+kFlc7OOK3IRj0=
=xSDc
-----END PGP SIGNATURE-----