-----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/jalu9uZGunHyUIFAmqjie0ACgkQu9uZGunH
yUK6Tw//XvpbeKkwWpFQ5gDIHa2c6vC8T5LnGC0Itw0EkSy8JfAkiJN/amyFztNM
kqEsTEfwDQ1XSb3D+nkoqh8zFsNKHXmSo3YxHHWF8fqXHPNkeRS98AD4mqs9rB1R
96L1hsUtEEJXQS1dhpzdwsKMTk3S6bQ9Ly1MH1IaU51VFMyPqDAar9d4v5a11YKO
Akt+zcrNFT8M/iCdxP03AGAu5oAyWTCvJ2knSjSzvGhATNfH4pYahw1I59/1LRLR
GGB4W6gZYYwS/fFbbhJB8eNMS/BFRRDGW15/NPHAt+MBR3ZvJbO2+dncPYgkx8U6
1ZqIC3isQTdz4HHMeJoj66l6lIAjXXtu7guy1WCI+VpSQwAcdl5cAk7PTnTHh+n+
dN84oZ1Eb5zUI8mGKVQVwPcYD16OH5kR0sJG2OSr9+j6CDEMfptrMmvUM+q+b3v6
c1n+40gEHtrKg9/fViWuXliZisNAumdrX1N0rJL1WcXK1TYYuYsztc9H/Y8IF8xv
xK+AJFyGC0uJvWCmc3E6H6c01Ss2Kz8XyBUtr7yZO94ShW1OWEtqSHDXGuxD3hVK
T3JpmCWIJZDaVafAMz24L62Y7tMgGS0IhMtZYHuz5tyb7yaR3vJHZ8vCUwiVcq/e
jLe3nIzfQumHo8Ft5WFh8WF9fYZY/WNrhaJD6vmm7kD8QlUeCUI=
=YGrV
-----END PGP SIGNATURE-----